Repository navigation
ci: the release deploys /apt from a commit Pages has not seen, and checks it lists the release - #18
Merged
Merged
Conversation
…ecks it lists the release Pages keeps the first deploy of a commit, and the tagged commit was deployed by its own push before the release had its .deb files: 2.4.0's /apt stayed at 2.3.0. update-apt now runs after commit-package-files, starts pages.yml on main's newest commit (the package-files commit, which nothing deployed), and reads /apt's Packages for amd64 and arm64 until they list the release. pages.yml drops the chore: release guard and its workflow_call trigger.
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.
2.4.0's /apt kept listing 2.3.0 until it was redeployed by hand. Pages keeps the first deploy of a commit, and the tagged commit had already been deployed by its own push, before the release had its .deb files.
chore: release vguard and its workflow_call triggerTested before merging: the check passes against the live 2.4.0 and fails for a version that isn't there; the run lookup finds a known dispatched Pages run and nothing for a commit without one. The dispatch itself runs for the first time at the next release, where the check would fail the release if /apt didn't update.
🤖 Generated with Claude Code