Repository navigation
Accept candidate sets built from omacom/omarchy - #53
Merged
Merged
Conversation
omacom/omarchy#14431 merged the runtime upstream, so a set built from it names omacom/omarchy. The policy now lists both source repositories; sets that name the omacom/omarchy-mac fork still verify.
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
quattro, so a candidate set built from it (e.g.e1b0e5e9b) namesomacom/omarchyas its source. The trust policy only acceptedomacom/omarchy-mac, so verification refused it with "wrong build manifest".policy.jsonnow hassource_repositories: ["omacom/omarchy", "omacom/omarchy-mac"]; both checks incandidate_set.pyuse it. Sets that name the fork keep verifying (it serves the same commits). Platform repositories are unchanged.Test plan
image-builder/test/allin an Arch Linux ARM containeromacom/omarchyate1b0e5e9b