59 lines
3.5 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

# SLICE 7 — Release
> **State-saving rule:** update this file immediately after EVERY completed task (tick the checkbox, update Status and Resume notes) and whenever pausing for input — automatically, without being asked. State on disk must always match reality.
## Status
**COMPLETE** (2026-07-18) — v0.7.0 published to npm (registry confirms
`latest: 0.7.0`) and manual sanity-open in Joplin desktop signed off by user.
All seven slices DONE. Nothing outstanding.
**Release-cut decision made with user (2026-07-18): ONE release, tagged 0.7.0.**
Rationale: gantt is woven through all four shared files (73 refs — 33 webview,
19 types.ts, 12 renderer, 9 index.ts), so a gantt-free 0.6.0 would be error-prone
surgery on an intermediate nobody tested; the 2026-07-18 E2E sign-off was on the
combined state. So npm goes 0.5.0 → 0.7.0 (0.6.0 not separately published); the
CHANGELOG keeps BOTH the 0.7.0 (gantt) and 0.6.0 (notebook/scope) entries as a
documentation split. Version bumped to 0.7.0 in src/manifest.json + package.json.
## Tasks
- [x] Decide with user: **ONE release, tagged 0.7.0** (see Status). CHANGELOG keeps
both 0.6.0 + 0.7.0 entries as documentation.
- [x] Bump `version` in BOTH `src/manifest.json` and `package.json` → 0.7.0 (match).
- [x] CHANGELOG.md entry finalized (0.7.0 at top, both feature entries present —
written in SLICE6).
- [x] **Archived existing publish/*.jpl first** — predist (scripts/archive-jpl.sh)
moved it to build-archive/com.victorwiebe...-0.7.0-20260718-115536.jpl
(no overwrite; three 0.5.0 archives preserved). NB the archive filename is
stamped with the *current* package.json version (0.7.0), not the version the
archived jpl was built at — cosmetic, git-ignored dir, left as-is.
- [x] `npm run dist` — GREEN. jest 140/140 first. New publish/*.jpl (156 KB)
embeds version 0.7.0 (verified in publish/*.json).
- [x] Sanity-open the .jpl in Joplin desktop — **DONE** (2026-07-18): user
completed manual visual check, signed off.
Path: publish/com.victorwiebe.joplin.plugin.gtd-calendar.jpl
- [x] `npm publish`**DONE** (2026-07-18): user re-logged in and published.
Registry (https://registry.npmjs.org/) confirms `latest: 0.7.0`.
- [x] **Committed + pushed to Gitea** (2026-07-18): commit 187fd34
"v0.7.0: Gantt chart, notebook targeting & profile-wide scope" (30 files,
+2300/-40), pushed 9780d95..187fd34 master->master. Per user: `.npmrc`
(browser=true) was included. workspace planning files and build-archive/ correctly
excluded from the release commit. NB: no git tag created — tagging was abandoned after 0.3.0 (0.4.0
& 0.5.0 untagged); left consistent with recent practice.
- [x] Mark all SLICE files DONE; summarize outcome here. **DONE**
SLICE16 already COMPLETE; SLICE7 now COMPLETE (this file).
## Outcome
2026-07-18: **v0.7.0 shipped.** The full slice effort (notebook targeting,
profile-wide `scope: all`, and the gtd-gantt view) is released as a single
0.7.0 (0.6.0 documented in CHANGELOG but never separately published, per the
one-release decision). Final state:
- Version 0.7.0 in src/manifest.json + package.json (match).
- Committed + pushed to Gitea (commit 187fd34, master).
- `npm run dist` green, 140/140 tests, clean 0.7.0 jpl (embedded version verified).
- **Published to npm — registry confirms `latest: 0.7.0`.**
- Manual sanity-open in Joplin desktop signed off by user.
All seven slices DONE. No follow-ups outstanding.
## Resume notes
Nothing to resume — SLICE17 all COMPLETE, v0.7.0 live on npm.