Repository navigation
fix(ci): run rubygems-await with Bundler older than 4.1 in release - #364
Conversation
PR overviewNo security issues were found in this pull request. Reviews
|
posthog-ruby-sync Compliance ReportDate: 2026-11-18T11:50:26.768333+00:00 ✅ All Tests Passed!47/47 tests passed Capture Tests✅ 30/30 tests passed View Details
Feature_Flags Tests✅ 17/17 tests passed View Details
|
posthog-ruby-async Compliance ReportDate: 2026-11-18T11:50:38.262806+00:00 ✅ All Tests Passed!47/47 tests passed Capture Tests✅ 30/30 tests passed View Details
Feature_Flags Tests✅ 17/17 tests passed View Details
|
SDK performance: posthog-rubyBenchmarks completed. No changes flagged for review. Flags require at least a 5% change in the median and all six pairs agreeing on direction. This is a noise filter, not proof of a performance change or a CI gate. View all results
Values are medians of paired measurements. Not flagged does not mean unchanged. Unavailable means a measurement could not be provided, not zero. Estimated allocation measurements retain their instrumentation uncertainty. RSS measures the whole process, not just SDK allocations; observed peaks are sampled checkpoints. Paired ranges in the diagnostics describe variability, not confidence intervals. Each shard uses its own runner; compare Before PR against With PR within a row, not across shards. Compared 102 metric rows; 102 rows shown in all results. Omitted or shortened data remain in |
💡 Motivation and Context
The release for
posthog-ruby3.34.2 failed in the "Wait for posthog-ruby to be available" step (run). The gem was already published to RubyGems, but the step timed out after 15 minutes. That cancelled theposthog-railsrelease and skipped the tag and GitHub release.The step runs
gem exec rubygems-await, which installs the newest Bundler. Bundler 4.1.0 was released on 2026-11-16 and moved its compact index client into RubyGems.rubygems-await0.5.4, the latest version, then takes a code path for old Bundler versions and calls a method that no longer exists:Its check of the RubyGems
infoendpoint fails on every attempt, so the step never finishes. The last successful release on 2026-11-13 used Bundler 4.0.24.The step now installs
rubygems-await0.5.4 and runs it with a Bundler version older than 4.1. The Bundler that ships with Ruby 4.0 meets that requirement.💚 How did you test it?
Locally with Ruby 4.0, in a clean
GEM_HOME:gem exec rubygems-await --timeout 20 posthog-ruby-3.34.2.gemreproduces the sameNoMethodErrorwith Bundler 4.1.0, and theinfocheck never succeeds.posthog-ruby-3.34.2.gemwith Bundler 4.1.0 installed. It reportedFound posthog-ruby-3.34.2and exited with status 0.After merging, re-run the failed jobs of the release run to tag 3.34.2 and publish
posthog-rails. The publish step already skips the push when the version is on RubyGems.📝 Checklist
If releasing new changes
pnpm changesetto generate a changeset file🤖 Agent context
Autonomy: Human-driven (agent-assisted)
rubygems-awaitand run it with an older Bundler, instead of writing a custom polling loop, to keep the change small. A fix inrubygems-awaititself would let us remove the Bundler restriction later.