Skip to content

Pin indexmap back to account for hashbrown MSRV bump #3402

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 7, 2024

Conversation

tnull
Copy link
Contributor

@tnull tnull commented Nov 7, 2024

... here we go again.

indexmap 2.6.0 upgraded to hashbrown 0.15, which unfortunately bumped their MSRV to rustc 1.65 with the 0.15.1 release. So we pin indexmap to 2.5.0 to fix our MSRV CI.

@tnull tnull requested a review from TheBlueMatt November 7, 2024 13:30
`indexmap` 2.6.0 upgraded to `hashbrown` 0.15, which unfortunately
bumped their MSRV to rustc 1.65 with the 0.15.1 release. So we pin
`indexmap` to 2.5.0 to fix our MSRV CI.
@tnull tnull force-pushed the 2024-11-pin-indexmap branch from 73e6066 to e12ee9d Compare November 7, 2024 13:35
Copy link

codecov bot commented Nov 7, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.67%. Comparing base (c35adff) to head (e12ee9d).
Report is 6 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3402      +/-   ##
==========================================
- Coverage   89.68%   89.67%   -0.02%     
==========================================
  Files         128      128              
  Lines      104891   104891              
  Branches   104891   104891              
==========================================
- Hits        94076    94065      -11     
- Misses       8114     8123       +9     
- Partials     2701     2703       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Collaborator

@TheBlueMatt TheBlueMatt left a comment

Choose a reason for hiding this comment

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

I'm starting to think we should move the lightning-transaction-sync crate back out of the workspace and increase its MSRV until we can replace its HTTP stack with something more conservative.

@TheBlueMatt TheBlueMatt merged commit 61a60d5 into lightningdevkit:main Nov 7, 2024
19 of 20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants