Add nightly-6.3 to our PR CI workflow and pin all workflows to a specific tag #1443
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
stmontgomery
added
the
documentation
stmontgomery
added
enhancement
shahmishal
approved these changes
Dec 10, 2025
…flow, and add (rather than replace) 6.2 alongside nightly-6.3
jerryjrchen
approved these changes
Dec 10, 2025
stmontgomery
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 modifies our pull request GitHub Actions workflow which is currently using
nightly-6.2builds to addnightly-6.3as well. This is possible now that nightly 6.3 development snapshots are available and swiftlang/github-workflows#206 has added the necessary workflow support logic.Additionally, this pins all of our workflows which use swiftlang/github-workflows to a specific tag (
0.0.2) instead ofmain. As of swiftlang/github-workflows#196, this is now the recommended practice since it helps prevent breakages due to upstream changes in the workflow definition file.Checklist: