Skip to content

Prepare reproducible marketplace release candidates #248

Description

@devantler

🤖 Generated by the Agentic Engineer

Problem

The marketplace has no repository release tags. Its two marketplace manifests carry a version, but maintainers cannot yet turn a reviewed source revision into a consistent, reviewable release proposal. Per-plugin cache versions already have a separate lifecycle and must remain independent.

Proposed increment

Add an opt-in, offline release-preparation command. Given a source revision and either the last stable marketplace tag or an explicit first-release choice, it calculates the stable version from Conventional Commit history, prepares matching marketplace manifests, and emits revision-bound JSON and readable notes in a new output directory. It never publishes, pushes, modifies the checkout, or changes per-plugin versions. Add a manually dispatched read-only workflow for the same candidate artifact and an ADR explaining the preparation/publication boundary.

Acceptance criteria

  • Real Git-history tests cover first release, patch/minor/major, scoped and breaking-footer changes, no-release histories, malformed or ambiguous inputs, and stale/unrelated baselines.
  • Both source manifests and tagged-baseline metadata are validated before output; per-plugin content/version data is preserved.
  • Complete source history and immutable commit identities are required; partial failures do not leave an apparently complete output directory.
  • The candidate names the source and baseline commits, selected version, contributing commits, plugin inventory, and the fact that it grants no publication authority.
  • Local use and a manual workflow produce the same artifact with read-only repository permissions. CI runs the offline regression suite.
  • Exercise the tool on the real repository and document the remaining live tag-reservation/publication work under feat(ci): cut semver releases so the marketplace has a version to pin #101.

Size: M. Part of #101. Actual tag creation, GitHub release publication, and consumer rollout remain a separate increment.

Activity

  1. self-assigned this
    on Sep 24, 2026
  2. moved this to 🏃🏻‍♂️ In Progress in 🌊 Project Boardon Sep 24, 2026
  3. added a commit that references this issue on Sep 24, 2026
  4. moved this from 👀 In Review to ✅ Done in 🌊 Project Boardon Sep 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Fields

Priority

None yet

Start date

None yet

Target date

None yet

Effort

None yet

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions