Repository navigation
fix: action reports its ref as the version; npm release publishes without staging - #87
Merged
Merged
Conversation
…ases directly Closes #85
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.
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