Skip to content

Release this repo's gem via trusted publishing (fixes stale monorepo workflow) - #812

Merged
ronaldtse merged 2 commits into
mainfrom
fix/release-gem-oidc
Oct 19, 2026
Merged

ronaldtse merged 2 commits into
mainfrom
fix/release-gem-oidc

Conversation

@ronaldtse

Copy link
Copy Markdown
Contributor

What

Replaces the stale release workflow (which checked out the old interscript monorepo, bootstrapped it, and published the monorepo's ruby package -- it has failed on every tag push, including all v3.0.0/v3.2.0 attempts, and references a repo secret that does not exist) with a release of THIS repo's gem:

  • self-checkout, Ruby 3.3, bundler-cache
  • full spec run before publishing
  • rubygems/release-gem@v1 with id-token: write (RubyGems.org trusted publishing / OIDC -- the org standard; no API-key secret needed)

bundler's rake release aborts when the v* tag already exists (maps lesson), so the release task is hand-rolled to push the built gem from pkg/.

Also carries the 3.2.0 version bump so the tag builds the right version.

Verify

  • gemspec deps unchanged (interscript-maps ~> 2.5, parsanol, text, thor -- identical to published 3.1.0)
  • specs run as the pre-publish gate

release.yml still targeted the old interscript monorepo (checkout +
bootstrap + monorepo ruby/js packages), which can never publish this
gem and has failed on every tag. Release the gem from this repo:
self-checkout, spec run, then rubygems/release-gem (OIDC).

bundler's rake release aborts when the v* tag already exists, so the
release task is hand-rolled to push the built gem directly.
@ronaldtse
ronaldtse merged commit 8b59468 into main Oct 19, 2026
10 checks passed
@ronaldtse
ronaldtse deleted the fix/release-gem-oidc branch October 19, 2026 13:54
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