GitHub actions runtime upgrade conventions vs NPM trusted publishing
GitHub actions runtime upgrade conventions is an open-source agent skill for developer tools. NPM trusted publishing is an open-source agent skill for developer tools.
- GitHub actions runtime upgrade conventions is best for fix node.js deprecation warnings shown in github actions run logs.
- NPM trusted publishing is best for remove npm_token from a github actions release workflow.
- What it is
- GitHub actions runtime upgrade conventions is an open-source agent skill for developer tools.NPM trusted publishing is an open-source agent skill for developer tools.
- Best for
- Fix Node.js deprecation warnings shown in GitHub Actions run logsRemove NPM_TOKEN from a GitHub Actions release workflow
- Kind
- SkillSkill
- Pricing
- Open sourceOpen source
- Platforms
- Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf, GooseClaude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf, Goose
- GitHub stars
- 41.3K41.3K
- Last commit
- Nov 2026Nov 2026
- License
- MITMIT
- Open source
- Good for
- Fix Node.js deprecation warnings shown in GitHub Actions run logs; Upgrade setup-node, setup-python or setup-dotnet steps in a workflow; Replace mutable action tags with pinned commit SHAsRemove NPM_TOKEN from a GitHub Actions release workflow; Set up tokenless npm publishing with OIDC and provenance; Fix an ENEEDAUTH error during an npm publish in CI
What GitHub actions runtime upgrade conventions does
Safe major version selection
Guides choosing the latest stable major release of each action that still fits the workflow.
Immutable commit SHA pinning
Explains resolving a release to a full commit SHA for use in uses: lines.
Behavior-preserving changes
Asks the agent to keep triggers, permissions and step behavior unchanged during upgrades.
Post-upgrade validation checklist
Lists checks for parsing, workflow runs, artifact steps and new deprecation warnings.
One-action-at-a-time workflow
Recommends upgrading one action or a tightly related group per commit to isolate failures.
PR summary guidance
Specifies what to report: from-to versions, blocked majors and re-run workflows.
What NPM trusted publishing does
OIDC permission setup
Checks that the publishing job grants id-token write while keeping the other scopes it needs.
Token removal checklist
Finds and removes NPM_TOKEN and similar credentials from workflow steps, env and scripts.
npm version requirements
Explains which npm or pnpm and Yarn versions support trusted publishing and how to upgrade.
Error diagnosis guide
Maps ENEEDAUTH, E404 on PUT and E422 repository.url errors to their likely causes.
Workflow security rules
Warns against granting publish access to untrusted triggers such as pull_request_target.
Trusted publisher configuration
Covers matching the workflow file name, environment and reusable workflow settings on npm.
GitHub actions runtime upgrade conventions vs NPM trusted publishing: questions
Is GitHub actions runtime upgrade conventions or NPM trusted publishing cheaper?
Both are open source. Compare current plans on each official site.
What is the difference between GitHub actions runtime upgrade conventions and NPM trusted publishing?
GitHub actions runtime upgrade conventions is an open-source agent skill for developer tools. NPM trusted publishing is an open-source agent skill for developer tools.
