You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Releases 5.3.0 of the Flagsmith Ruby client, bumping the version manifest and updating the changelog to include retry logic for event delivery and flush on close.
Written for commit ebabf45. Summary will update on new commits.
The release manifest version changes from 5.2.0 to 5.3.0. The changelog adds a 5.3.0 entry dated 2026-11-13. It describes retrying event delivery and flushing on close.
This release is marked 5.3.0 in the manifest and changelog, but the gem's own version constant still says 4.3.0. Publishing could fail or ship a gem with the wrong version number. Update the version constant, or configure release-please to maintain it, before merging.
- [ ] Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
Review info
Run configuration
Source mode: Auto
Repository: Unavailable
Branch: Unavailable
File: No configuration file from this repository applied
Commit: Unavailable
Layers: Organization UI
Review profile: ASSERTIVE
Plan: Advanced
Run ID: a5e0e605-54ea-4ff6-adfd-dcf3f3c249cb
Commits
Reviewing files that changed from the base of the PR and between 5abcc8e and ebabf45.
Files selected for processing: 2
.release-please-manifest.json
CHANGELOG.md
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.
The reason will be displayed to describe this comment to others. Learn more.
Major · Data Integrity & Integration · Quick win
Update Flagsmith::VERSION to 5.3.0 in this release.
The gemspec takes its version from Flagsmith::VERSION, and this PR leaves that constant at 4.3.0. The publish job builds the gem from this tree, so the artifact carries version 4.3.0. The rake release step can then fail when 4.3.0 already exists on RubyGems.
Suggested fix
module Flagsmith
- VERSION = '4.3.0'+ VERSION = '5.3.0'
end
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
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.
🤖 I have created a release beep boop
5.3.0 (2026-11-13)
Features
This PR was generated with Release Please. See documentation.
Summary by cubic
Releases
5.3.0of the Flagsmith Ruby client, bumping the version manifest and updating the changelog to include retry logic for event delivery and flush on close.Written for commit ebabf45. Summary will update on new commits.