Skip to content

chore(main): release 5.3.0 - #130

Open
flagsmithdev wants to merge 1 commit into
mainfrom
release-please--branches--main
Open

flagsmithdev wants to merge 1 commit into
mainfrom
release-please--branches--main

Conversation

@flagsmithdev

@flagsmithdev flagsmithdev commented Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

5.3.0 (2026-11-13)

Features

  • Retry event delivery and flush on close (#129) (5abcc8e)

This PR was generated with Release Please. See documentation.


Summary by cubic

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.

View guided diff Turn on auto-fix

@flagsmithdev
flagsmithdev requested a review from a team as a code owner November 13, 2026 13:54
@flagsmithdev
flagsmithdev requested review from emyller and removed request for a team November 13, 2026 13:54
@coderabbitai

coderabbitai Bot commented Nov 13, 2026 •

Copy link
Copy Markdown

Explain Change →

Walkthrough

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.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Merge Risk: Moderate · up to ebabf

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.

Share

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 2 files

View guided diff | Turn on auto-fix | Re-trigger cubic

@codspeed

codspeed Bot commented Nov 13, 2026

Copy link
Copy Markdown

Merging this PR will not alter performance

✅ 15 untouched benchmarks


Comparing release-please--branches--main (ebabf45) with main (5abcc8e)

Open in CodSpeed

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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.

@@ -1 +1 @@
{".":"5.2.0"}
{".":"5.3.0"}

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant