Skip to content

Commit 3f85e9d

Browse files
focaxisdevfocaxisdev
authored
docs: record v0.7.0 release completion (#10)
Archive the completed release open loop and update project memory and release documentation with the verified npm and GitHub release state.
1 parent 32ce3c5 commit 3f85e9d

4 files changed

Lines changed: 31 additions & 26 deletions

File tree

‎docs/release-v0.7.0.md‎

Lines changed: 12 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
1-
# Deja Vu v0.7.0 Release Candidate
1+
# Deja Vu v0.7.0 Release
22

3-
v0.7.0 is the first release candidate whose public npm package includes the three-file starter kit and unified CLI.
3+
v0.7.0 is the first public npm release that includes the three-file starter kit and unified CLI.
44

55
## Why this release matters
66

7-
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.
7+
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.
88

99
v0.7.0 closes that adoption gap and hardens the first-run experience for repos with existing project rules.
1010

@@ -43,15 +43,14 @@ Verify the packed file list contains:
4343
- `starter-kit/memory/impressions.jsonl`
4444
- all declared package binaries
4545

46-
## Publish sequence
46+
## Published result
4747

48-
1. Merge the reviewed v0.7.0 changes.
49-
2. Confirm npm authentication with `npm whoami`.
50-
3. Publish with `npm publish --access public`.
51-
4. Verify `npm view @focaxisdev/deja-vu version bin --json` reports v0.7.0 and all four binaries.
52-
5. Test `npx @focaxisdev/deja-vu init --dry-run` from an empty temporary directory.
53-
6. Create the v0.7.0 GitHub release from the verified commit.
54-
7. Update the GitHub description, topics, and social preview.
55-
8. Use the prepared launch copy only after the public quick start succeeds.
48+
Completed on 2026-08-09:
5649

57-
Do not publish, tag, or announce from an unverified working tree.
50+
- PR #9 was squash-merged to `main` as commit `32ce3c5`.
51+
- [`@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`.
52+
- Registry metadata reports all four package binaries.
53+
- A fresh public-registry `npx @focaxisdev/deja-vu@0.7.0 init --dry-run --json` run returned `ok: true` and `ready: true`.
54+
- [GitHub Release v0.7.0](https://github.com/focaxisdev/deja-vu/releases/tag/v0.7.0) was published from the verified merge commit.
55+
56+
Prepared promotion copy remains in `docs/launch-copy.md` for a separate launch step.

‎memory/impressions.jsonl‎

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,4 +4,5 @@
44
{"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"}
55
{"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"}
66
{"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"}
7-
{"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"}
7+
{"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"}
8+
{"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"}

‎memory/open-loops/publish-v0.7.0.md‎

Lines changed: 15 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,17 @@
11
---
22
id: publish-v0.7.0
33
title: Publish and verify Deja Vu v0.7.0
4-
status: active
4+
status: archived
55
scope: project:deja-vu
66
updated: 2026-08-09
7+
closed: 2026-08-09
78
---
89

910
# Publish and Verify Deja Vu v0.7.0
1011

1112
## Why it matters
1213

13-
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.
14+
npm `latest` was v0.1.0 and did not include the unified `deja-vu` CLI, leaving the public quick start unusable.
1415

1516
## Owner
1617

@@ -20,14 +21,18 @@ Repository maintainer.
2021

2122
2026-08-09.
2223

23-
## Next trigger
24+
## Resolution
25+
26+
Resolved on 2026-08-09:
2427

25-
After the v0.7.0 pull request is reviewed and merged:
28+
- PR #9 was squash-merged to `main` as commit `32ce3c5`.
29+
- `@focaxisdev/deja-vu@0.7.0` was published publicly with npm `latest` pointing to v0.7.0.
30+
- Registry metadata exposes `deja-vu`, `deja-vu-scan-memory`, `deja-vu-lint-memory`, and `deja-vu-feedback-report`.
31+
- A fresh public-registry `npx ... init --dry-run --json` returned `ok: true` and `ready: true`.
32+
- GitHub Release `v0.7.0` was published from the verified merge commit.
2633

27-
1. run the clean release verification in `docs/release-v0.7.0.md`
28-
2. publish v0.7.0 to npm with public access
29-
3. verify package version, bin metadata, and a fresh `npx ... init --dry-run`
30-
4. create the matching GitHub release
31-
5. update repository metadata and begin the prepared launch sequence
34+
The prepared launch copy remains available for a separately authorized promotion step.
35+
36+
## Next trigger
3237

33-
Do not announce the quick start before the public package smoke test passes.
38+
None. Keep this record archived; track any future release or promotion work in a new open-loop record.

‎memory/summary.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -34,11 +34,11 @@ v0.7.0 closes the gap between the repository story and the installable product:
3434
- Package verification installs the built tarball and runs its CLI.
3535
- Local Markdown links are validated in CI.
3636

37-
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.
37+
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`.
3838

3939
## Open loops
4040

41-
- [Publish and verify v0.7.0](./open-loops/publish-v0.7.0.md)
41+
- No v0.7.0 release blockers remain.
4242

4343
## Boundaries
4444

0 commit comments

Comments
 (0)