6.0: Pin Ninja checkout to v1.11.1 #73006
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
Ninja 1.12 just released and seems to be dying silently while building the Swift stdlib. Lets go ahead and pin it to the old tag. Pinned dependencies are better from a security standpoint anyway. I'm leaving `next` on the ninja release branch so that we still have some signal from it, but folks aren't generally living on `next`, so it should have less impact.
tbkka
approved these changes
Apr 12, 2024
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.
Cherry-pick of #72989 .
Ninja 1.12 just released and seems to be dying silently while building the Swift stdlib. Lets go ahead and pin it to the old tag. Pinned dependencies are better from a security standpoint anyway.
I'm leaving
nexton the ninja release branch so that we still have some signal from it, but folks aren't generally living onnext, so it should have less impact.