feat(static-site): publish v0.3.2 - #35
Merged
Merged
Conversation
raymondk
approved these changes
Jul 31, 2026
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
2 participants
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.
Publishes the
static-siterecipe at v0.3.2, pinning the canister and sync-plugin wasm from dfinity/certified-assets's v0.3.2 release.The committed
recipe.hbsis the asset attached to that release, verbatim — verify it matches:https://github.com/dfinity/certified-assets/releases/download/v0.3.2/recipe.hbs
After merge, tag
static-site-v0.3.2in this repo to cut the recipe release.Context: version ordering
This publishes
static-site-v0.3.2, below the existingstatic-site-v0.4.0. That'sdeliberate: the
static-siterecipe version tracks the certified-assets release itpins, and v0.4.0 pins v0.3.1 artifacts. A minor bump upstream also carries a specific
meaning — breaking change, canister reinstall, every asset re-uploaded — which doesn't
apply here.
Sequence: merge this → tag
static-site-v0.3.2→ retire thestatic-site-v0.4.0tagand release. One local checkout references it, coordinated directly.
#34's
visibilityoption is unaffected: it was carried upstream incertified-assets#118, so it's in
the recipe committed here and the diff is only the two wasm pins. These files are
regenerated from that repo on each publish, so changes persist by landing there.