Skip to content

fix: restore release version source after marketplace decommission#26

Merged
antonbabenko merged 1 commit into
masterfrom
fix/release-version-source
May 17, 2026
Merged

fix: restore release version source after marketplace decommission#26
antonbabenko merged 1 commit into
masterfrom
fix/release-version-source

Conversation

@antonbabenko
Copy link
Copy Markdown
Owner

Problem

PR #25 (decommission) set conventional-changelog-action skip-version-file: true. Without a version file the action recomputed the version from git as 1.1.0, hit the pre-existing v1.1.0 tag, and the post-merge release failed (run 25985392387). No bad commit/tag was pushed; master is clean at 778dfcb but the decommission is unreleased and the pipeline is broken.

Fix

  • Add version.json ({"version":"1.9.0"}) - dedicated version file, seeded at the current release so the action bumps from the right baseline. No marketplace.json dependency.
  • automated-release.yml: version-file: ./version.json, version-path: version, skip-version-file: false. 2b step still syncs SKILL.md frontmatter from $VERSION; git add now includes version.json.

Effect

Commits since v1.9.0 = decommission chore: + this fix: -> patch -> v1.9.1, fresh tag (no collision). SKILL.md frontmatter synced. marketplace.json stays deleted.

Note

This corrects a deviation in the approved plan: the plan/my first attempt assumed skip-version-file was sufficient; the action actually needs a version file for the current baseline. version.json is the minimal correct artifact.

The decommission set conventional-changelog-action to skip-version-file,
which made it lose the current-version baseline and recompute from git
as 1.1.0 -> tag collision -> release failed.

Add version.json as the dedicated version file (seed 1.9.0 = current
release). The action reads/bumps it; the 2b step still syncs SKILL.md
frontmatter from $VERSION. No marketplace.json dependency reintroduced.
@antonbabenko antonbabenko merged commit 77db3a3 into master May 17, 2026
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