The problem
The marketplace has no release version. There are no tags, no GitHub releases, no changelog, and
no release workflow — only ci.yaml
and update-agent-skills.yaml.
AGENTS.md states this as a
deliberate position: "The repo is consumed directly as a marketplace (no release pipeline)."
Why it is worth revisiting
Per-plugin versioning here is strong — bump-plugin-version.sh
moves a version everywhere it has to agree, and check-plugin-version-bump.sh
stops a content change from shipping on a stale cache key. That covers one plugin over time.
It does not cover the marketplace as a whole:
- Nothing to pin or roll back to. A consumer who wants a known-good state of the marketplace has
only a commit SHA. There is no v1.4.0 to point at and no way back to yesterday's set.
- No answer to "what changed?" Conventional Commit titles are already required, and every
ingredient for generated release notes is present — but nothing consumes them, so the history is
readable only by scrolling it.
metadata.version in both marketplace manifests is hand-set and drifts silently. It sits at
1.0.0 today and nothing checks or moves it, so it says nothing about the current state.- The
released label exists but is never applied, which suggests a release step was intended
at some point.
What would close this
A release pipeline on main that reads the Conventional Commit history, calculates the next SemVer
tag, publishes a GitHub release with generated notes, and writes that version into metadata.version
in both marketplace manifests. Per-plugin versions stay exactly as they are — independent, bumped by
the existing scripts and gate. The repository-level tag describes the marketplace, not any single
plugin.
The sibling repo devantler-tech/agent-skills
already releases this way (currently v1.9.2) via its
release.yaml
and cd.yaml,
so the pattern is already proven in this organisation.
The problem
The marketplace has no release version. There are no tags, no GitHub releases, no changelog, and
no release workflow — only
ci.yamland
update-agent-skills.yaml.AGENTS.mdstates this as adeliberate position: "The repo is consumed directly as a marketplace (no release pipeline)."
Why it is worth revisiting
Per-plugin versioning here is strong —
bump-plugin-version.shmoves a version everywhere it has to agree, and
check-plugin-version-bump.shstops a content change from shipping on a stale cache key. That covers one plugin over time.
It does not cover the marketplace as a whole:
only a commit SHA. There is no
v1.4.0to point at and no way back to yesterday's set.ingredient for generated release notes is present — but nothing consumes them, so the history is
readable only by scrolling it.
metadata.versionin both marketplace manifests is hand-set and drifts silently. It sits at1.0.0today and nothing checks or moves it, so it says nothing about the current state.releasedlabel exists but is never applied, which suggests a release step was intendedat some point.
What would close this
A release pipeline on
mainthat reads the Conventional Commit history, calculates the next SemVertag, publishes a GitHub release with generated notes, and writes that version into
metadata.versionin both marketplace manifests. Per-plugin versions stay exactly as they are — independent, bumped by
the existing scripts and gate. The repository-level tag describes the marketplace, not any single
plugin.
The sibling repo
devantler-tech/agent-skillsalready releases this way (currently
v1.9.2) via itsrelease.yamland
cd.yaml,so the pattern is already proven in this organisation.