Skip to content

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

Closed
marandaneto wants to merge 1 commit into
mainfrom
chore/revert-version-bump-3.34.2
Closed

marandaneto wants to merge 1 commit into
mainfrom
chore/revert-version-bump-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.
  • 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.

@marandaneto marandaneto self-assigned this Nov 18, 2026
@marandaneto
marandaneto marked this pull request as ready for review November 18, 2026 12:16
@marandaneto
marandaneto requested a review from a team as a code owner November 18, 2026 12:16
@marandaneto
marandaneto enabled auto-merge (squash) November 18, 2026 12:16
@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

Copy link
Copy Markdown
Member Author

Replaced by #366. The default revert message quoted a skip-CI marker, which skipped CI here and would also skip the release workflow after a squash merge.

auto-merge was automatically disabled November 18, 2026 12:26

Pull request was closed

@marandaneto
marandaneto deleted the chore/revert-version-bump-3.34.2 branch November 18, 2026 12:27
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