Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view

This file was deleted.

7 changes: 0 additions & 7 deletions .changes/evals/fix-17262-eval-root-search-d9011832.md

This file was deleted.

This file was deleted.

This file was deleted.

This file was deleted.

This file was deleted.

This file was deleted.

17 changes: 0 additions & 17 deletions .changes/plugin-profiles/feat-plugin-profiles-reset-14c36134.md

This file was deleted.

This file was deleted.

13 changes: 0 additions & 13 deletions .changes/source-control/fix-read-back-pin-rung-7c1e4d20.md

This file was deleted.

This file was deleted.

This file was deleted.

8 changes: 8 additions & 0 deletions docs/conventions/pr-pipeline/CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,13 @@
# Changelog for the PR pipeline convention

## [10.17.0] - 2026-11-19

### Changed

- A vendored-copy upstream-drift issue (github-actions[bot] wrote it, nobody else last edited it, its title is `Upstream drift: <id>` and its first body line is the filer's vendored-copy lead) reaches the issue lane with no owner step, as a hex-pin drift issue does (owner direction 2026-11-18). `driftIssue` in `admit.mjs` decides both kinds at every author gate, and `trustedDriftSpec` gives each its own fixed spec: the vendored one runs the skill's update procedure found from the id's row in `scripts/upstream-drift-vendored-report.sh`, folds the changes into the skill's distilled files and adds a changelog fragment, never a `version` or `CHANGELOG.md` change. pr-verify and the merge gate count it only for a pull request whose files are all markdown under that plugin's `skills/`, markdown, `.jsonc` or `LICENSE` files in a `vendor/` baseline there, or fragments directly under its `.changes/`, with no `scripts`, `hooks`, `lib`, `.claude-plugin`, `.mcp.json` or `evals` path segment. A `SKILL.md` outside `vendor/` counts only as a modification whose frontmatter changes nothing but its `upstream-version`, `upstream-sha` and `synced` values and whose `` !` `` lines stay the same, with no fenced ```` ```! ```` block, read at the merge base and the head (`skillTextSafe`). A skill's `actions/update.md`, and the plugin's `update` skill outside `vendor/`, never count: a change to the update procedure comes from a person. It is trusted only when every row for the id carries `files-only` (an apply mode that rewrites vendored files and installs no package), so a row whose update runs `npm install` (firecrawl, context7) is not, and the spec forbids any package install.
- `scripts/upstream-drift-vendored-report.sh` joins the merge hold floor (`enforcement`), as `docs/upstream/**` is: its rows now decide which plugin a vendored drift issue's pull request may change.
- The drift filer runs daily instead of weekly.

## [10.16.0] - 2026-11-19

### Added
Expand Down
2 changes: 1 addition & 1 deletion plugins/evals/.claude-plugin/plugin.json
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@
"name": "Melodic Software",
"email": "info@melodicsoftware.com"
},
"version": "0.20.3",
"version": "0.20.4",
"license": "MIT",
"userConfig": {
"max_cost_usd": {
Expand Down
6 changes: 6 additions & 0 deletions plugins/evals/CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,11 @@
# Changelog: evals

## [0.20.4] - 2026-11-19

### Changed

- `run-validity.py`'s `permission denials` check no longer fails a finished without-arm run for a denied `Grep` or `Glob` whose `path` is that run's own eval root (the sandbox holding its `out/trace.jsonl`): the arm lacks the plugin and looks for it in its own folder. That denial is now a warning, and the verdict line, which is all CI keeps in `validity.txt`, names each excused call with its tool, root and pattern. A `Glob` pattern that is rooted or holds `..`, a path under or above the root, another tool, a with-arm run and an unfinished run still fail ([#17262](https://github.com/melodic-software/claude-code-plugins/issues/17262)).

## [0.20.3] - 2026-11-19

### Fixed
Expand Down
2 changes: 1 addition & 1 deletion plugins/playwright/.claude-plugin/plugin.json
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@
"name": "Melodic Software",
"email": "info@melodicsoftware.com"
},
"version": "2.0.21",
"version": "2.0.22",
"license": "MIT AND Apache-2.0",
"userConfig": {
"demo_style": {
Expand Down
8 changes: 8 additions & 0 deletions plugins/playwright/CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,14 @@
All notable changes to the `playwright` plugin are documented here. Format follows
[Keep a Changelog](https://keepachangelog.com/en/1.1.0/); this plugin uses semantic versioning.

## [2.0.22] - 2026-11-19

### Changed

- The `update` action's safety table states the current rule: the marketplace's daily drift workflow runs `--check` and files an `Upstream drift: playwright/playwright` issue when upstream moves, the issue lane runs `--apply` and the reference integration, and the change merges through a reviewed pull request. It no longer says nothing runs on a schedule. The README says the check runs daily and that the issue lane works the issue.
- The update action's finishing steps and `update.sh --apply` mark the global `npm install -g @playwright/cli@latest` upgrade as a step a person runs; the upstream-drift issue lane never runs it.
- The update action's finishing steps and `update.sh --apply` name a changelog fragment as the release record, since the plugin is in fragment mode, in place of a `plugin.json` version bump.

## [2.0.21] - 2026-11-19

### Changed
Expand Down
2 changes: 1 addition & 1 deletion plugins/plugin-profiles/.claude-plugin/plugin.json
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@
"name": "Melodic Software",
"email": "info@melodicsoftware.com"
},
"version": "0.8.0",
"version": "0.9.0",
"license": "MIT",
"types": "./types/index.d.ts",
"keywords": [
Expand Down
16 changes: 16 additions & 0 deletions plugins/plugin-profiles/CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,22 @@
All notable changes to the `plugin-profiles` plugin are documented here. Format follows
[Keep a Changelog](https://keepachangelog.com/en/1.1.0/); this plugin uses semantic versioning.

## [0.9.0] - 2026-11-19

### Added

- `profiles.mjs reset` puts every settings file a profile changed on the machine back, user settings included, behind one preview and one yes; a reset stopped part way finishes on the next run. It reads a record only from a home that can hold it, refuses a write that no longer matches the preview passed with `--preview-id`, and exits 3 when it wrote what it could and named each file it skipped. A moved repository with profiles applied before and after the move goes back one layer per reset, newest first, each run writing a file from one record only; a run that leaves an older record waiting exits 3 and says to run reset again, and after the last layer the file holds what it held before the first apply. A no to the one question keeps the recorded files and still asks each file's own question (`--keep-recorded` for a caller). A file changed by hand after a reset was stopped before its write keeps its record and gets its own yes (`--finish-cut-off`, `--keep-cut-off`), which puts back only the entries still at the profile's values, counting an entry an unfinished switch still owes until it is back at its value before the profile.
- The `/plugin-profile` picker has a **Reset** row under No profile, and the profile skill has a reset action; both show the same preview and ask before writing, and a folder without a record changes only on a yes for that folder. Each per-file question in `reset --dry-run --json` carries its answers' labels and flags and a recommended answer with a one-sentence reason (`ask.recommend`; `questionRecommend` for the one question); the picker shows it as a line before the question and the skill marks that answer `(Recommended)`.- Reset notes the bytes it left in each file it put back, so a later reset does not offer that file's own entries for removal while it is unchanged; an edit or an apply ends that.

### Changed

- Every question the `/plugin-profile` picker and the profile skill ask lists the answer that changes nothing first (Cancel, Keep, No), so the picker pre-selects it, the apply, switch and clear confirms included; Esc is that answer.
- A one-session file also names each installed plugin of every other marketplace some profile governs, at its value at launch, so a reset or another profile elsewhere never changes that session's plugins; a later `/plugin` toggle of such a plugin reaches only sessions started after it.

### Fixed

- The `/plugin-profile` picker's second write after a reload runs `apply --finish-pending`, which writes only while the folder's switch is still pending, so it never writes back a profile cleared or reset since, including one cleared or reset while it lists the installed plugins: it saves its record only while the pending record it read is unchanged.

## [0.8.0] - 2026-11-19

### Added
Expand Down
2 changes: 1 addition & 1 deletion plugins/source-control/.claude-plugin/plugin.json
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@
"name": "Melodic Software",
"email": "info@melodicsoftware.com"
},
"version": "13.0.2",
"version": "13.1.0",
"license": "MIT",
"keywords": [
"git",
Expand Down
16 changes: 16 additions & 0 deletions plugins/source-control/CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,22 @@
All notable changes to the `source-control` plugin are documented here. Format follows
[Keep a Changelog](https://keepachangelog.com/en/1.1.0/); this plugin uses semantic versioning.

## [13.1.0] - 2026-11-19

### Changed

- The babysit merge gate trusts a vendored-copy upstream-drift issue as it trusts a hex-pin one: github-actions[bot] wrote it, nobody else last edited it, its title is `Upstream drift: <id>` and its first body line is the filer's vendored-copy lead for that id. It counts only for a pull request whose changed files, renames' old paths included, are markdown under the `skills/` of the plugin that id's row in the default branch's `scripts/upstream-drift-vendored-report.sh` names, markdown, `.jsonc` or `LICENSE` files in a `vendor/` baseline there, or fragments directly under that plugin's `.changes/`, with no `scripts`, `hooks`, `lib`, `.claude-plugin`, `.mcp.json` or `evals` path segment, and whose `SKILL.md` files outside `vendor/` change no frontmatter but the sync stamps and no `` !` `` line or fenced ```` ```! ```` block, and that touch no skill's `actions/update.md` and no file of the plugin's `update` skill outside `vendor/`, matching pr-verify's `driftSpec`. An id no row names, that two plugins claim, or with a row lacking the `files-only` mark (its update may install a package) is not trusted.

### Fixed

- lift a read-back record on a C2 or C3 merge pin

The merge policy's read-back check matched only a pin comment with no
rung, so a pull request merged at rung C2 or C3, whose pin carries
`rung=C2` or `rung=C3`, never read back, and its read-back record could
never lift. The pin pattern now accepts the optional rung, as the
post-merge reader already does.

## [13.0.2] - 2026-11-19

### Fixed
Expand Down
Loading