Skip to content

ci: pass gated=false to enable rubygems publish#8

Merged
ronaldtse merged 1 commit into
mainfrom
chore/release-gated-false
Jul 2, 2026
Merged

ci: pass gated=false to enable rubygems publish#8
ronaldtse merged 1 commit into
mainfrom
chore/release-gated-false

Conversation

@ronaldtse

Copy link
Copy Markdown
Contributor

Summary

The SHOULD_PUBLISH condition in metanorma/ci's rubygems-release.yml is:

github.event_name == 'workflow_dispatch' &&
  (inputs.gated == false || secrets.pat_token == '')

Without gated: false AND with pat_token set (we pass ${{ secrets.GITHUB_TOKEN }}), the condition is false. The previous release run (ea_release7) marked itself "success" but only bumped the version and pushed the v0.1.1 tag — it never pushed the gem to rubygems.

Fix

Add gated: false to the with: block so SHOULD_PUBLISH evaluates true for workflow_dispatch on this repo.

The metanorma/ci rubygems-release.yml computes SHOULD_PUBLISH:
  github.event_name == 'workflow_dispatch' &&
    (inputs.gated == false || secrets.pat_token == '')

Without 'gated: false' AND with pat_token set, the condition
evaluates to false and the workflow bumps + tags but never
publishes to rubygems. The previous run (ea_release7, success)
created tag v0.1.1 but did not push the gem.
@ronaldtse
ronaldtse merged commit 356103c into main Jul 2, 2026
2 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