chore(ENG-12048): deprecate v1 — Node 20 EoL#35
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
- Adds explicit deprecation messaging for the
@v1GitHub Action now that it runs on an EoL Node.js runtime, and guides users toward migrating to@v2.
Changes:
- Emit a runtime deprecation warning on every
@v1run viacore.warning. - Add deprecation notices in user-facing metadata/docs (README banner, Marketplace description, changelog entry).
- Bump the
@v1package version to1.0.11and regenerate the bundleddist/index.js.
Reviewed changes
Copilot reviewed 5 out of 7 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| src/main.js | Adds a runtime core.warning deprecation notice for @v1. |
| README.md | Adds a top-of-file deprecation banner and migration pointers to @v2. |
| action.yml | Prefixes the Marketplace description to indicate @v1 is deprecated. |
| CHANGELOG.md | Introduces a changelog entry documenting the deprecation in 1.0.11. |
| package.json | Bumps the package version to 1.0.11. |
| package-lock.json | Updates lock metadata to match the new version. |
| dist/index.js | Regenerates the bundled action with the new deprecation warning included. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
cloudsmith-iduffy
approved these changes
May 5, 2026
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.
Summary
Following the Node.js release cycle, Node 20 is now EoL — this change adds deprecation notices to
@v1. We will continue to provide security-only patches until 2026-12-31, after which@v1reaches end-of-life. This window is to allow time for migration to@v2.Where the deprecation surfaces
@v1job (viacore.warning)@v1README[DEPRECATED]prefix on theaction.ymldescription (visible in the Marketplace listing)CHANGELOG.mdentry onrelease/v1(1.0.11)Migrating from
@v1→@v21. Bump the action reference
2. OIDC audience default has changed
@v2now defaultsoidc-audiencetohttps://github.com/{org-name}(resolved fromGITHUB_REPOSITORY_OWNER) instead ofapi://AzureADTokenExchange.If your downstream validates the
audclaim against the old value, either update that validation or pin the previous default explicitly:3. Self-hosted runners need Node.js 24
GitHub-hosted runners are unaffected. Self-hosted runners must provide Node.js 24+.
No input or output names changed — existing workflows otherwise migrate one-for-one.