Prepare v0.2.0 release#11
Merged
Merged
Conversation
Bumps package.json to 0.2.0 and updates the pinned-install examples in README.md from #v0.1.0 to #v0.2.0. The historical "pre-v0.1.0 build" note in Troubleshooting stays — it refers to an old cache state, not the current version.
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.
Summary
package.jsonversion from0.1.0to0.2.0.README.md(lines 155 and 270) from#v0.1.0to#v0.2.0.v0.1.0build" untouched — it refers to a historical cache state, not the current version.After merge: tag the merge commit as
v0.2.0, push the tag, and publish a GitHub Release with notes covering everything that landed since v0.1.0 (working-discipline guidance, first-match-wins foragents-md-revise,fileswhitelist for install footprint, expanded.gitignore).