Repository navigation
ci: Bump flagsmith-flag-engine's minimum version via Renovate - #72
Merged
Merged
Conversation
Cargo's default `update-lockfile` strategy only updates our Cargo.lock, which downstream users don't consume, so they could keep resolving an older engine without its fixes. Bump the requirement in Cargo.toml instead, so every SDK release requires the engine version it was tested against.
|
No actionable comments were generated in the recent review.
 |
emyller
approved these changes
Oct 30, 2026
This comment was marked as outdated.
This comment was marked as outdated.
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.
Instead of re-locking the existing constraint, eagerly bump the engine for every engine release.