Skip to content

Fix automatic GitHub Packages release versioning - #6

Merged
marcialwushu merged 2 commits into
mainfrom
fix/automatic-package-release
Oct 10, 2026
Merged

marcialwushu merged 2 commits into
mainfrom
fix/automatic-package-release

Conversation

@marcialwushu

Copy link
Copy Markdown
Member

Summary

  • replace manual release inputs with an input-free publish-packages workflow
  • calculate SemVer from the latest reachable release tag and repository diff
  • publish PromptKit before Prompts with one shared version
  • create the release tag only after both GitHub Packages publications succeed
  • reject releases from branches other than main

Validation

  • actionlint .github/workflows/*.yml
  • 58 unit and contract tests passed
  • first-release plan simulation: base root commit, impact MAJOR, version 0.1.0 from version.json

Failure fixed

The previous manual run allowed base-ref to point to the current commit and accepted identical previous/next version inputs. The new orchestration exposes no manual version fields.

@marcialwushu marcialwushu added the semver:patch Backward-compatible patch release impact label Oct 10, 2026 — with ChatGPT Codex Connector
@marcialwushu
marcialwushu merged commit 857d598 into main Oct 10, 2026
5 checks passed
@marcialwushu
marcialwushu deleted the fix/automatic-package-release branch October 10, 2026 19:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

semver:patch Backward-compatible patch release impact

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant