chore(changelog): retire CHANGELOG.md as a dependency
The update dialog (server and desktop) now reads changelog/index.json and renders title, intro and groups; the release workflow builds the GitHub Release body and name from changelog/<version>.md; oc-dev, the issue-intake agent, AGENTS.md and the changelog skill no longer point at the file. CHANGELOG.md stays as a legacy copy for installs up to 1.22.1, which fetch it for update notes. The generator refreshes it while it exists and never recreates it, so deleting it after 2026-09-19 retires it for good. Generated outputs hold released versions only, so editing unreleased.md never makes them stale: agents write that file and nothing else, and oc-dev create-release does the generation. Claude-Session: https://claude.ai/code/session_01VqV56Hez25hTxXH4ipJfzH
This commit is contained in:
@@ -42,7 +42,7 @@ Shared contracts must define intentional behavior for every applicable runtime:
|
||||
- Do not add dependencies unless explicitly requested.
|
||||
- Never add or log secrets, bearer tokens, pairing credentials, or sensitive user data.
|
||||
- Keep changes minimal and preserve unrelated worktree changes.
|
||||
- Release notes are the maintainer's release-time work: they get written once, as one story, in `changelog/unreleased.md` when the maintainer asks to update the changelog. Until that request, treat `changelog/` as read-only — a fix, feature, or merged PR lands without a changelog line. `CHANGELOG.md`, `packages/vscode/CHANGELOG.md`, and `changelog/index.json` are generated from `changelog/*.md` by `bun run changelog:build`; never edit them by hand.
|
||||
- Release notes are the maintainer's release-time work: they get written once, as one story, in `changelog/unreleased.md` when the maintainer asks to update the changelog. Until that request, treat `changelog/` as read-only — a fix, feature, or merged PR lands without a changelog line. `packages/vscode/CHANGELOG.md` and `changelog/index.json` are generated from `changelog/*.md` by `oc-dev create-release`, and `CHANGELOG.md` is a legacy copy for older installs: never edit or regenerate any of them; an agent's only changelog output is `changelog/unreleased.md`.
|
||||
- Enforce security and correctness in core/runtime logic, not only UI visibility or prompts.
|
||||
- Keep entrypoints and bridges thin; place domain logic in focused owning modules.
|
||||
- Update owning documentation when module ownership, contracts, or invariants change.
|
||||
@@ -101,7 +101,7 @@ process violation.
|
||||
| Settings UI, settings dialogs, configuration surfaces, or settings search | `settings-ui-patterns` |
|
||||
| Sortable or drag-to-reorder behavior, especially `@dnd-kit` and touch/wrapping layouts | `drag-to-reorder` |
|
||||
| iOS Simulator build, launch, preview, gestures, or `serve-sim` control | `serve-sim` |
|
||||
| The maintainer explicitly asks to update the changelog (main app or VS Code extension) — the only time either CHANGELOG is edited | `changelog-authoring` |
|
||||
| The maintainer explicitly asks to update the changelog (main app or VS Code extension) — the only time `changelog/unreleased.md` is edited | `changelog-authoring` |
|
||||
| Creating or editing skills, `AGENTS.md`, or docs reached through agent instructions/context pointers | `writing-for-agents` |
|
||||
| Reviewing a single pull request or drafting a PR verdict/close/review comment | `pr-review` |
|
||||
| Triaging, cleaning up, or batch-processing the open PR queue | `triage-prs` |
|
||||
|
||||
Reference in New Issue
Block a user