docs(release): Record 8.2.0 publication
Update the maintainer and user walkthroughs so they reflect the completed 8.2.0 release publication instead of the pre-release ready state. Capture the final PR merge set, issue closure state, and the exact release commands that were executed on main.
This commit is contained in:
@@ -2,7 +2,7 @@
|
||||
|
||||
## Overview
|
||||
|
||||
This walkthrough captures the maintainer-side documentation and release preparation work for **v8.2.0** after the 2026-03-18 maintenance sweep.
|
||||
This walkthrough captures the maintainer-side documentation and release publication work for **v8.2.0** after the 2026-03-18 maintenance sweep.
|
||||
|
||||
## Changes Verified
|
||||
|
||||
@@ -31,7 +31,8 @@ This walkthrough captures the maintainer-side documentation and release preparat
|
||||
|
||||
- **Issue #344**: Corrected `.claude-plugin/marketplace.json` to use `source: "./"` and added a regression test for the Claude Code marketplace entry
|
||||
- **.github/MAINTENANCE.md**: Documented the maintainer flow for fork-gated workflows and stale PR metadata
|
||||
### 4. Release protocol to run
|
||||
|
||||
### 4. Release protocol executed
|
||||
|
||||
- `npm run release:preflight`
|
||||
- `npm run security:docs`
|
||||
@@ -42,4 +43,4 @@ This walkthrough captures the maintainer-side documentation and release preparat
|
||||
## Expected Outcome
|
||||
|
||||
- Documentation, changelog, and generated metadata all agree on the release state.
|
||||
- The repository is ready for the `v8.2.0` tag and GitHub release.
|
||||
- The repository published the `v8.2.0` tag and GitHub release successfully.
|
||||
|
||||
@@ -2,10 +2,16 @@
|
||||
|
||||
- Fixed issue `#344` by correcting `.claude-plugin/marketplace.json` so the marketplace plugin entry uses `source: "./"` instead of `"."`, matching Claude Code's relative-path schema requirement for marketplace entries.
|
||||
- Added `tools/scripts/tests/claude_plugin_marketplace.test.js` and wired it into the local test suite so invalid marketplace `source` paths fail fast in CI/maintainer verification.
|
||||
- Merged PRs `#333`, `#336`, `#338`, `#343`, `#340`, and `#334` via GitHub squash merge after maintainer refresh of forked workflows and PR metadata.
|
||||
- Merged PRs `#333`, `#336`, `#338`, `#343`, `#340`, `#334`, and `#345` via GitHub squash merge after maintainer refresh of forked workflows and PR metadata.
|
||||
- Closed PR `#337` and PR `#342` as superseded by `#338`, then closed issue `#339` manually after confirming the accepted fix path; issue `#335` auto-closed from the merged PR body.
|
||||
- Left issue `#344` open with a triage comment, and left PR `#341` open with a blocking review comment because the submitted skill content is corrupted even though CI is green.
|
||||
- Closed issue `#344` with a follow-up comment after shipping the plugin marketplace fix on `main`, and left PR `#341` open with a blocking review comment because the submitted skill content is corrupted even though CI is green.
|
||||
- Documented a new maintainer edge case in `.github/MAINTENANCE.md`: forked runs in `action_required`, `pr-policy` failures caused by stale PR bodies, the REST API fallback when `gh pr edit` fails with the Projects Classic GraphQL error, and the need to `close`/`reopen` a PR when a plain rerun does not pick up updated metadata.
|
||||
- Refreshed the release-facing docs for `8.2.0` across `README.md`, `docs/users/getting-started.md`, `docs/users/walkthrough.md`, and `CHANGELOG.md`.
|
||||
- Published release `v8.2.0` on `main` with:
|
||||
- `npm run release:preflight`
|
||||
- `npm run security:docs`
|
||||
- `npm run release:prepare -- 8.2.0`
|
||||
- `npm run release:publish -- 8.2.0`
|
||||
|
||||
# Maintenance Walkthrough - 2026-03-17
|
||||
|
||||
|
||||
Reference in New Issue
Block a user