Skip to content

Fix the RubyGems step of the release publishing script - #284

Merged
avsej merged 1 commit into
couchbase:mainfrom
avsej:fix-publish-rubygems-skip
Oct 21, 2026
Merged

avsej merged 1 commit into
couchbase:mainfrom
avsej:fix-publish-rubygems-skip

Conversation

@avsej

@avsej avsej commented Oct 21, 2026

Copy link
Copy Markdown
Member

Problem. bin/publish-release.rb fails at the RubyGems step on every run, dry-run included:

./bin/publish-release.rb:501:in 'Object#push_to_rubygems': undefined method 'each_value' for an instance of Array (NoMethodError)

plan_rubygems_push returns the already-published gems as an Array of [gem, spec] pairs, and push_to_rubygems iterates it with each_value.

Change. The skip list holds the gem specification alone, and is iterated with each.

Motivation
----------
plan_rubygems_push returns the gems already on rubygems.org as an
Array of [gem, spec] pairs. push_to_rubygems iterates it with
each_value, which Array does not define. The step therefore raises
NoMethodError on every run, in dry-run and with --execute, before
any gem is pushed.

Modifications
-------------
The skip list holds the gem specification alone, and
push_to_rubygems iterates it with each.

Results
-------
A dry run of the RubyGems step lists the gems already live and the
gems it would push.
@avsej
avsej merged commit 84dac1b into couchbase:main Oct 21, 2026
39 checks passed
@avsej
avsej deleted the fix-publish-rubygems-skip branch October 21, 2026 22:46
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