Modernize GitHub Actions workflows#196
Merged
Merged
Conversation
Bump actions/checkout@v3 → v6 and actions/setup-node@v3 → v6 to clear the Node.js 20 deprecation warning (forced to Node 24 on 2026-06-02). Upgrade the workflow Node.js runtime from 16.x (EOL Sept 2023) to 22.x LTS. Drop the duplicate `push: tags` trigger from the release workflow. GitHub releases already push the tag, so both events fired on every publish and the second run always failed with "already published". Keep only the `release: published` trigger, which is the deliberate action. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
Summary
actions/checkout@v3 → v6andactions/setup-node@v3 → v6to clear the Node.js 20 deprecation warning (GitHub forces Node 24 on 2026-06-02 and removes Node 20 on 2026-09-16).16.x(EOL since Sept 2023) to22.xLTS.push: tagstrigger fromrelease-package.yml. GitHub releases already push the tag, so both events fired on every publish and the second run always failed with "already published" (see run24878697800and its sibling24878684711). Onlyrelease: publishedremains.Note — does not fix the v4.0.1 publish failure
Run
24878697800failed withCouldn't publish package: "https://registry.npmjs.org/@graylog%2fsawmill: Not found". That is the npm registry's response to a publish request carrying an invalid/expired token on a scoped package (404 is returned instead of 401/403 for privacy). TheNPM_RELEASE_TOKENorg secret atGraylog2was created 2023-11-28 and has never been rotated — it needs to be regenerated on npmjs.com and the org secret updated before a new v4.0.1 tag/release will publish.Test plan
Buildworkflow runs green on a subsequent push/PR.NPM_RELEASE_TOKEN, cut a patch release and confirmPublish Package to npmjsnow runs exactly once (onrelease: published) and succeeds.🤖 Generated with Claude Code