chore: bump to v2.0.0 and refresh readme after publish#51
Merged
Conversation
michaelmalave
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Bumps the package to 2.0.0 in
package.jsonandpackage-lock.json, and updates the README usage sample and “See code” links to v2.0.0 so docs match the published npm release.Type of Change
(Version bump is chore; README edits are docs — pick one primary box or leave both checked as above.)
Verification
CI Passes
Confirm
package.json/ lockfile version 2.0.0 and README references v2.0.0 tags/links.Additional Context
This PR merges into
feat/ruby-to-typescript(notmain). It only aligns repo metadata and generated/readme docs with the post-publish 2.0.0 release; it does not expand the Ruby→TypeScript migration itself.Related Issue
Closes W-20888419