Skip to content

chore: bump versions - #624

Merged
danielraffel merged 2 commits into
mainfrom
fix/plugin-manifest-duplicates
Apr 22, 2026
Merged

chore: bump versions#624
danielraffel merged 2 commits into
mainfrom
fix/plugin-manifest-duplicates

Conversation

@danielraffel

Copy link
Copy Markdown
Collaborator

Automated by shipyard pr.

Claude Code auto-loads ./hooks/hooks.json from plugins, so manifest.hooks
pointing at the same path caused a duplicate-file load error. The plugin's
.mcp.json entry was also being skipped at load time because the project-
level .mcp.json already registers the pulp MCP server with the same
command, and the relative ./build/tools/mcp/pulp-mcp path only resolves
inside this repo anyway.

Resolves the two errors surfaced by /reload-plugins.
Automated by `shipyard pr`.
@codecov

codecov Bot commented Apr 22, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@github-actions

Copy link
Copy Markdown

Diff coverage (required)

Diff coverage threshold: 75% (required).

diff-cover report

Diff: origin/main...HEAD, staged and unstaged changes

No lines with coverage information in this diff.

See coverage.md for how to interpret this number and the full Phase 1 → Phase 3 roadmap.

Per-tier diff coverage (#566 Phase 2)

Tier Target Diff coverage Touched lines Result
audio-critical 80% — (no touched lines) 0
user-facing 70% — (no touched lines) 0
infrastructure 50% — (no touched lines) 0

All touched tiers meet their per-tier floors.

@danielraffel
danielraffel merged commit 47e6aeb into main Apr 22, 2026
18 checks passed
danielraffel added a commit that referenced this pull request Apr 22, 2026
* chore: bump Shipyard pin v0.22.9 → v0.25.0

Pulls in two semantic changes that directly affect pulp's ship flow:

1. v0.24.0 (Shipyard #151) — `shipyard pr` now walks past the
   mechanical "chore: bump versions" commit when composing the
   auto-PR title and body, using the feature commit's subject/body
   instead. Pulp PR #624 was the canonical repro: its title read
   "chore: bump versions" and the body was "Automated by
   `shipyard pr`." — both are gone now. The tool-branding text is
   also scrubbed, so shipped PRs read as first-party.

2. v0.25.0 (Shipyard #152) — `Version-Bump: <surface>=<level>`
   trailers are now authoritative rather than ceiling-raising.
   Previously an author-declared `=patch` could be silently raised
   to `=minor` by the conventional-commit heuristic, defeating the
   point of the trailer. This commit also syncs pulp's bundled
   `tools/scripts/version_bump_check.py` with that behaviour so the
   hook-time, CI-time, and shipyard-time gates all agree.

Third improvement, automatic (no pulp-side code): v0.25.0 also
serves `shipyard ship-state list` from the running daemon via IPC
when one is available (Shipyard #154), bypassing the ~5-6s
PyInstaller cold-start on every call. The macOS GUI polls this
every 7s; `pulp pr` also hits it during preflight.

Verified: new binary installed at ~/.local/bin/shipyard, responds
`shipyard, version 0.25.0`. `version_bump_check.py --mode=report`
and `skill_sync_check.py --mode=report` both clean against
origin/main on this branch.

Version-Bump: sdk=skip reason="shipyard pin + bundled script sync — no SDK API surface moved"
Version-Bump: plugin=skip reason="shipyard pin + bundled script sync — no plugin surface moved"

* docs(ci-skill): note v0.24.0/v0.25.0 behavior changes at new pin

Skill-sync maps tools/shipyard.toml to the `ci` skill. The pin bump
in 3fb011c surfaced three new behaviours agents need to know about:

1. Auto-PR title/body now walks past the bump commit (v0.24.0).
2. Version-Bump trailer is authoritative (v0.25.0).
3. ship-state list goes through the daemon over IPC (v0.25.0).

Updated the ci SKILL.md with a new "Behaviour notes at the current
pin" subsection, and corrected the stale `v0.21.0` pin reference.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant