ci: publish playground wasm only on release tags - #46
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
lightsofapollo
marked this pull request as ready for review
July 29, 2026 00:38
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.
Summary
v*release tagsmainWhy
The workflow was configured for matching pushes to
main, so ordinary commits could publish a WASM release asset and bumpwebsite/playground-wasm.lock. Restricting the automatic trigger to release tags keeps those updates aligned with releases.Tag-triggered workflows run from a detached tag ref, so the lock step now checks out the latest target branch before writing and committing the lock file.
Validation
actionlint .github/workflows/playground-wasm.ymlgit diff --check -- .github/workflows/playground-wasm.yml