chore: bump quarry to v1.15.0 in marketplace#199
Conversation
There was a problem hiding this comment.
Pull request overview
Updates the Claude marketplace entry for punt-labs/quarry to the new release.
Changes:
- Bump the
quarryGit ref fromv1.14.0tov1.15.0 - Update the marketplace
versionfield from1.14.0to1.15.0
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
| "source": { | ||
| "source": "github", | ||
| "repo": "punt-labs/quarry", | ||
| "ref": "v1.14.0" | ||
| "ref": "v1.15.0" | ||
| }, | ||
| "description": "Local semantic search with automagic knowledge capture: /find, /ingest, /explain, /source, /quarry", | ||
| "version": "1.14.0", | ||
| "version": "1.15.0", | ||
| "author": { | ||
| "name": "Punt Labs", | ||
| "email": "hello@punt-labs.com" |
There was a problem hiding this comment.
🔴 This PR is missing a CHANGELOG entry for the quarry v1.14.0 → v1.15.0 bump, which is required by CLAUDE.md before merging. Add a 'Changed' entry under ## [Unreleased] in CHANGELOG.md (e.g., - quarry bumped to v1.15.0).
Extended reasoning...
What the bug is: CLAUDE.md states unambiguously: '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 the quarry plugin from v1.14.0 to v1.15.0 in the marketplace catalog — a direct user-facing change (users installing quarry via the marketplace will receive v1.15.0). The PR diff touches only marketplace.json and contains no CHANGELOG.md update.
The specific code path: The [Unreleased] section of CHANGELOG.md currently lists: beadle added at v0.3.0, an install.sh fix, beadle bumped to v0.7.0, and ethos bumped to v0.2.0. There is no quarry v1.15.0 entry. The PR diff confirms no CHANGELOG file was modified.
Why existing content does not prevent this: The CHANGELOG does have historic version-bump entries (beadle to v0.7.0, ethos to v0.2.0), but these are old entries, not from the recent bump PRs. The refutation notes that PRs #195–#198 (ethos v3.9.0, biff v1.10.0, quarry v1.14.0, beadle v0.15.0) also omitted CHANGELOG entries — and this is factually correct. However, CLAUDE.md explicitly forecloses that line of reasoning: 'There is no such thing as a pre-existing issue. If you see a problem… you fix it. Do not classify issues as pre-existing to justify ignoring them.' Prior omissions do not retroactively permit new omissions; each PR must meet the standard independently.
Impact: Per CLAUDE.md, this PR is not ready to merge in its current state. Users and maintainers rely on CHANGELOG to track what changed between installs; silently advancing quarry from v1.14.0 to v1.15.0 without a log entry breaks that contract.
How to fix: Add one line under ### Changed in CHANGELOG.md's ## [Unreleased] section:
- `quarry` bumped to v1.15.0
Step-by-step proof:
- Open
CHANGELOG.md— the[Unreleased]section contains no mention of quarry v1.15.0. - Open the PR diff — only
.claude-plugin/marketplace.jsonis modified;CHANGELOG.mdis not in the changed-files list. - Open
CLAUDE.mdline 36: 'If a PR changes user-facing behavior and the diff does not include a CHANGELOG entry, the PR is not ready to merge.' - Bumping
marketplace.jsonfromref: v1.14.0/version: 1.14.0toref: v1.15.0/version: 1.15.0directly changes what version marketplace consumers install — this is user-facing by any reasonable definition. - Conclusion: rule is violated, PR must add the CHANGELOG entry before merging.
Note
Low Risk
Low risk metadata-only change that updates the
quarryplugin reference/version in the marketplace manifest; no runtime logic is modified.Overview
Updates the marketplace manifest (
.claude-plugin/marketplace.json) to point thequarryplugin to releasev1.15.0by bumping both its gitrefand listedversionfrom1.14.0to1.15.0.Reviewed by Cursor Bugbot for commit 6f64722. Bugbot is set up for automated code reviews on this repo. Configure here.