fix: pin reedline to 0.47.0#3398
Merged
Merged
Conversation
Temporarily pin reedline to the previous version while investigating a suspected terminal segfault introduced after the 0.48.0 update. Co-Authored-By: ForgeCode <noreply@forgecode.dev>
Pin the toolchain back to the previous Rust version while investigating the suspected terminal segfault alongside the reedline rollback. Co-Authored-By: ForgeCode <noreply@forgecode.dev>
754cf4e to
c1cef33
Compare
laststylebender14
approved these changes
May 28, 2026
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.
Summary
Pin
reedlineto0.47.0to mitigate a suspected terminal segfault introduced after the0.48.0dependency update.Context
The
v2.13.0release included areedlineupdate from0.47.0to0.48.0. The segfault appears related to terminal interaction, and Forge's interactive prompt is built directly onreedline. This PR temporarily pinsreedlineto the previous known version while the0.48.0regression is investigated.Changes
reedlinedependency to exactly0.47.0Cargo.lockfromreedline 0.48.0to0.47.0Testing
Notes
This is intended as a conservative mitigation. Once the upstream
reedline 0.48.0issue is isolated or fixed, the dependency can be unpinned and upgraded again.