Repository navigation
ci: deploy Pages under a version of each run - #242
Merged
Merged
Conversation
A release tag sits on the commit main already deployed, and Pages keeps the first deployment of a build version, so the tag run reported success while the site kept serving main's build. The deploy job now calls the Pages API with <sha>-<run id>-<attempt> as the build version.
Collaborator
0kaba0hub
added a commit
that referenced
this pull request
Oct 31, 2026
Pages answers 404 to a build version that is not a commit, so the <sha>-<run>-<attempt> version failed the first deploy after #242. The orphan commit each run pushes to gh-pages is new on every run, so it is the version. A failed create now logs the API's answer. Co-authored-by: Ihor Rusyn <0kaba0@gmail.com>
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.
The
v2.4.5deploy runs succeeded, yet/2.4.5/is still 404 andversions.jsonon the site is empty, whilegh-pagesalready holds both.Cause:
actions/deploy-pagesuses the commit SHA as the Pages build version. The release tagv2.4.5sits on2c59279, the commit themaindeploy had already published, and Pages kept that first deployment. Every release lands the same way, because the release pipeline tags the head ofmain.Change: the deploy job calls the Pages deployment API itself, with
<sha>-<run id>-<attempt>as the build version, so each run is a deployment of its own.upload-pages-artifactthrough a job output.A branch cannot deploy to
github-pages, so the merge is the first run. It also publishes 2.4.5, since the build packs the wholegh-pagesbranch.actionlintis clean.