Repository navigation
Conversation
upils
force-pushed
the
channel-compat
branch
2 times, most recently
from
October 9, 2026 12:23
c9e34e1 to
bddf14c
Compare
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.
This PR introduces a top-level
channelskey in package slices files, declaringthe finite set of
<track>/<pattern>channels a PSF is compatible with. This fieldis mandatory for store PSFs.
Two aspects are worth noting: the list must match the package's
default-trackresolvedwith the default
stablerisk, ensuring cutting the default channel always succeeds; andvalidation happens entirely at release-read time without consulting the store, keeping
releases self-contained and verifiable offline.