Skip to content

Release 2.1.282 (2026-10-31)

Bug fixes

  • update only the declared marketplaces and report a failed command's stdout (#3881)
  • fix(plugins): update only the declared marketplaces and report a failed command's stdout

The marketplace refresh now runs 'claude plugin marketplace update ' for each marketplace it adds, instead of the bare form that updates every registered marketplace. A stale marketplace the settings do not declare is no longer touched, so it can no longer fail the refresh. A declared marketplace's failed update is reported as marketplace:.

A failed command in the refresh path now has its stdout printed with the failure, since claude writes some causes only there; the Run still echoes its stderr. This covers the listing commands too.

Documentation

  • document rolling back a release and switching the marketplace ref (#3880)
  • docs(release): document rolling back a release and switching the marketplace ref

The consumer setup guide defines vergil-marketplace at the floating v2.1 tag and documents switching an existing machine with vrg-host plugins and vrg-vm update --all, and moving to a new minor line by hand. The release guide gains a Rolling back a release runbook: the exact vrg-promote steps, picking the move up on each machine, and how long a rollback lasts. The vrg-promote reference links the runbook. Ref vergil-project/vergil-tooling#3853

  • docs(release): warn about in-flight releases and the warn-only start refresh in the rollback runbook

The rollback runbook now has the operator check that no plugin release is in flight before moving the tag, since its promote stage or a later resume moves v2.1 forward over the rollback with no prompt. Both guides say a stopped VM's start refresh only warns on failure and how to check it. The runbook keeps to the spec's procedure: the plugin-dir caveat, the roll-forward line, the follow-up promote wording, the Keeping up to date pointer and the vrg-promote reference link are removed. Ref vergil-project/vergil-tooling#3853

  • docs(release): tighten the rollback runbook's checks and the plugin refresh guidance

The rollback runbook names the Tag protection ruleset as the gate, asks the operator to re-read the confirmed move and to check each machine's installed version at the end, since the ref verification cannot see a backward move on the same ref, and explains that a release in flight or a resume without --no-promote undoes the rollback. The switching section narrows what the verification covers, gives the update order, and separates the single-VM, Lima and cloud cases for a VM that is not running. The minor-line paragraph says a rollback stays within one line. Keeping up to date and the stale plugin cache entry now lead with vrg-host plugins and vrg-vm update --all. Ref vergil-project/vergil-tooling#3853

  • docs(release): correct the vrg-vm update order and cover promote's uncertain exits

The switching section gives vrg-vm update's real order (tooling, then settings, then plugins) and what a box whose tooling update fails is left with. The rollback runbook names the rolling-tag branch-name ruleset as part of the gate for Claude Code, says to re-run the dry run after an exit that leaves origin moved or unknown, and how to check the checkout when the tag is already promoted. Ref vergil-project/vergil-tooling#3853

  • docs(release): say the plugin refresh updates every registered marketplace

The bare marketplace update covers undeclared marketplaces too, so a stale one fails the refresh. Add a troubleshooting entry pointing at the manual command and vergil-project/vergil-tooling#3879.

  • docs(release): fix the already-promoted origin check and widen the in-flight release warning

Use vrg-git ls-remote --get-url origin, since vrg-git denies remote. vrg-release --resume runs every stage again, so any open plugin release tracking issue re-promotes; say so, and drop the duplicate pointer before the four steps.

  • docs(release): link the vrg-promote reference to the rollback runbook

  • docs(release): cover plugin-dir sessions, no-promote releases and rolling forward in the rollback runbook

  • docs(release): say a malformed plugin-dirs file still fails a cloud session

CI Evidence: All gates passed — full audit bundle available. Download →