From 273cfe0d2d0fc15b9d021bff8fdfabfea59abaa2 Mon Sep 17 00:00:00 2001 From: Mohammad Saddam Hossain Date: Sat, 18 Jul 2026 22:00:38 +0530 Subject: [PATCH] docs: note the website version bump in the release checklist MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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) --- CLAUDE.md | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/CLAUDE.md b/CLAUDE.md index 3d6f4f8..8806bf8 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -131,11 +131,18 @@ When upgrading the project version, **always update all places the version is re | `docs-site/src/pages/index.js` | Maven dependency snippet in hero section | | `PLAN.md` | Released versions table | +**Outside this repo** — the marketing site ships the version too, so a bump here without +a bump there advertises a stale release on seleniumboot.com: + +| Repo / File | Location | +|---|---| +| `seleniumboot/website` → `src/data/content.ts` | `LATEST_VERSION` — feeds the copy-to-clipboard Maven snippet in the homepage CTA | + Also add a new changelog entry in `CHANGELOG.md` and `docs-site/docs/changelog.md` describing what changed. The full version history lives in `CHANGELOG.md` (extracted from the README); the README only keeps a one-line "Current release" pointer. ### Release checklist (every version bump) -1. Update all version references in the table above. +1. Update all version references in the in-repo table above. 2. Add the `CHANGELOG.md` + `docs-site/docs/changelog.md` entries. 3. Commit and push. 4. **Tag the release commit and push the tag** — lightweight tag named `vX.Y.Z` @@ -153,6 +160,10 @@ Also add a new changelog entry in `CHANGELOG.md` and `docs-site/docs/changelog.m Verify with `gh release list` (newest version should show "Latest"). 6. Publish to Maven Central (`mvn deploy`) and finish the manual publish in the Central Portal (see Publishing below). +7. **Last**, bump `LATEST_VERSION` in the `seleniumboot/website` repo and push to + `main` (Actions deploys it). Do this *after* the artifact is live on Central — + the homepage snippet is copy-to-clipboard, so bumping earlier hands visitors a + `pom.xml` that won't resolve yet. ## Publishing