Skip to content
Merged
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
4 changes: 2 additions & 2 deletions .claude-plugin/marketplace.json
Original file line number Diff line number Diff line change
Expand Up @@ -132,16 +132,16 @@
},
{
"name": "quarry",
"source": {
"source": "github",
"repo": "punt-labs/quarry",
"ref": "v1.13.0"
"ref": "v1.14.0"
},
"description": "Local semantic search with automagic knowledge capture: /find, /ingest, /explain, /source, /quarry",
"version": "1.13.0",
"version": "1.14.0",
Comment on lines +138 to +141
Copy link

Copilot AI Apr 18, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a user-facing marketplace catalog change (plugin version bump). Per CLAUDE.md, PRs that change user-facing behavior must include a CHANGELOG.md entry under ## [Unreleased]; please add an entry describing the quarry bump before merge.

Copilot uses AI. Check for mistakes.
"author": {
"name": "Punt Labs",
"email": "hello@punt-labs.com"

Check failure on line 144 in .claude-plugin/marketplace.json

View check run for this annotation

Claude / Claude Code Review

Missing CHANGELOG entry for quarry v1.14.0 bump

This PR bumps quarry from v1.13.0 to v1.14.0 but is missing a required CHANGELOG entry. Per CLAUDE.md: 'If a PR changes user-facing behavior and the diff does not include a CHANGELOG entry, the PR is not ready to merge.' Add a line like '- quarry bumped to v1.14.0' under the [Unreleased] Changed section in CHANGELOG.md before merging.
Comment on lines 135 to 144
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔴 This PR bumps quarry from v1.13.0 to v1.14.0 but is missing a required CHANGELOG entry. Per CLAUDE.md: 'If a PR changes user-facing behavior and the diff does not include a CHANGELOG entry, the PR is not ready to merge.' Add a line like '- quarry bumped to v1.14.0' under the [Unreleased] Changed section in CHANGELOG.md before merging.

Extended reasoning...

What the bug is: CLAUDE.md contains an explicit merge gate: 'If a PR changes user-facing behavior and the diff does not include a CHANGELOG entry, the PR is not ready to merge.' This PR bumps quarry from v1.13.0 to v1.14.0 in .claude-plugin/marketplace.json but the diff contains no corresponding CHANGELOG.md entry.

The specific code path: The only file changed in this PR is .claude-plugin/marketplace.json, updating ref from "v1.13.0" to "v1.14.0" and version from "1.13.0" to "1.14.0" (lines 135–144). CHANGELOG.md is untouched.

Why existing code doesn't prevent it: There is no automated CI check enforcing CHANGELOG entries — this is a documented manual convention. CLAUDE.md says entries must be written in the PR branch before merge, not retroactively.

The impact: Users who install quarry from the marketplace catalog will receive v1.14.0 instead of v1.13.0 with no documented explanation of what changed. This violates the project's transparency standard and CLAUDE.md explicitly classifies this as a merge blocker.

How to fix it: Add a single line to CHANGELOG.md under the [Unreleased]Changed section:

- quarry bumped to v1.14.0

This follows the exact pattern already established for other plugins: 'beadle bumped to v0.7.0', 'ethos bumped to v0.2.0'.

Step-by-step proof:

  1. CLAUDE.md states: 'If a PR changes user-facing behavior and the diff does not include a CHANGELOG entry, the PR is not ready to merge.'
  2. A marketplace plugin version bump is user-facing: any user running the marketplace installer will receive quarry v1.14.0 instead of v1.13.0.
  3. The PR diff shows only .claude-plugin/marketplace.json changed — no CHANGELOG.md modification.
  4. The CHANGELOG.md [Unreleased] section already contains entries for other bumps, confirming the convention applies.
  5. CLAUDE.md also states 'There is no such thing as a pre-existing issue,' so the fact that prior PRs (chore: bump ethos to v3.8.0 in marketplace #193chore: bump biff to v1.10.0 in marketplace #196) also skipped CHANGELOG entries does not excuse this omission.
  6. Conclusion: the PR violates the documented merge gate and must not be merged until a CHANGELOG entry is added.

},
"keywords": [
"search",
Expand Down
Loading