ci(release): reference the shared release workflows through v1 - #30
Merged
Merged
Conversation
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
Reference the shared npm release workflow from
AntelopeJS/.githubthrough the moving major tag@v1instead of a pinned commit SHA. The organization re-pointsv1to the latest backward-compatible version of the reusable workflows (see the "Release channels" section of the organizationCONTRIBUTING.md), so this repository picks up compatible fixes, such asrelease: v${version}commits on the next channel and optional service containers, without manual SHA bumps.Related issue
N/A: organization-wide maintenance change aligning release workflow references on
v1.Verification
grep -rn 'AntelopeJS/.github/.github/workflows' .github/workflowsshows only the@v1reference.actionlint .github/workflows/release.ymlpasses.Checklist