glass-browser 0.2.0

Lightweight local browser control for Chrome and Chromium via raw CDP
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

# Release checklist

Use this checklist for each public release.

## Candidate status

The current release is `glass-browser` version `0.2.0`. The target
platforms are Linux x86-64, Linux arm64, macOS x86-64, and macOS arm64.
Windows is unsupported.

Do not describe a GitHub release, tag, crates.io package, npm package, or
binary artifact as published until the corresponding operation succeeds.

## Prepare

- [ ] Confirm the version and release date.
- [ ] 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] Check the README installation commands against `glass --help`.
- [ ] Review dependency and browser-facing security changes.
- [ ] 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 build --release --locked
cargo package --locked --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:

- [ ] Run the real-browser matrix on Linux x86-64/arm64 and macOS
      x86-64/arm64. Linux ARM64 uses an installed system Chromium binary.
- [ ] Run `--help`, navigation, observation, screenshot, TUI startup, and
      MCP initialization with the release binary.
- [ ] Inspect `cargo package --list` and the unpacked package.
- [ ] Download each artifact and verify `SHA256SUMS` with
      `sha256sum -c`.
- [ ] Verify the Sigstore bundle with `cosign verify-blob`.
- [ ] Review dependency, license, and vulnerability JSON reports.
- [ ] Run a clean-machine install and upgrade test.

The isolated install command above has passed on the current Linux ARM64 host.
Repeat it on each release runner before checking this release gate.

## Publish

- [ ] Commit the version and changelog update.
- [ ] Create a signed annotated tag such as `v0.2.0`.
- [ ] Publish artifacts only from the tagged commit.
- [ ] Include supported platforms, checksums, changelog entries, and known
      limitations in the release entry.
- [ ] Verify installation from each published artifact in a clean environment.
- [ ] Publish the crate and client packages only after artifact checks pass.
- [ ] Restore an empty `Unreleased` changelog section.

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