feat: v0.22.2 — harden terminal and wasm release gates#304
Merged
Conversation
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
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.
Release v0.22.2
Patch release focused on terminal safety, browser backend lifecycle, state cleanup, API consistency, release gates, and documentation parity.
Highlights
f64APIs while keeping deprecatedf32aliases for compatibility.WasmAppHandleand DOM mount/flush/dispose browser smoke coverage.superlighttuiandslt-wasmversioning and harden CI/release publishing order.Local gate
cargo fmt -- --checkcargo check --all-featurescargo clippy --all-features -- -D warningscargo test --all-featurescargo check --examples --all-featurestyposcargo check -p superlighttui --no-default-featurescargo check -p slt-wasm --target wasm32-unknown-unknowncargo hack check -p superlighttui --each-feature --no-dev-depscargo auditcargo deny checkcargo +1.88 check -p superlighttui --features async,serdecargo +1.88 clippy -p superlighttui --all-features -- -D warningscargo check -p slt-wasm --all-features --target wasm32-unknown-unknowncargo clippy -p slt-wasm --all-features --target wasm32-unknown-unknown -- -D warningscargo test -p slt-wasm --all-featurescargo semver-checkscargo package --allow-dirty -p superlighttuiLocal browser
wasm-packsmoke was attempted but this macOS host has no PATH chromedriver and wasm-pack downloads a ChromeDriver that mismatches the locally installed Chrome. CI now installs Chrome and chromedriver explicitly and passesCHROMEDRIVERtowasm-pack.Closes #284
Closes #285
Closes #286
Closes #287
Closes #288
Closes #289
Closes #290
Closes #291
Closes #292
Closes #293
Closes #294
Closes #295
Closes #296
Closes #297
Closes #298
Closes #299
Closes #300
Closes #301
Closes #302
Closes #303