Repository navigation
Release 0.1.1, the first npm alpha - #19
Merged
Merged
Conversation
The v0.1.0 tag's publish run failed before uploading (fixed in #18), so 0.1.0 never reached npm. Publish the first alpha as 0.1.1 instead of moving the tag. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
Bumps the version to 0.1.1 for the first
wechaty-puppet-neoalpha:package.json,package-lock.json,PuppetNeo.VERSION, and the README's release example.The
v0.1.0publish run failed before uploading anything (fixed in #18), so 0.1.0 never reached npm. Releasing as 0.1.1 avoids moving the existingv0.1.0tag. After merge, thev0.1.1tag publishes to npm onnext.Testing
npm run build,npm run typecheckand the offline tests (9 pass) on Node.js 26 (Linux x64).🤖 Generated with Claude Code