glass-browser 0.2.4

Local, revision-safe Chrome automation runtime for agents, with semantic observation, verified workflows, MCP, CLI, TUI, and Rust APIs
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82

# Release checklist

Use this checklist for each public release.

## Release status

The current published release is `glass-browser` version `0.2.3`. This
checklist is being used for the next crates.io release, `0.2.4`. Linux
x86-64, Linux arm64, macOS x86-64, and macOS arm64 remain declared targets;
only Linux arm64 has been verified on the current machine. Windows is
unsupported.

Versioning and annotated `vX.Y.Z` tags remain part of the process. Starting
with 0.2.1, crates.io is the only publication channel. GitHub release binaries, checksum manifests, Sigstore bundles, and the npm native launcher are not release deliverables.

Pushing a `vX.Y.Z` tag runs `.github/workflows/crates-release.yml`. The action
checks the tag and package version, runs the release validation suite, performs
a crates.io dry run, and publishes only the crate. If that exact crate version
is already on crates.io, the action records the existing publication and skips
a duplicate upload. It does not create a GitHub release or upload native
binary artifacts.

## Prepare

- [x] Confirm development version `0.2.4`; release date remains pending
      publication.
- [x] Check the package name, description, license, README, and repository
      metadata in `Cargo.toml`.
- [x] Record the 0.2.0 release date in the changelog.
- [x] Record the 0.2.1 release date in the changelog.
- [x] Record the 0.2.2 release date in the changelog.
- [x] Record the 0.2.3 release date in the changelog.
- [x] Check the README installation commands against `glass --help`.
- [x] Review dependency and browser-facing security changes.
- [x] Check that the working tree has no profiles, screenshots, logs, or other
      generated data.

## Validate the checkout

Run:

```console
cargo fmt --all -- --check
python3 scripts/check-version-sync.py
cargo test --all --locked
cargo clippy --all-targets --all-features --locked -- -D warnings
RUSTDOCFLAGS="-D warnings" cargo doc --all-features --locked --no-deps
cargo package --locked --no-verify
cargo publish --locked --dry-run --no-verify
cargo deny check
cargo audit
cargo check --manifest-path fuzz/Cargo.toml --bins
GLASS_PREVIOUS_VERSION=0.1.18 scripts/smoke-clean-install.sh
```

Then complete these release checks:

- [x] Run the real-browser smoke test on the current Linux ARM64 machine with
      its installed Chromium binary.
- [x] Record the host OS, architecture, Rust target, browser version, and
      commands used for the local platform check.
- [x] Keep other declared targets labeled unverified unless their own native
      environments are tested separately.
- [x] Inspect `cargo package --list` and the unpacked package.
- [x] Review dependency, license, and vulnerability JSON reports.
- [ ] Run a clean-machine crates.io install and upgrade test after publication.

The local browser and package checks are evidence for this machine only.

## Publish

- [x] Commit the 0.2.4 development version and changelog update.
- [ ] Create a signed annotated tag such as `v0.2.4` after publication approval.
- [ ] Publish `glass-browser` from the tagged commit with `cargo publish
      --locked` after the package checks pass and publication is approved.
- [ ] Include the local Linux ARM64 verification boundary and known
      limitations in the 0.2.4 release notes or changelog.
- [ ] Verify installation from crates.io in a clean environment after
      publication.
- [x] Restore an empty `Unreleased` changelog section after publication.

A release is not complete while any required checkbox is open.