chore: prepare 0.2.1 release - #7
Merged
Merged
Conversation
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
1 participant
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.
The repository is ready for the next npm publication, but
package.jsonstill reports the already published0.2.0version after the merged adapter fixes.This changes the package version to
0.2.1so the next publication can carry the merged documentation and adapter corrections. After this PR merges, publish npm0.2.1together with GitHub Releasev0.2.1as required by the repository instructions.Verification:
npm test(76 passed, 1 skipped)npm run check-packagenpm pack --dry-rungit diff --checkAgent: GPT-6 via Codex