chore: automate ruby releases with changesets#124
Merged
marandaneto merged 6 commits intomainfrom Apr 16, 2026
Merged
Conversation
dustinbyrne
approved these changes
Apr 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
💡 Motivation and Context
The Ruby SDK release process still required manually editing
lib/posthog/version.rbandCHANGELOG.mdin the PR. This change brings it in line with the other SDKs by making releases Changesets-driven and letting CI handle the version bump, changelog update, tagging, and publish flow.It also aligns the repo's GitHub Actions usage with the rest of the SDK repos by pinning
pnpm/action-setupto a full commit SHA, moving GitHub-owned actions to newer major versions where this repo was behind, standardizing on Node 24 for the release workflow, and using plain semver tags/releases without avprefix.To validate the new automation end-to-end, this PR now includes a patch changeset and the
releaselabel so merging it should exercise the new release workflow immediately.💚 How did you test it?
.github/workflows/release.yml,.github/workflows/codeql.yml, and.github/workflows/unit-tests.ymlwith Ruby YAML to verify the workflow files are validbash -n scripts/bump-version.shpnpm changeset statusseesposthog-rubyas a versioned package and computes the next version from a temporary changeset.changeset/README.mdsince it is not needed for this repopnpm/action-setupis not treated as an exception; those repos pin it to full SHAs as well.nvmrcwith Node 24 and updated the release workflow to usenode-version: 24X.Y.Zinstead ofvX.Y.Z3.6.2📝 Checklist
If releasing new changes
pnpm changesetto generate a changeset filereleaselabel to the PR