docs: correct the marketplace dispatch comment

The comment said a release of an existing plugin leaves the catalogue
byte-identical "because entries carry no version and npm resolves latest",
so the dispatch existed only to surface a *new* plugin promptly.

The generator now records the resolved version in the codex manifest, so a
release does change the catalogue's bytes. That was the point of pinning:
without a version, codex compared byte-identical documents, concluded the
catalogue had not moved, and left the installed plugin on whatever it first
resolved.

Comment only — the step already behaved correctly for both cases. Worth
fixing because the old wording invites the reader to skip wiring up
marketplace_dispatch_url unless they are adding a plugin, which is how one
consumer ended up without it.

Co-Authored-By: Claude Opus 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01MgsFmepr9FxbFkax5Y2h6z
This commit is contained in:
2026-08-24 08:50:02 -04:00
co-authored by Claude Opus 5
parent d54502067f
commit 74674412e3
@@ -513,11 +513,12 @@ jobs:
files: dist/*
- name: Refresh the central marketplace
# The manifest is derived from the package registry, so it only needs
# regenerating when the set of plugins changes — a new version of an
# existing plugin leaves it byte-identical, because entries carry no
# version and npm resolves `latest`. This call exists so a *new* plugin
# appears immediately rather than at the next scheduled run.
# The manifest is derived from the package registry, so publishing is
# all this job has to do — the generator re-derives the catalogue from
# whatever the registry now holds. This call only makes that happen now
# rather than at the generator's next scheduled run, and it matters for
# a new version just as much as a new plugin: codex entries carry the
# resolved version, so a release changes the catalogue's bytes.
if: inputs.marketplace_dispatch_url != ''
env:
DISPATCH_URL: ${{ inputs.marketplace_dispatch_url }}