Repository navigation
chore(main): release 5.1.0 - #113
flagsmithdev wants to merge 1 commit into
Conversation
6c3f3fe to
4cafb25
Compare
|
No actionable comments were generated in the recent review.
|
There was a problem hiding this comment.
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:
270795c9-7d50-4a72-b32d-865449fb09d7
Files selected for processing: 2-
.release-please-manifest.jsonCHANGELOG.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.0.1"} | |||
| {".":"5.0.2"} | |||
There was a problem hiding this comment.
Synchronise the gem version with the 5.0.2 release.
flagsmith.gemspec reads Flagsmith::VERSION, but lib/flagsmith/version.rb still defines 4.3.0. This change therefore advertises version 5.0.2 while the built gem remains 4.3.0. Update the version file and ensure Release Please updates that path. (raw.githubusercontent.com)
9b38ce1 to
8afdbd2
Compare
8afdbd2 to
cdb7110
Compare
🤖 I have created a release beep boop
5.1.0 (2026-10-30)
Features
Bug Fixes
CI
This PR was generated with Release Please. See documentation.