Releasing a version - SeleniumBase for Rust

A release is cut from main by a maintainer, by hand. GitHub Actions cannot run for this repository at the moment (billing), so the release workflow does not build binaries: the only prebuilt binary is the macOS arm64 one built locally, and every other platform installs from source (cargo install --git ... --tag vX.Y.Z seleniumbase-rs-cli) or through Homebrew.

Warning

Every push, tag, GitHub release and Homebrew commit is public. Run the whole gate on the exact commit you tag, and never force-push.

Start from a clean, current main

Terminal

git fetch origingit switch main && git merge --ff-only origin/maingit status --short    # nothing but files you mean to keep out of the release

Set the version

Terminal

cargo set-version X.Y.Z -p seleniumbase-rs -p seleniumbase-rs-cli

cargo set-version (cargo-edit) also moves the CLI crate’s path dependency on the library; Cargo.lock follows. Update the version pins in README.md and look for the old version in other docs (rg -n 'OLD\.VERSION' -g '*.md' -g '*.toml' -g '*.rb', CHANGELOG files aside).

Close the changelog

Rename ## [Unreleased] in CHANGELOG.md to ## [X.Y.Z] - YYYY-MM-DD, open a new empty ## [Unreleased] above it, then write the docs page from it:

Terminal

python3 -I tools/docs7_changelog.py

Regenerate what is generated

Terminal

SB_UPDATE_COMPLETIONS=1 cargo test -p seleniumbase-rs-cli --bin sbrs usage_specSB_UPDATE_API_INDEX=1 cargo test -p seleniumbase-rs --features mcp-server api_indexpython3 -I tools/parity/render_docs.py

Commit everything as chore(release): X.Y.Z.

Gate the release commit

Terminal

export CARGO_BUILD_JOBS=2 CARGO_INCREMENTAL=0 CARGO_PROFILE_DEV_DEBUG=0cargo fmt --all -- --checkcargo clippy --all-targets --features "mcp-server test-util" -- -D warningscargo nextest run --features "mcp-server test-util"cargo test --doc --features "mcp-server test-util"cargo audit && cargo deny checktrufflehog filesystem . --only-verified && ripsecretsjust mdx && mdbook build

Publish main and the tag

Terminal

C=$(git rev-parse HEAD)git fetch origin && git merge-base --is-ancestor origin/main "$C"git push origin "${C}:refs/heads/main"git tag -a vX.Y.Z -m "seleniumbase-rs X.Y.Z" "$C"git push origin vX.Y.Z

In zsh write "${C}:refs/heads/main": $C:r would be read as a modifier.

Build the macOS binary

Terminal

cargo build --release --locked -p seleniumbase-rs-cli

Archive target/release/sbrs and target/release/sbrs-mcp with the completion scripts as seleniumbase-rs-vX.Y.Z-aarch64-apple-darwin.tgz, and write its SHA-256 next to it.

Create the GitHub release

Terminal

gh release create vX.Y.Z --verify-tag --title "vX.Y.Z" --notes-file NOTES.md \  seleniumbase-rs-vX.Y.Z-aarch64-apple-darwin.tgz seleniumbase-rs-vX.Y.Z-aarch64-apple-darwin.tgz.sha256

The notes are the version’s CHANGELOG block, plus a line saying the prebuilt binary is for macOS arm64 only and how to install elsewhere.

Update the Homebrew formula

In the homebrew-tap repository, set url to the tag’s source archive and sha256 to its checksum in Formula/sbrs.rb:

Terminal

curl -sL https://github.com/MustCodeAl/seleniumbase-rs/archive/refs/tags/vX.Y.Z.tar.gz | shasum -a 256brew audit --strict --online Formula/sbrs.rbbrew install --build-from-source Formula/sbrs.rb && brew test sbrs

Commit sbrs X.Y.Z and push. brew upgrade sbrs then gives users the release.

Move the consumers

The companion extension’s end-to-end crate pins the library by tag: move it to vX.Y.Z. The stealth workspace follows with cargo update -p seleniumbase-rs and its own gates.