docs: record v1.1.0 as released on GitHub, and the moved tag
- docs/15: Phase 7 done (#26–#29); a "v1.1.0 released" row with the signed
tag on 9040f84, the checksum-verified zip and its manifest diff against
1.0.1 (version, Chrome floor, CSP — nothing else); a pending "submitted"
row; a decision-log row on why the tag moved.
- docs/00: the header says released, not in preparation; §10 item 12 lists
what is still human-only for the store; doc suite 1.9.
- docs/13 §7: the one case where re-pointing a tag is right — a run that
failed before any Release existed.
- CLAUDE.md: phases 0–7 complete; the Phase 7 exit as it stands.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
9040f84fe2
commit
b73803a718
4 files changed
+26
-9
No files matched your search
@@ -8,7 +8,8 @@ This file is the entry point; the `docs/` suite is the specification.
|
||||
>
|
||||
> **BookmarkMagic is published on the Chrome Web Store and has real users**
|
||||
> (v1.0.0 live by 2026-08-03; v1.0.1 live, confirmed on the listing
|
||||
> 2026-10-28). Phases 0–6 are complete; the project is in **maintenance**.
|
||||
> 2026-10-28; v1.1.0 released on GitHub 2026-10-29, ⚠️ not yet submitted).
|
||||
> Phases 0–7 are complete; the project is in **maintenance**.
|
||||
> That changes the rules of the game:
|
||||
>
|
||||
> - Every change now reaches installed users through a store review. It needs a
|
||||
@@ -148,9 +149,10 @@ around a store, with Sort A→Z, drag to reorder and batched live sync; a
|
||||
technical redesign of every surface; local diagnostics; a cross-tab write
|
||||
lock; docs and legal synced (clarifications only — `LEGAL_VERSION` stays 1);
|
||||
contact aliases per purpose.
|
||||
**Exit:** `main` tag-ready with `verify:full` green; the human runs the
|
||||
docs/11 §5 manual pass on real Chrome including the **1.0.1 → 1.1.0 upgrade
|
||||
over an existing profile** ⚠️, then uploads the release zip to the store ⚠️.
|
||||
**Exit:** ✔ v1.1.0 tagged and released 2026-10-29 (signed tag on `9040f84`,
|
||||
checksum-verified zip). Still human-only: the docs/11 §5 manual pass on real
|
||||
Chrome including the **1.0.1 → 1.1.0 upgrade over an existing profile** ⚠️,
|
||||
then the zip uploaded to the store ⚠️.
|
||||
|
||||
## Working style
|
||||
|
||||
|
||||
@@ -17,16 +17,18 @@
|
||||
> 5 users) on 2026-10-28. ⚠️ The exact approval date was never recorded — the
|
||||
> owner can read it from the dashboard. Installed users are on 1.0.1.
|
||||
>
|
||||
> **v1.1.0 is in preparation** on `release/1.1.0`: versioned, with its
|
||||
> CHANGELOG section dated 2026-10-29, but not yet tagged, released or
|
||||
> submitted. Until it clears review, installed users stay on 1.0.1. It raises
|
||||
> **v1.1.0 is RELEASED on GitHub, not yet on the store.** Tagged and
|
||||
> released 2026-10-29 (signed tag on `9040f84`, checksum-verified zip). ⚠️ It
|
||||
> still needs the owner's manual pass on real Chrome, including the 1.0.1 →
|
||||
> 1.1.0 upgrade over an existing profile, and a hand upload to the store
|
||||
> (`13 §1b`); until it clears review, installed users stay on 1.0.1. It raises
|
||||
> the floor to Chrome 136 (`08 §7`); permissions are unchanged.
|
||||
>
|
||||
> The project is now in **maintenance**, not construction: every change from
|
||||
> here reaches installed users through a store review, so it needs a version
|
||||
> bump, a CHANGELOG entry and an update submission (`13 §1b`). Sequencing lives
|
||||
> in `/CLAUDE.md`; what is still open is in §10 below.
|
||||
> **Doc suite version:** 1.8 (2026-10-29 — specs reconciled with `release/1.1.0`)
|
||||
> **Doc suite version:** 1.9 (2026-10-29 — v1.1.0 released on GitHub)
|
||||
|
||||
---
|
||||
|
||||
@@ -220,6 +222,13 @@ Derived identifiers (canonical across docs and code):
|
||||
open: the exact approval date, and `13 §1b` step 10 against the published
|
||||
build (install on a clean profile, re-run the upgrade check) — no result is
|
||||
recorded for either.
|
||||
12. ⚠️ **v1.1.0 to the store.** The GitHub Release exists and is verified
|
||||
(`15`'s progress table). Still human-only: the `11 §5` manual pass on real
|
||||
Chrome — the **1.0.1 → 1.1.0 upgrade over an existing profile** above all —
|
||||
then the hand upload of the Release zip (`13 §1b`), with new screenshots
|
||||
chosen from `store/screenshots/`. Also unverified outside the harness: the
|
||||
account-storage roots of a signed-in profile and the hidden empty Mobile
|
||||
root (`02 §4`), and the `MAX_WRITE_DEPTH` rationale against a real Chrome.
|
||||
|
||||
## 11. Reading order
|
||||
|
||||
|
||||
@@ -191,6 +191,9 @@ to read carefully.
|
||||
already seen, so a rejected 1.0.1 comes back as 1.0.2 — not as a re-upload.
|
||||
3. Never delete or move the tag of a rejected version. It is a real, published
|
||||
GitHub Release and moving it invalidates its checksum. Leave it and move on.
|
||||
The one exception is a tag whose run failed **before** any Release existed —
|
||||
nothing was published, so fix the workflow on `main` and re-point the tag,
|
||||
as `v1.1.0` was (`15` decision log, 2026-10-29).
|
||||
4. Note the rejection and its resolution in `15`'s decision log — it is the only
|
||||
memory the project has of what the reviewers actually object to.
|
||||
|
||||
|
||||
+4
-1
@@ -25,7 +25,9 @@ Build-phase breakdown lives in `CLAUDE.md` (single source for sequencing).
|
||||
| **v1.0.1 released** | ✔ 2026-08-03 | signed tag on `4654086`, GitHub Release with a `sha256sum -c`-verified zip; shipped manifest `1.0.1`, permissions unchanged. `announce` skipped (no `DISCORD_ANNOUNCE`), store publish skipped (no `CWS_AUTOPUBLISH`) |
|
||||
| **v1.0.1 submitted** | ✔ 2026-08-03 | uploaded to the CWS dashboard by hand (`13 §1b` step 6) |
|
||||
| **v1.0.1 published** | ✔ observed 2026-10-28 | listing shows version 1.0.1 (`Updated: August 3, 2026`), 5 users. ⚠️ Exact approval date not recorded; `13 §1b` step 10 (clean-profile install of the published build + upgrade re-check) has no recorded result |
|
||||
| 7 — v1.1.0 | in review 2026-10-29 | PR-A toolchain/CI/Sonar merged as #26; PR-B (import redesign, Chrome/Firefox formats, Merge reuse, Edit store + Sort A→Z + reorder, technical UI, diagnostics, docs/legal) on `release/1.1.0` |
|
||||
| 7 — v1.1.0 | ✔ 2026-10-29 | PR-A toolchain/CI/Sonar (#26); PR-B import redesign, Chrome/Firefox formats, Merge reuse, Edit store + Sort A→Z + reorder, technical UI, diagnostics, docs/legal (#27); the second review's fixes, which missed the #27 merge (#28); the release workflow's artifact fix (#29) |
|
||||
| **v1.1.0 released** | ✔ 2026-10-29 | signed tag on `9040f84`, GitHub Release with a `sha256sum -c`-verified zip (`104f020c…2dd6c94`, 94 091 bytes). Its manifest differs from 1.0.1's only in `version`, `minimum_chrome_version` (120 → 136) and the new CSP; permissions unchanged. The first tag run failed before publishing anything (`12 §2.3`); fixed in #29 and the tag moved while no Release existed. `announce` and store publish skipped (variables unset) |
|
||||
| **v1.1.0 submitted** | ⚠️ pending | owner: the `11 §5` manual pass on real Chrome, including the **1.0.1 → 1.1.0 upgrade over an existing profile**, then upload the Release zip by hand (`13 §1b`) |
|
||||
|
||||
**Verified on real browsers 2026-07-25:** Chrome and Brave, unpacked build.
|
||||
Until that point every phase had been tested only against a hand-rolled
|
||||
@@ -296,3 +298,4 @@ without one).
|
||||
| 2026-10-29 | **The extension-page CSP gains `default-src 'none'`** — reversing the earlier "deliberately no default-src". Every directive the pages use is listed, so it changes nothing for them, and it closes what was left open (manifests, prefetch). WebRTC, which no CSP directive Chrome enforces governs, stays covered by the bundle and source scans | 08 §3 |
|
||||
| 2026-10-29 | **Diagnostics allowlist enforced by types**: every `DiagEvent` string field is a union of fixed values, error names pass through an allowlist (`'other'` otherwise), and `@ts-expect-error` tests keep a title from compiling | 09 §7 |
|
||||
| 2026-10-29 | **SonarCloud runs in two jobs**: coverage with no secret, then a scan that installs nothing and gets the lcov report as an artifact — a job's secrets are readable by every step on its runner | 12 §2.5 |
|
||||
| 2026-10-29 | **The first `v1.1.0` tag run failed before publishing, and the tag was moved.** `upload-artifact` skips hidden paths, so the build job's `.output/*` matched nothing. Fixed in #29; since no Release or asset existed yet, `v1.1.0` was re-pointed at the fixed `main` (`9040f84`) rather than burning a version. `13 §7`'s rule — never move the tag of a published Release — is unchanged | 12 §2.3, 13 §7 |
|
||||
Reference in new issue
Block a user