chore: release runbook and benchmark guard#23
Open
benvinegar wants to merge 1 commit into
Open
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.
Two changes to prevent the missing-benchmark CI failure from recurring:
AGENTS.md: Added a Releases section with the exact step-by-step runbook, emphasizing that pnpm bench:release must run and the snapshot must be committed before tagging.
scripts/check-release-version.mjs: The release workflow already runs this script to verify the tag matches package.json version. Now it also checks that benchmarks/release/bench-.json exists, failing early with a clear message instead of letting bench:release:compare fail later with a less obvious error.