From 71599462b014684be8a394d5cd4e3d419532e261 Mon Sep 17 00:00:00 2001 From: Focaxis Dev Date: Sun, 9 Aug 2026 14:03:32 +0800 Subject: [PATCH] docs: record v0.7.0 release completion --- docs/release-v0.7.0.md | 25 ++++++++++++------------- memory/impressions.jsonl | 3 ++- memory/open-loops/publish-v0.7.0.md | 25 +++++++++++++++---------- memory/summary.md | 4 ++-- 4 files changed, 31 insertions(+), 26 deletions(-) diff --git a/docs/release-v0.7.0.md b/docs/release-v0.7.0.md index a084bfa..9cda783 100644 --- a/docs/release-v0.7.0.md +++ b/docs/release-v0.7.0.md @@ -1,10 +1,10 @@ -# Deja Vu v0.7.0 Release Candidate +# Deja Vu v0.7.0 Release -v0.7.0 is the first release candidate whose public npm package includes the three-file starter kit and unified CLI. +v0.7.0 is the first public npm release that includes the three-file starter kit and unified CLI. ## Why this release matters -The repository reached v0.6.0, but npm `latest` remained at v0.1.0. That published package does not expose the `deja-vu` CLI, so the README's `npx @focaxisdev/deja-vu init` path cannot work until a new package is published. +Before v0.7.0, the repository had reached v0.6.0 while npm `latest` remained at v0.1.0. That published package did not expose the `deja-vu` CLI, so the README's `npx @focaxisdev/deja-vu init` path could not work. v0.7.0 closes that adoption gap and hardens the first-run experience for repos with existing project rules. @@ -43,15 +43,14 @@ Verify the packed file list contains: - `starter-kit/memory/impressions.jsonl` - all declared package binaries -## Publish sequence +## Published result -1. Merge the reviewed v0.7.0 changes. -2. Confirm npm authentication with `npm whoami`. -3. Publish with `npm publish --access public`. -4. Verify `npm view @focaxisdev/deja-vu version bin --json` reports v0.7.0 and all four binaries. -5. Test `npx @focaxisdev/deja-vu init --dry-run` from an empty temporary directory. -6. Create the v0.7.0 GitHub release from the verified commit. -7. Update the GitHub description, topics, and social preview. -8. Use the prepared launch copy only after the public quick start succeeds. +Completed on 2026-08-09: -Do not publish, tag, or announce from an unverified working tree. +- PR #9 was squash-merged to `main` as commit `32ce3c5`. +- [`@focaxisdev/deja-vu@0.7.0`](https://www.npmjs.com/package/@focaxisdev/deja-vu/v/0.7.0) was published publicly and assigned npm `latest`. +- Registry metadata reports all four package binaries. +- A fresh public-registry `npx @focaxisdev/deja-vu@0.7.0 init --dry-run --json` run returned `ok: true` and `ready: true`. +- [GitHub Release v0.7.0](https://github.com/focaxisdev/deja-vu/releases/tag/v0.7.0) was published from the verified merge commit. + +Prepared promotion copy remains in `docs/launch-copy.md` for a separate launch step. diff --git a/memory/impressions.jsonl b/memory/impressions.jsonl index 1932d27..f82ffc9 100644 --- a/memory/impressions.jsonl +++ b/memory/impressions.jsonl @@ -4,4 +4,5 @@ {"schema_version":1,"id":"cli-helper-scope","scope":"project:deja-vu","title":"CLI is an optional helper","keywords":["cli","init","doctor","explain","merge-agents","optional","helper"],"aliases":["deja-vu-cli"],"record_path":"memory/summary.md","updated":"2026-08-09","weight":0.8,"status":"active"} {"schema_version":1,"id":"safety-privacy-boundary","scope":"project:deja-vu","title":"Safety privacy boundaries","keywords":["safety","privacy","secrets","PII","transcripts","noise"],"aliases":["memory-safety"],"record_path":"memory/summary.md","updated":"2026-05-17","weight":0.85,"status":"active"} {"schema_version":1,"id":"v060-release-readiness","scope":"project:deja-vu","title":"v0.6.0 release readiness","keywords":["v0.6.0","release","readiness","checklist","candidate"],"aliases":["release-candidate"],"record_path":"memory/summary.md","updated":"2026-08-09","weight":0.4,"status":"superseded","superseded_by":"v070-npm-release-gap"} -{"schema_version":1,"id":"v070-npm-release-gap","scope":"project:deja-vu","title":"Publish and verify the first CLI-capable npm release","keywords":["v0.7.0","npm","publish","npx","latest","cli","release"],"aliases":["npm-release-gap","cli-release"],"record_path":"memory/open-loops/publish-v0.7.0.md","updated":"2026-08-09","weight":0.95,"status":"active"} +{"schema_version":1,"id":"v070-npm-release-gap","scope":"project:deja-vu","title":"Publish and verify the first CLI-capable npm release","keywords":["v0.7.0","npm","publish","npx","latest","cli","release"],"aliases":["npm-release-gap","cli-release"],"record_path":"memory/open-loops/publish-v0.7.0.md","updated":"2026-08-09","weight":0.4,"status":"superseded","superseded_by":"v070-release-complete"} +{"schema_version":1,"id":"v070-release-complete","scope":"project:deja-vu","title":"v0.7.0 public release is live and verified","keywords":["v0.7.0","npm","published","npx","latest","cli","github-release"],"aliases":["v070-released","cli-release-live"],"record_path":"memory/summary.md","updated":"2026-08-09","weight":0.85,"status":"active"} diff --git a/memory/open-loops/publish-v0.7.0.md b/memory/open-loops/publish-v0.7.0.md index ea1fd93..3b6e2ad 100644 --- a/memory/open-loops/publish-v0.7.0.md +++ b/memory/open-loops/publish-v0.7.0.md @@ -1,16 +1,17 @@ --- id: publish-v0.7.0 title: Publish and verify Deja Vu v0.7.0 -status: active +status: archived scope: project:deja-vu updated: 2026-08-09 +closed: 2026-08-09 --- # Publish and Verify Deja Vu v0.7.0 ## Why it matters -npm `latest` is v0.1.0 and does not include the unified `deja-vu` CLI. The public quick start remains broken until a package containing the current starter kit and binaries is published. +npm `latest` was v0.1.0 and did not include the unified `deja-vu` CLI, leaving the public quick start unusable. ## Owner @@ -20,14 +21,18 @@ Repository maintainer. 2026-08-09. -## Next trigger +## Resolution + +Resolved on 2026-08-09: -After the v0.7.0 pull request is reviewed and merged: +- PR #9 was squash-merged to `main` as commit `32ce3c5`. +- `@focaxisdev/deja-vu@0.7.0` was published publicly with npm `latest` pointing to v0.7.0. +- Registry metadata exposes `deja-vu`, `deja-vu-scan-memory`, `deja-vu-lint-memory`, and `deja-vu-feedback-report`. +- A fresh public-registry `npx ... init --dry-run --json` returned `ok: true` and `ready: true`. +- GitHub Release `v0.7.0` was published from the verified merge commit. -1. run the clean release verification in `docs/release-v0.7.0.md` -2. publish v0.7.0 to npm with public access -3. verify package version, bin metadata, and a fresh `npx ... init --dry-run` -4. create the matching GitHub release -5. update repository metadata and begin the prepared launch sequence +The prepared launch copy remains available for a separately authorized promotion step. + +## Next trigger -Do not announce the quick start before the public package smoke test passes. +None. Keep this record archived; track any future release or promotion work in a new open-loop record. diff --git a/memory/summary.md b/memory/summary.md index 8f2c528..c4cba92 100644 --- a/memory/summary.md +++ b/memory/summary.md @@ -34,11 +34,11 @@ v0.7.0 closes the gap between the repository story and the installable product: - Package verification installs the built tarball and runs its CLI. - Local Markdown links are validated in CI. -As of 2026-08-09, npm `latest` is still v0.1.0 and does not expose the unified CLI. Do not launch the `npx @focaxisdev/deja-vu init` path until v0.7.0 is published and verified. +Released on 2026-08-09, npm `latest` now resolves to v0.7.0 and exposes the unified CLI plus all four declared binaries. A fresh public-registry `npx @focaxisdev/deja-vu@0.7.0 init --dry-run --json` run returned `ok: true` and `ready: true`. The matching GitHub release points to verified merge commit `32ce3c5`. ## Open loops -- [Publish and verify v0.7.0](./open-loops/publish-v0.7.0.md) +- No v0.7.0 release blockers remain. ## Boundaries