Repository navigation
docs(adr): 0052 the registry finds stable releases itself - #294
Merged
Merged
Conversation
ShortArrow
marked this pull request as ready for review
October 20, 2026 02:54
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
1 participant
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.
ADR 0052 §3 left open how a release starts the registry's publishing run, deferring to ShortArrow/pkg's ADR 0001. ShortArrow/pkg#8 settled it: an hourly workflow in the registry lists the stable releases of the projects it serves and publishes each new version.
§3 now records what that means for this repository. It holds no credential for the registry and sends it nothing; a token able to send
repository_dispatchthere needs Contents write, which would also let it change the registry's keyring. A published version's.debassets are never replaced by different files under the same names, because the registry's index pins each file's size and hash.Consequences gains the delay this brings: a release reaches APT within about an hour of its GitHub Release.
release.ymlneeds no change; its.debnames and itsSHA256SUMSare what the registry reads.