docs(release): bump with npm version, matching the sibling repos - #11
Merged
Conversation
The runbook told you to bump package.json, merge it, then tag separately. That is not how the other repos release and it is worse: two steps where npm version is one, with a window in between to tag the wrong commit. Verified rather than inferred from the commit subjects. ssm-secrets 3c70167b and nuxt-auth 6daf2ad0 are both single-parent, touch only package.json, carry the bare version as the subject and have zero associated pull requests, and each repo's tag points at that exact commit. Neither main is protected, so the direct push is allowed rather than a bypass.
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.
What
Replaces the three-step bump in the runbook with the sibling one-liner.
Also records that the bump commit goes straight to
mainwith no PR, which is what the other repos do.Why
The runbook said to bump
package.json, merge it, then tag separately. That is two steps wherenpm versionis one, and the gap between them is a window to tag the wrong commit. It also did not match howsidebase/ssm-secretsandsidebase/nuxt-authactually release.Checked rather than read off the commit subjects.
ssm-secrets@3c70167bandnuxt-auth@6daf2ad0are single-parent, touch onlypackage.json, carry the bare version as the commit subject, and have zero associated pull requests. Each repo's tag points at that exact commit, which is whatnpm versionproduces. Neithermainis protected, so the direct push is the convention rather than a bypass.