[vlad-salone]

Release 0.3.0: the browser build. sqzer goes to npm from this tag for the first time (#43, #44), AVIF decodes on wasm32 (#40) and oxipng writes PNG there (#41).

It's 0.3.0, not 0.2.1, because #41 removed sqzer_codecs::png::PngEncoder from the published library API.

Cargo.toml, both lockfiles   0.2.0 -> 0.3.0, workspace crates only
CHANGELOG.md                 ## 0.3.0 cut from Unreleased, the breaking section first
README.md                    an "In the browser" section, the note no longer says the build is not there
ROADMAP.md                   the 0.3 milestone becomes "The page at sqzer.dev": the package shipped, the page is next
CLAUDE.md                    "later a WASM package" -> "a WASM package, sqzer on npm"

tools/calibrate/Cargo.lock moves further than the version: it had not followed #40, so re_rav1d gives way to sqzer-rav1d and strum goes from 0.26 to 0.27 with it. Nothing else in that file changed.

Checked by hand

$ cargo publish --workspace --dry-run
ten crates packaged and verified from their tarballs, sqzer-wasm skipped (publish = false)

$ dist plan
announcing v0.3.0
  sqzer-cli 0.3.0

$ cargo test --workspace
377 passed

The wasm job of this PR runs pack.sh, so the tarball a tag would stage is built and run here as sqzer-0.3.0.tgz.

After merge

# the tip of main. merge nothing that touches .github/workflows until the run finishes
git tag v0.3.0 && git push origin v0.3.0

• The run ends with sqzer@0.3.0 staged, not live. Approve it under Staged Packages on npmjs.com.
• cargo publish --workspace for the crates, as for 0.2.0.
• ADR-0011 item 4 gets ticked once the version is live.

Note: The npm job has never run against the registry. It needs the trusted publisher on npmjs.com to name sqzer-dev/sqzer and release.yml. If it fails, the GitHub release and the Homebrew formula are already out, the tarball is attached to the release, and the job can be run again.

🤖 Generated with Claude Code

[greptile-apps]

Confidence Score: 4/5

[High risk] Version bump and dependency lock file updates.

The PR appears safe to merge, but its npm availability wording should reflect the approval gate.

Summary

This PR advances the Rust workspace to 0.3.0, synchronizes the calibration lockfile, cuts release notes, and documents the browser package and next website milestone.

• The Rust and npm package versions are aligned for a v0.3.0 release.
• The npm availability wording runs ahead of the required manual approval step.

_{Reviews (1) · Last reviewed commit: "chore(workspace): release 0.3.0"}