Release via tanem/release-action - #3026
Merged
Merged
Conversation
Replaces the tanem-scripts release command with the composite action, SHA-pinned and rolled forward by Renovate. The workflow keeps its filename: npm's trusted publisher for this package matches on repo + workflow filename. CHANGELOG.md is frozen at v7.1.0 — GitHub Releases is now the canonical changelog, categorised by the same labels that drive the bump. The `version` lifecycle script goes too. It ran inside `npm version`, which is how the action now bumps, and it regenerated CHANGELOG.md and AUTHORS through the very package being removed — so leaving it would have failed the release and un-frozen the changelog in the same step. The `changelog` and `authors` scripts it called go with it.
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.
This repo now releases through the
tanem/release-actioncomposite action instead of thetanem-scriptsrelease command. The action derives the semver bump from the labels on the week's merged PRs exactly as before, versions and tags the repo, publishes categorised notes to GitHub Releases, and publishes to npm under trusted publishing. Thetanem-scriptsdevDependency goes with it, taking nine transitive runtime dependencies out of the lockfile.The workflow keeps its
release.ymlfilename deliberately: npm's trusted publisher for this package matches on repo plus workflow filename, so renaming the file would mean updating the publisher first. Actions are SHA-pinned with version comments so Renovate can roll them forward.RELEASE_TOKENis gone — the bump commit and tag are pushed with the ambient workflow token — and so isCHANGELOG_GITHUB_TOKEN, which existed only to regenerate the changelog file.GitHub Releases becomes the canonical changelog.
CHANGELOG.mdis frozen at v7.1.0 with a pointer, and.github/release.ymlsorts generated notes into the same categories the bump labels already imply.The
versionlifecycle script had to go, and that is the substantive change here. It ranrun-s test changelog authors && git add .from insidenpm version— which is exactly how the action now bumps — so it would have regeneratedCHANGELOG.mdandAUTHORSthrough the very package being removed, failing the release and un-freezing the changelog in one step. Thechangelogandauthorsscripts it called are removed with it.preparestill buildsdist/on both install and publish, so the published artifact is unaffected.AGENTS.mdis updated to describe the action rather than the old command, including that a quiet week is now a clean skip instead of a failed run.AUTHORSis left in place as frozen history; nothing regenerates it andfilesnever shipped it.