docs: update wasmCloud version to 2.5.2#1217
Merged
Merged
Conversation
ericgregory
added
automated
documentation
✅ Deploy Preview for dreamy-golick-5f201e ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
🔎 Structured data validation
✅ All checks pass and no authoring warnings to backfill. ⚙️ Generated by |
ricochet
approved these changes
Jul 13, 2026
Signed-off-by: Bailey Hayes <bailey@cosmonic.com>
ricochet
force-pushed
the
docs/update-version-2.5.2
branch
from
0345c57 to
a162e95
Compare
Two substantive changes shipped in wasmCloud 2.5.2 that make the Host Interfaces section's earlier warnings and multiplexed-backend list stale: 1. wasm_component_model_implements is now compiled into the published ghcr.io/wasmcloud/wash:2.5.2 image and the standalone wash CLI binaries. Verified: .github/workflows/wash.yml sets `CARGO_FEATURES=wasm_component_model_implements` in the docker build-args for both the e2e host image and the pushed release image (both build stages), and the `canary-binaries` job that produces the release-attached wash binaries builds them with `--features wasm_component_model_implements`. The default install path now covers `(implements ..)` — no custom Docker build or `runtime.image.tag` override is required. Embedders still building their own host image can pass the same Cargo feature explicitly; the note now says how. 2. Unlabeled imports of wasmcloud:blobstore and wasmcloud:keyvalue/store now bind to the workload's default (unnamed) backend (wasmCloud#5309). A component that needs a single backend can drop the (implements ..) label entirely and still get a working binding. Also removes the incidental (and inaccurate) mention of `ghcr.io/wasmcloud/runtime-operator` in the feature-flag context — the runtime-operator is a Go controller and has no involvement with the wash-runtime Cargo feature. Bumps the "As of 2.5.1, multiplexed backends ship for..." line to 2.5.2 and appends the new default-backend sentence for keyvalue and blobstore. Rider on this PR because it's the natural landing spot for anything that only becomes true when the WASMCLOUD_VERSION placeholder flips to 2.5.2. Signed-off-by: Eric Gregory <eric@cosmonic.com>
ricochet
reviewed
Jul 13, 2026
Netlify's deploy preview failed for the previous commit while GitHub Actions build succeeded and local build succeeded. Content is clean; retrying to rule out a transient build-cache issue. Signed-off-by: Eric Gregory <eric@cosmonic.com>
Per @ricochet on the PR: `wasm_component_model_implements` is intended to be enabled in canary builds only, not in release tags. My earlier commit overreached and claimed the release image ships with the feature by default. Rework the callout to state what's actually committed to: - Release images `ghcr.io/wasmcloud/wash:X.Y.Z` do not commit to the feature — same wording direction as pre-2.5.2, with the incidental (and inaccurate) `ghcr.io/wasmcloud/runtime-operator` mention still removed. - The `ghcr.io/wasmcloud/wash:canary` tag IS built with the flag for wasmCloud's own multi-backend CI (verified: the canary and 2.5.2 manifest digests currently match, and `.github/workflows/wash.yml` sets `CARGO_FEATURES=wasm_component_model_implements` on the pushed image build). Users can point `runtime.image.tag` at it for evaluation, with the caveat that the canary manifest moves on every main merge. - For a pinned surface, build a custom host image with the same Cargo feature — unchanged from the previous doc guidance. Line 169 reverts to "Enabled in 2.5.0" (drop my "default in 2.5.2" sentence). The default-backend paragraph (unlabeled wasmcloud:blobstore and wasmcloud:keyvalue/store) stays — that's #5309 and is real in release. Signed-off-by: Eric Gregory <eric@cosmonic.com>
ricochet
approved these changes
Jul 13, 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
3 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.
Automated version bump from the wasmCloud release pipeline.
Updates
src/wasmcloud-version.tsto2.5.2.The remark plugin propagates the new value to all
{{WASMCLOUD_VERSION}}placeholdersin code blocks across the docs at build time — no other files need editing.
Merging this PR with the
release-bumplabel will auto-cutdocs-v2.5.2(via
.github/workflows/tag-after-merge.yml), which firesrelease-docs.ymlandpublishes the offline docs image + tarball.