⚠️ No Changeset found

Latest commit: cc9fbf1

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Walkthrough

The release workflow's WASM build artifact upload step was modified to explicitly upload three individual WASM packages—bundler, Node.js, and web variants—rather than a single per-target artifact. A comment clarifying the rationale for these specific paths was added. Configuration settings for handling missing files and artifact naming behaviour remain unchanged.

Possibly related PRs

• ci: restore WASM build in release #8264: Directly related refactoring of WASM build/upload in release workflow from matrix to three explicit targets
• ci: breakdown wasm CI build #8187: Prior WASM workflow refactoring that adjusted artifact paths in the release build logic
• ci: fix wasm artifact names for release workflow #8468: Related modification of the same artifact upload step with different WASM package consolidation approach

Suggested labels

A-Project

Suggested reviewers

• ematipico
• siketyan

Pre-merge checks and finishing touches

_{Comment @coderabbitai help to get the list of available commands and usage tips.}