fix: sync package.json version with published tags, backfill changelog#101
Open
dmchaledev wants to merge 1 commit into
Open
fix: sync package.json version with published tags, backfill changelog#101dmchaledev wants to merge 1 commit into
dmchaledev wants to merge 1 commit into
Conversation
package.json/package-lock.json stayed at 1.0.1 because publish.yml only bumped the version inside its own ephemeral job — the bump was never committed back to main. Tags v1.0.2/v1.0.3 were published to npm with no corresponding CHANGELOG entries, so `--version` and the changelog both misrepresented what was actually shipped (closes #94). - Bump package.json/package-lock.json to 1.0.3 (the latest published tag) - Backfill CHANGELOG.md entries for 1.0.2 and 1.0.3 - auto-tag.yml now bumps package.json itself and commits the release (with [skip ci]) alongside the tag, so this can't drift again Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GmYTtFbpbcmFtYv7RbJRFL
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
2 participants
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.
Summary
Closes #94.
package.json/package-lock.jsononmainwere still at1.0.1while npm has already shippedv1.0.2andv1.0.3— becausepublish.ymlonly bumped the version inside its own ephemeral job (npm version "$TAG_VERSION" --no-git-tag-version) and never committed that bump back tomain.CHANGELOG.mdwas similarly stuck at1.0.1despite grade-changing rule fixes shipping in between (stricter Permissions-Policy scoring, CSPbase-uri/bare-scheme checks, etc.), with no record of why a CI gate's result might have changed.package.json/package-lock.jsonto1.0.3(the latest published tag) sosecurity-headers --versionreports the truth.CHANGELOG.mdwith[1.0.2]and[1.0.3]entries, called out by PR/issue number, including the grading-relevant changes..github/workflows/auto-tag.yml: it now runsnpm versionitself and commits the release (chore: release vX.Y.Z [skip ci]) alongside the tag it pushes, somainand the published version can no longer drift apart.[skip ci]keeps the release commit from re-triggering CI (and therefore this same workflow).No source/behavior changes to the library itself — only
package.json,package-lock.json,CHANGELOG.md, and the auto-tag workflow.Test plan
npm run typecheckpassesnpm testpasses (85/85)package.jsonandpackage-lock.jsonversions match (1.0.3) and are valid JSON.github/workflows/auto-tag.ymlYAML syntaxmainwill exercise the updated auto-tag workflow end-to-end (commit + tag + push)🤖 Generated with Claude Code
https://claude.ai/code/session_01GmYTtFbpbcmFtYv7RbJRFL
Generated by Claude Code