Skip to content

Conversation

@TheBlueMatt
Copy link
Collaborator

If we're waiting on ldk-node anyway, we might as well do an rc2. I guess we could just go ahead and do 0.2-final too, its been a week or two of 0.2-rc1 and only splice-compat issues and some really minor stuff really came up. Thoughts?

@ldk-reviews-bot
Copy link

ldk-reviews-bot commented Nov 12, 2025

I've assigned @joostjager as a reviewer!
I'll wait for their review and will help manage the review process.
Once they submit their review, I'll check if a second reviewer would be helpful.

@codecov
Copy link

codecov bot commented Nov 12, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 88.85%. Comparing base (1daf93d) to head (be7218d).
⚠️ Report is 3 commits behind head on 0.2.

Additional details and impacted files
@@            Coverage Diff             @@
##              0.2    #4222      +/-   ##
==========================================
- Coverage   88.87%   88.85%   -0.03%     
==========================================
  Files         180      180              
  Lines      138000   138000              
  Branches   138000   138000              
==========================================
- Hits       122654   122620      -34     
- Misses      12529    12561      +32     
- Partials     2817     2819       +2     
Flag Coverage Δ
fuzzing 21.42% <ø> (+0.58%) ⬆️
tests 88.69% <ø> (-0.03%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

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

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

- name: Install Rust ${{ env.TOOLCHAIN }} toolchain
run: |
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh -s -- -y --profile=minimal --default-toolchain ${{ env.TOOLCHAIN }}
- name: Pin the syn and regex dependencies
Copy link
Contributor

Choose a reason for hiding this comment

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

and quote

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Eh, quote is a part of syn, basically 🤷‍♂️

cd fuzz && cargo update -p regex --precise "1.9.6" && cargo update -p syn --precise "2.0.106"
cd write-seeds && cargo update -p regex --precise "1.9.6" && cargo update -p syn --precise "2.0.106"
cd fuzz && cargo update -p regex --precise "1.9.6" && cargo update -p syn --precise "2.0.106" && cargo update -p quote --precise "1.0.41"
cd write-seeds && cargo update -p regex --precise "1.9.6" && cargo update -p syn --precise "2.0.106" && cargo update -p quote --precise "1.0.41"
Copy link
Contributor

Choose a reason for hiding this comment

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

I couldn't find any context for this change. It's not a backport, or is it? I am assuming it isn't necessary in main because of the MSRV bump.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Indeed, main has a higher MSRV.

@tnull
Copy link
Contributor

tnull commented Nov 13, 2025

I guess we could just go ahead and do 0.2-final too, its been a week or two of 0.2-rc1 and only splice-compat issues and some really minor stuff really came up. Thoughts?

Given that most users would only be able to test this once we ship LDK Node 0.7-rc.1 I think it makes sense to wait and give them at least ~a week after the RC to report any issues.

@TheBlueMatt TheBlueMatt merged commit e2ca5ba into lightningdevkit:0.2 Nov 13, 2025
24 of 25 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.

5 participants