Repository navigation
Bump LfMerge to 2.0.142 to match what production already runs - #1860
Merged
Merged
Conversation
Production was moved to lfmerge 2.0.142 directly in the fleet repo
("Deploy LfMerge bugfix"). The deploy job now writes the version from
this Dockerfile, so without this bump the next production release
would downgrade lfmerge to 2.0.141.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Unit Test Results362 tests 362 ✅ 11s ⏱️ Results for commit 872b82e. |
hahn-kev
added
the
engineering
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.
Production was moved to lfmerge 2.0.142 directly in the fleet repo ("Deploy LfMerge bugfix"). The deploy job now writes the version from this Dockerfile, so without this bump the next production release would downgrade lfmerge to 2.0.141.