Skip to content

chore: revert version bump to re-run the 3.34.2 release - #366

Merged
marandaneto merged 1 commit into
mainfrom
chore/rerun-release-3.34.2
Nov 18, 2026
Merged

marandaneto merged 1 commit into
mainfrom
chore/rerun-release-3.34.2

Conversation

@marandaneto

Copy link
Copy Markdown
Member

💡 Motivation and Context

The 3.34.2 release did not finish (run). posthog-ruby 3.34.2 was pushed to RubyGems, but the step that waits for the gem to show up crashed with Bundler 4.1. #364 fixed that step. Because the failure stopped the job early:

  • posthog-ruby 3.34.2 has no git tag and no GitHub release.
  • posthog-rails 3.26.5 was never published. RubyGems still has 3.26.4.

Re-running the failed run would not help. A re-run uses the workflow file from the commit that started the run, so it would still have the broken wait step. A manual run from main would not help either. The version bump commit already deleted the changeset, so the workflow would find nothing to release.

This PR reverts the version bump commit 16decc9. That brings back the ruby-flags-explicit-geoip-default changeset and sets the versions back to posthog-ruby 3.34.1 and posthog-rails 3.26.4. When it merges, the release workflow runs again with the fixed wait step:

  • The version bump sets the same versions as before, posthog-ruby 3.34.2 and posthog-rails 3.26.5.
  • The publish step sees that posthog-ruby 3.34.2 is already on RubyGems and skips the push. It then creates the tag and GitHub release.
  • posthog-rails 3.26.5 is built, pushed, tagged, and released.

💚 How did you test it?

  • git revert 16decc9 applied cleanly on top of main. The commit message leaves out the reverted commit's title, which contains a skip-CI marker that would stop both PR checks and the release workflow on merge. This replaces chore: revert version bump to re-run the 3.34.2 release #365.
  • pnpm changeset status --verbose plans posthog-ruby 3.34.2 and posthog-rails 3.26.5, the same versions as the failed release.
  • The RubyGems API returns 200 for posthog-ruby 3.34.2 and 404 for posthog-rails 3.26.5. This matches what the publish step checks before it pushes.

📝 Checklist

  • All commits are signed (see Commit signing)
  • I reviewed the submitted code.
  • I added tests to verify the changes.
  • I updated the docs if needed.
  • No breaking change or entry added to the changelog.

If releasing new changes

  • Ran pnpm changeset to generate a changeset file

🤖 Agent context

Autonomy: Human-driven (agent-assisted)

  • I used Pi to look at the failed release and pick a way to finish it. Reverting the version bump commit was chosen over tagging and pushing posthog-rails by hand, so the release goes through the normal workflow and approval.
  • Merge this before any other posthog-ruby changeset. Otherwise the release would bump to 3.34.3 instead of finishing 3.34.2.

Restores the ruby-flags-explicit-geoip-default changeset and resets
posthog-ruby to 3.34.1 and posthog-rails to 3.26.4, reverting 16decc9.
@github-actions

Copy link
Copy Markdown

posthog-ruby-async Compliance Report

Date: 2026-11-18T12:28:48.543139+00:00
Duration: 98878ms

✅ All Tests Passed!

47/47 tests passed


Capture Tests

✅ 30/30 tests passed

View Details
Test Status Duration
Format Validation.Event Has Required Fields ✅ 108ms
Format Validation.Event Has Uuid ✅ 106ms
Format Validation.Event Has Lib Properties ✅ 108ms
Format Validation.Distinct Id Is String ✅ 105ms
Format Validation.Token Is Present ✅ 107ms
Format Validation.Custom Properties Preserved ✅ 107ms
Format Validation.Event Has Timestamp ✅ 106ms
Format Validation.Non Utc Event Timestamp Is Converted To Utc ✅ 7ms
Retry Behavior.Retries On 503 ✅ 5311ms
Retry Behavior.Does Not Retry On 400 ✅ 2109ms
Retry Behavior.Does Not Retry On 401 ✅ 2109ms
Retry Behavior.Respects Retry After Header ✅ 8113ms
Retry Behavior.Implements Backoff ✅ 15723ms
Retry Behavior.Retries On 500 ✅ 5213ms
Retry Behavior.Retries On 502 ✅ 5212ms
Retry Behavior.Retries On 504 ✅ 5214ms
Retry Behavior.Max Retries Respected ✅ 15522ms
Deduplication.Generates Unique Uuids ✅ 111ms
Deduplication.Preserves Uuid On Retry ✅ 5211ms
Deduplication.Preserves Uuid And Timestamp On Retry ✅ 10417ms
Deduplication.Preserves Uuid And Timestamp On Batch Retry ✅ 5214ms
Deduplication.No Duplicate Events In Batch ✅ 111ms
Deduplication.Different Events Have Different Uuids ✅ 107ms
Compression.Sends Gzip When Enabled ✅ 105ms
Batch Format.Uses Proper Batch Structure ✅ 105ms
Batch Format.Flush With No Events Sends Nothing ✅ 4ms
Batch Format.Multiple Events Batched Together ✅ 112ms
Error Handling.Does Not Retry On 403 ✅ 2108ms
Error Handling.Does Not Retry On 413 ✅ 2109ms
Error Handling.Retries On 408 ✅ 5213ms

Feature_Flags Tests

✅ 17/17 tests passed

View Details
Test Status Duration
Request Payload.Request With Person Properties Device Id ✅ 108ms
Request Payload.Flags Request Uses V2 Query Param ✅ 105ms
Request Payload.Flags Request Hits Flags Path Not Decide ✅ 106ms
Request Payload.Flags Request Omits Authorization Header ✅ 106ms
Request Payload.Token In Flags Body Matches Init ✅ 106ms
Request Payload.Groups Round Trip ✅ 106ms
Request Payload.Groups Default To Empty Object ✅ 107ms
Request Payload.Disable Geoip False Propagates As Geoip Disable False ✅ 108ms
Request Payload.Disable Geoip Omitted Defaults To False ✅ 106ms
Request Payload.Flag Keys To Evaluate Contains Only Requested Key ✅ 105ms
Request Lifecycle.No Flags Request On Init Alone ✅ 4ms
Request Lifecycle.No Flags Request On Normal Capture ✅ 105ms
Request Lifecycle.Two Flag Calls Produce Two Remote Requests ✅ 109ms
Request Lifecycle.Mock Response Value Is Returned To Caller ✅ 105ms
Retry Behavior.Retries Flags On 502 ✅ 210ms
Retry Behavior.Retries Flags On 504 ✅ 211ms
Side Effect Events.Get Feature Flag Captures Feature Flag Called Event ✅ 110ms

@github-actions

Copy link
Copy Markdown

posthog-ruby-sync Compliance Report

Date: 2026-11-18T12:28:51.131317+00:00
Duration: 94136ms

✅ All Tests Passed!

47/47 tests passed


Capture Tests

✅ 30/30 tests passed

View Details
Test Status Duration
Format Validation.Event Has Required Fields ✅ 9ms
Format Validation.Event Has Uuid ✅ 5ms
Format Validation.Event Has Lib Properties ✅ 5ms
Format Validation.Distinct Id Is String ✅ 7ms
Format Validation.Token Is Present ✅ 6ms
Format Validation.Custom Properties Preserved ✅ 6ms
Format Validation.Event Has Timestamp ✅ 6ms
Format Validation.Non Utc Event Timestamp Is Converted To Utc ✅ 6ms
Retry Behavior.Retries On 503 ✅ 5307ms
Retry Behavior.Does Not Retry On 400 ✅ 2009ms
Retry Behavior.Does Not Retry On 401 ✅ 2010ms
Retry Behavior.Respects Retry After Header ✅ 8014ms
Retry Behavior.Implements Backoff ✅ 15280ms
Retry Behavior.Retries On 500 ✅ 5115ms
Retry Behavior.Retries On 502 ✅ 5154ms
Retry Behavior.Retries On 504 ✅ 5118ms
Retry Behavior.Max Retries Respected ✅ 15568ms
Deduplication.Generates Unique Uuids ✅ 16ms
Deduplication.Preserves Uuid On Retry ✅ 5113ms
Deduplication.Preserves Uuid And Timestamp On Retry ✅ 10305ms
Deduplication.Preserves Uuid And Timestamp On Batch Retry ✅ 5154ms
Deduplication.No Duplicate Events In Batch ✅ 15ms
Deduplication.Different Events Have Different Uuids ✅ 8ms
Compression.Sends Gzip When Enabled ✅ 5ms
Batch Format.Uses Proper Batch Structure ✅ 4ms
Batch Format.Flush With No Events Sends Nothing ✅ 2ms
Batch Format.Synchronous Capture Delivers Each Event Immediately ✅ 13ms
Error Handling.Does Not Retry On 403 ✅ 2006ms
Error Handling.Does Not Retry On 413 ✅ 2009ms
Error Handling.Retries On 408 ✅ 5114ms

Feature_Flags Tests

✅ 17/17 tests passed

View Details
Test Status Duration
Request Payload.Request With Person Properties Device Id ✅ 9ms
Request Payload.Flags Request Uses V2 Query Param ✅ 7ms
Request Payload.Flags Request Hits Flags Path Not Decide ✅ 8ms
Request Payload.Flags Request Omits Authorization Header ✅ 6ms
Request Payload.Token In Flags Body Matches Init ✅ 5ms
Request Payload.Groups Round Trip ✅ 5ms
Request Payload.Groups Default To Empty Object ✅ 5ms
Request Payload.Disable Geoip False Propagates As Geoip Disable False ✅ 5ms
Request Payload.Disable Geoip Omitted Defaults To False ✅ 5ms
Request Payload.Flag Keys To Evaluate Contains Only Requested Key ✅ 5ms
Request Lifecycle.No Flags Request On Init Alone ✅ 1ms
Request Lifecycle.No Flags Request On Normal Capture ✅ 5ms
Request Lifecycle.Two Flag Calls Produce Two Remote Requests ✅ 6ms
Request Lifecycle.Mock Response Value Is Returned To Caller ✅ 5ms
Retry Behavior.Retries Flags On 502 ✅ 108ms
Retry Behavior.Retries Flags On 504 ✅ 109ms
Side Effect Events.Get Feature Flag Captures Feature Flag Called Event ✅ 8ms

@marandaneto
marandaneto marked this pull request as ready for review November 18, 2026 12:28
@marandaneto
marandaneto requested a review from a team as a code owner November 18, 2026 12:28
@veria-ai

veria-ai Bot commented Nov 18, 2026 •

Copy link
Copy Markdown

PR overview

No security issues were found in this pull request.

Reviews

@marandaneto
marandaneto merged commit c5bedb3 into main Nov 18, 2026
31 checks passed
@marandaneto
marandaneto deleted the chore/rerun-release-3.34.2 branch November 18, 2026 12:29
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.

2 participants