Skip to content

docs: note the website version bump in the release checklist - #28

Merged
shossain786 merged 1 commit into
masterfrom
docs/website-version-bump
Jul 18, 2026
Merged

shossain786 merged 1 commit into
masterfrom
docs/website-version-bump

Conversation

@shossain786

Copy link
Copy Markdown
Contributor

Why

The Version Bumps table lists eight files, all inside this repo. The marketing site also ships the version — LATEST_VERSION in seleniumboot/website src/data/content.ts — and it feeds a copy-to-clipboard Maven snippet in the homepage CTA.

That snippet was just given a copy button, which changes the stakes: it's no longer decoration people retype, it's something they paste straight into a pom.xml. A release cut here without a corresponding bump there means seleniumboot.com quietly hands every visitor a stale version.

Nothing in the checklist pointed at it, so it would have gone stale on the next release.

What

  • New "Outside this repo" table naming the website file and what it feeds.
  • Step 1 reworded to "in-repo table" now that there are two.
  • New step 7 for the website bump, deliberately ordered last — bumping the site before mvn deploy finishes would advertise a version that doesn't resolve on Central yet.

Docs only; no code or build changes.

🤖 Generated with Claude Code

The bump table covers eight in-repo files but stops at the repo boundary.
The marketing site now ships the version too (LATEST_VERSION in
seleniumboot/website), feeding a copy-to-clipboard Maven snippet on the
homepage — so a release here without a bump there leaves seleniumboot.com
handing visitors a stale version.

Add it as an explicit cross-repo step, ordered last: the site must not
advertise a version until the artifact is actually resolvable on Central.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@shossain786
shossain786 merged commit 94fd4be into master Jul 18, 2026
2 checks passed
@shossain786
shossain786 deleted the docs/website-version-bump branch July 18, 2026 16:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant