Skip to content

fix: Rakefile with build/release tasks for the release-gem action - #192

Merged
ronaldtse merged 1 commit into
mainfrom
fix/rakefile
Aug 27, 2026
Merged

fix: Rakefile with build/release tasks for the release-gem action#192
ronaldtse merged 1 commit into
mainfrom
fix/rakefile

Conversation

@ronaldtse

Copy link
Copy Markdown
Contributor

Fourth layer of the rubygems/release-gem onboarding: the action's flow is
bundle install -> rake build -> rake release, so the repo needs those rake
tasks. This adds a minimal Rakefile.

Deliberately hand-rolled instead of require "bundler/gem_tasks": bundler's
release task creates and pushes a vX.Y.Z git tag, and this repo's v* tags are
already cut by the maps artifact release flow (v2.5.0 exists) — bundler would
abort with "Tag v2.5.0 already has been created" before pushing.

  • rake build — gem build interscript-maps.gemspec
  • rake release — gem push (uses the OIDC-derived key env the action sets)

Failure ladder so far: no Gemfile (#190) -> rake missing from bundle (#191) ->
no Rakefile (this PR).

Hand-rolled rather than bundler/gem_tasks because bundler's release
task creates and pushes a git tag; this repo's v* tags are cut by the
maps artifact release flow and v2.5.0 already exists.
@ronaldtse
ronaldtse merged commit bc5994a into main Aug 27, 2026
6 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