Repository navigation
chore(release): integrate standard-version for releases - #3
Merged
Merged
Conversation
Add standard-version as a devDependency and expose three release scripts: - npm run release bumps the version, regenerates CHANGELOG.md, and tags. - npm run release:dry previews the bump, changelog, and tag without writing. - npm run release:first tags the initial release without re-bumping. Document the release flow in the README (dry-run first, then release, push the tag, then npm publish), along with a note on --release-as for forcing a specific SemVer bump.
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.
Add standard-version as a devDependency and wire it into npm scripts for cutting releases.
Changes
standard-version@^9.5.0as a devDependency.package.json:npm run release— bumppackage.json, regenerateCHANGELOG.md, create thevX.Y.Ztag.npm run release:dry— preview the bump, changelog, and tag without writing.npm run release:first— tag the initial release without re-bumping.README.md(dry-run → release → push tag →npm publish), plus a short note on--release-asfor forcing a specific SemVer bump.package.jsonas the bump file, GitHub commit URLs inferred fromrepository.url,vX.Y.Ztag prefix).Verification
npm run release:dryruns cleanly and correctly infers the Conventional Commits preset and the next bump from the current commit history.pre-commit(eslint +npm test) andcommit-msg(commitlint) hooks pass on the integration commit.Notes
npm run releaseafter this is merged.