Skip to content

CI | Publish a release when the version is bumped - #5

Merged
shahen94 merged 2 commits into
mainfrom
ci/release-on-bump
Oct 26, 2026
Merged

shahen94 merged 2 commits into
mainfrom
ci/release-on-bump

Conversation

@shahen94

Copy link
Copy Markdown
Member

What

Release Version pushes its tag with GITHUB_TOKEN, which doesn't trigger other workflows, so Release never ran for 0.0.8 or 0.1.0. The latest release is still 0.0.7.

  • release.yml: add workflow_dispatch, and move softprops/action-gh-release from v1 to v2.
  • release_version.yml: after pushing the tag, dispatch the release on it (actions: write):
- name: Start the release build
  run: gh workflow run release.yml --ref "${{ steps.bump.outputs.tag }}"

After merging

  • Run Release Version to publish the next version. For a minor bump that is 0.2.0.
  • To build a release for a tag that already exists, run gh workflow run release.yml --ref <tag>.

Tags pushed by Release Version use GITHUB_TOKEN, which never triggers
other workflows, so 0.0.8 and 0.1.0 were tagged without a release. A
dispatch on the tag's ref is the one trigger that token can start. Also
moves the upload action off v1, which runs on a retired Node.js.
Dispatches Release on the new tag, since the tag push alone doesn't
start it when made with GITHUB_TOKEN.
@shahen94
shahen94 merged commit c26e456 into main Oct 26, 2026
4 checks passed
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