Skip to content

fix: action reports its ref as the version; npm release publishes without staging - #87

Merged
lex00 merged 1 commit into
mainfrom
ci/npm-no-stage
Nov 17, 2026
Merged

lex00 merged 1 commit into
mainfrom
ci/npm-no-stage

Conversation

@lex00

@lex00 lex00 commented Nov 17, 2026

Copy link
Copy Markdown
Contributor

chant release tags the green commit with no version commit, so the committed action bundle embedded the previous version. The action now takes its version from GITHUB_ACTION_REF when that is a version tag (uses: INTENTIUS/github-warden@v0.8.1) and falls back to package.json for branches, SHAs and floating tags. The CLI and npm package still use package.json, which chant release stamps before building. Used by --version and the drift record evidence.

The npm publish target sets stage: false, so the release does not need Allow npm dist-tag on the trusted-publisher record. The rendered publish.yml does not change (the setting is read at publish time).

Closes #85

@lex00
lex00 merged commit 54d4fc5 into main Nov 17, 2026
5 checks passed
@lex00
lex00 deleted the ci/npm-no-stage branch November 17, 2026 21:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

release: the committed action bundle reports the previous version at a new tag

1 participant