ci(deploy): bump install-action pin to fix wasm-pack 404#148
Merged
Conversation
The old pin's bundled manifest pointed wasm-pack downloads at drager/wasm-pack, which hosts no releases, so the v2.4.7 deploy failed with a 404 installing wasm-pack@0.13.1. Bump to v2.81.1, whose manifest uses the now-canonical wasm-bindgen/wasm-pack repo (which still serves v0.13.1 with matching checksums). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.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
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
The
v2.4.7"Deploy to GitHub Pages" run failed at the Install wasm-pack step with a repeated 404:Root cause
The wasm-pack repo changed ownership. The old
taiki-e/install-actionpin (a2352fc, ~v2) froze a manifest that pointed wasm-pack downloads atdrager/wasm-pack— a repo that hosts no releases. Nothing in our repo changed; the upstream metadata our pin captured went stale. The action has since corrected its manifest to the now-canonicalwasm-bindgen/wasm-pack.Fix
Bump the pin to
v2.81.1(e49978b), whose manifest useswasm-bindgen/wasm-pack.Verified before applying:
wasm-bindgen/wasm-packserves our pinnedv0.13.1(302 → asset)0.13.1entry with checksums, sochecksum: truestill validatesdeploy.ymlis the only workflow using this action —ci.ymlandpublish-python.ymldon't install wasm-packAfter merge, the
v2.4.7tag will be moved onto the merge commit to re-trigger the deploy.🤖 Generated with Claude Code