remove patches for lifecycle - #344
Merged
PiotrKorkus merged 1 commit intoSep 14, 2026
Merged
PiotrKorkus merged 1 commit into
PiotrKorkus merged 1 commit into
Conversation
kgraeper
requested review from
AlexanderLanin,
FScholPer,
MaximilianSoerenPollak,
PiotrKorkus,
antonkri,
dcalavrezo-qorix,
lurtz,
nradakovic,
opajonk and
pawelrutkaq
as code owners
September 14, 2026 12:30
|
The created documentation from the pull request is available at: docu-html |
PiotrKorkus
approved these changes
Sep 14, 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
2 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.
The lifecycle patches were already applied upstream in the lifecycle repo and are no longer referenced in known_good.json, so they are removed.
Removed files:
known_good.json needs no change — the score_lifecycle entry never carried a bazel_patches field against the current pinned hash, and the changes are present at that commit already, so the build is unaffected.