From 5f5b7369e5552f868378dc1cc61e75cc9b7b9bb9 Mon Sep 17 00:00:00 2001 From: BrandonML Date: Fri, 18 Sep 2026 12:48:19 -0400 Subject: [PATCH] docs: drop the Status column from the CWS version history In practice a submission follows the version bump almost immediately, so Draft was never a real state and Submitted/Published needed a follow-up edit each release just to flip one word (see PR #48). Date already says roughly when a version went out, and actual rejections have their own section further down -- the column wasn't carrying information those didn't already cover. Also documents in RELEASE.md that the version bump + version-history row belong in the same pre-merge commit/PR as the change they describe, since tag-release.yml reads manifest.json's version at merge time. Co-Authored-By: Claude Sonnet 5 --- RELEASE.md | 1 + cws/CHROMEWEBSTORE.md | 10 +++++----- 2 files changed, 6 insertions(+), 5 deletions(-) diff --git a/RELEASE.md b/RELEASE.md index d93cb43..11455c7 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -10,6 +10,7 @@ Steps to ship a change to `main`, which auto-deploys the server to Northflank, a - [ ] Default: open a pull request straight from the feature branch into `main` — don't merge locally and push. Going through a PR is what lets the ruleset above actually gate the merge on CI passing (a direct push of an untested commit is rejected outright, since it can never satisfy the required check). The ruleset gates on the *target* branch (`main`) requiring a PR + a green `test` check — it doesn't care what the source branch is named, so there's no need to create a `dev` branch just to have one. - [ ] Exception: if several feature branches are ready to ship together, merge them all into a shared `dev` branch first, then open one PR from `dev` into `main`. Use this only when bundling multiple branches — a single feature branch goes straight to `main`. +- [ ] Bump `manifest.json`/`package.json` to the new version and add a row to `cws/CHROMEWEBSTORE.md`'s Version History table, as a commit on the same branch/PR — this is what `tag-release.yml` reads post-merge, so it needs to land in the same merge as the change it describes rather than as a follow-up. - [ ] Wait for the `test` check to go green. If it's red, stop — do not merge. - [ ] Merge the PR. diff --git a/cws/CHROMEWEBSTORE.md b/cws/CHROMEWEBSTORE.md index 9f99a62..ecd26b0 100644 --- a/cws/CHROMEWEBSTORE.md +++ b/cws/CHROMEWEBSTORE.md @@ -187,11 +187,11 @@ https://github.com/BrandonML/tabby ## Version History -| Version | Date | Changes | Status | -|---------|------|---------|--------| -| 0.1.0 | 2026-08-19 | Initial Chrome Web Store submission: location/ZIP search with radius escalation, explore-another-area, adoption fee display, redesigned card layout | Draft | -| 2.1.0 | 2026-09-14 | Custom "Share via" menu (WhatsApp, Email, X/Twitter, Facebook, Reddit, Pinterest, Nextdoor, Copy link) replacing the single native-share-only button | Submitted | -| 2.2.0 | 2026-09-18 | Design polish: settings panel spacing + floating-label ZIP/Save input group (#30), tagline moved beside the wordmark (#25), dropped the un-loaded Inter font (#42), focus-visible rings and hover transitions, ZIP field now filters non-digit input as you type | Submitted | +| Version | Date | Changes | +|---------|------|---------| +| 0.1.0 | 2026-08-19 | Initial Chrome Web Store submission: location/ZIP search with radius escalation, explore-another-area, adoption fee display, redesigned card layout | +| 2.1.0 | 2026-09-14 | Custom "Share via" menu (WhatsApp, Email, X/Twitter, Facebook, Reddit, Pinterest, Nextdoor, Copy link) replacing the single native-share-only button | +| 2.2.0 | 2026-09-18 | Design polish: settings panel spacing + floating-label ZIP/Save input group (#30), tagline moved beside the wordmark (#25), dropped the un-loaded Inter font (#42), focus-visible rings and hover transitions, ZIP field now filters non-digit input as you type | ## Review Notes