fix(release): derive tag from package.json and publish in the same run - #73
Merged
Conversation
added 2 commits
August 7, 2026 13:48
Closes #56 Dev/test dependencies inflated diffs and tripped --fail-on gates, and the CycloneDX scope field was silently dropped — there was no way to gate on runtime risk only. - Parser: extract CycloneDX component scope (required/optional/excluded) - CLI: new --runtime-only flag filters dev/test (scope=optional/excluded) components out of the diff and the gate; unset scope = runtime (CDX default) and is kept - Help text documents the flag - 3 new tests: scope parsing, flag parsing, default false 115 tests pass, tsc clean.
Closes #26 Three compounding defects in the release machinery: 1. Tag pushes used GITHUB_TOKEN, which cannot trigger publish.yml (GitHub blocks workflow re-entry from token-created events) — publish never fired. Now auto-tag.yml publishes in the SAME run after tagging. 2. The tagger derived the next version from the latest v* git tag (v0.0.x), diverging from package.json (1.0.1) forever. Now package.json is the source of truth and the tag is its next patch. 3. publish.yml (manual fallback) now warns when a tag version disagrees with package.json instead of silently overwriting. NPM_TOKEN secret doesn't exist on the repo yet: the publish step warns and skips gracefully when it's absent (tag still created). Add the secret to enable actual npm publication.
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.
Closes #26
Three defects fixed
Note
NPM_TOKEN secret doesn't exist on the repo yet — the publish step warns and skips gracefully when absent (tag is still created). Add the secret to enable actual npm publication.