ci: deploy webui.ipfs.io only after release#2498
Merged
Merged
Conversation
Publishing surfaces for webui.ipfs.io now run only after semantic-release succeeds, so a failed dispatch or one with nothing to release can no longer update the production dnslink or GitHub Pages. - ci.yml: drop the production dnslink step and the deployPages job; builds, CAR artifacts, and dev publishing are unchanged - ci.yml: drop web3.storage pinning; the remaining cluster pin fails the job directly instead of via a both-backends-failed check - deploy-release.yml: new workflow triggered by release publication; deploys the CAR attached to the release (the canonical source of truth for release content) to GitHub Pages, then points _dnslink.webui at the same CID; manual dispatch with a tag redeploys or rolls back any past release - document the flow in docs/RELEASING.md, README.md, and new AGENTS.md
lidel
marked this pull request as ready for review
July 17, 2026 17:36
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.
Problem
Production publishing is tied to the
workflow_dispatchitself, not to the release outcome: a dispatch where semantic-release fails or finds nothing to release still updateswebui.ipfs.ioon GitHub Pages and its DNSLink. A broken release can ship to users.Fix
ci.ymlno longer touches production: the_dnslink.webuiupdate and the Pages deploy are removed, along with web3.storage pinning (the remaining pin step now fails the job directly)deploy-release.ymlruns when a release is published: it downloads the CAR attached to that release, the canonical source of truth for release content, verifies its root CID, deploys it to GitHub Pages, and only then points_dnslink.webuiat the same CIDdeploy-release.ymlmanually with a tag redeploys or rolls back to any past releasedocs/RELEASING.md,README.md, and newAGENTS.mdTODO
github-pagesenvironment needs av*tag rule under "Deployment branches and tags", since these deploys run from tag refs.