Repository navigation
ci(release): notify the apt repository after a release - #52
Merged
Merged
Conversation
The apt repository only picked new packages up on a six-hourly schedule, so a release reached apt hours later. Send it a repository_dispatch once the .deb is attached to the release. Assisted-by: LLM Signed-off-by: Aleksei Sviridkin <f@lex.la>
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.
The apt repository picked new packages up only on a six-hourly schedule, so a release showed up in apt hours later. The release job now sends lexfrei/apt a repository_dispatch after the .deb is attached. This needs an APT_DISPATCH_TOKEN secret: a fine-grained PAT scoped to lexfrei/apt with Contents read and write.