chore(release): tracking files for 0.8.13 - #592
Open
sotashimozono wants to merge 1 commit into
Open
Conversation
The four files that record the last published stable, bumped together as CONTRIBUTING describes. They cannot be written before the release exists: the formula pins the binaries by sha256, and .mcp.json pins the npm version the plugin runs. Formula regenerated from the v0.8.13 release's own .sha256 assets, not by hand. Verified: update-homebrew-formula.test.sh passes, the release-sync posture check reports all four agreeing on 0.8.13 with a CHANGELOG section to match, and doiget-cli@0.8.13 is live on npm so the pin is not a 404. Signed-off-by: Sota Shimozono <shimozono-sota631@g.ecc.u-tokyo.ac.jp>
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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 one maintainer step after a stable release, per CONTRIBUTING. Four files record the last published stable and none can be written before the release exists — the formula pins the binaries by
sha256, and.mcp.jsonpins the npm version the plugin runs.Formula/doiget.rb.sha256assets.claude-plugin/plugin.jsonversion.claude-plugin/marketplace.jsonversion.mcp.jsondoiget-cli@0.8.13Verified rather than assumed
scripts/update-homebrew-formula.test.shpasses — the committed formula is byte-identical to generator output, so it is not a hand-edit.release-tracking files name one versionposture check, new this cycle, reportsformula=0.8.13 plugin=0.8.13 marketplace=0.8.13 .mcp.json=0.8.13and thatCHANGELOG.mdhas a matching section — the check that exists because.claude-plugin/*once sat at 0.8.11 while 0.8.12 was shipping.doiget-cli@0.8.13is live on npm (dist-tags.latest = 0.8.13), so the pin is not a 404 for plugin users.Note on
version-bumpExpected red.
nextcarries the clean0.8.13after this cycle's cut landed there before the promotion, so every PR tonextnow fails the beta-lane rule. It is not a required check onnext.