Repository navigation
Conversation
* feat!: key the artifact's build info by file name BUILD_INFO keeps the toolchain at the top and moves cflags, target features, digest and size under artifacts["shellcheck.wasm"], so a second build of ShellCheck (one without tail calls) would only add a key. build-info.json, the Release asset, keeps its flat shape. BREAKING CHANGE: BUILD_INFO.cflags, targetFeatures, sha256 and size moved to BUILD_INFO.artifacts["shellcheck.wasm"]. * feat: tell hosts whether the engine can compile the artifact isArtifactSupported() validates two tiny modules, one with return_call and one with a v128 constant, so a web host can say the browser is too old (Safari before 18.2, Firefox ESR 115) instead of surfacing a CompileError. Exported from ./client, so it is MIT. * style: format client-entry
|
🎉 This PR is included in version 0.3.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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
Promote
nextontomain.nextis one feature ahead:feat!: key build info by artifact and add isArtifactSupported(#29), already published asv0.3.0-next.1.Merge with "Create a merge commit" — not squash or rebase. The analyzer on
mainreads the individual commits, andv0.3.0-next.1must stay reachable frommain. A squash titledchore: …would publish nothing and drop that tag frommain.After this lands,
release.ymlonmainwill publish0.3.0to thelatestdist-tag. Then mergemainback intonextwith a merge commit so the next promotion is clean.#31was squash-merged, so the branches have diverged; this merge brings them back together.