Skip to content

Conversation

@jbrill
Copy link

@jbrill jbrill commented Dec 16, 2025

Updates lnc-web to use the new lnc-core v0.3.5-alpha bindings.

@jamaljsr
Copy link
Member

It's fine for CI to fail right now since the new lnc-core release hasn't been published.

The more important update that this PR should include is to update the URL to the new LNC wasm file. See #122 for reference.

@jbrill
Copy link
Author

jbrill commented Dec 16, 2025

Great @jamaljsr I've updated that lnc-web PR to contain the new WASM.

I've tested this linked through lnc-web, up to terminal-web, and confirm the new RPC does, in fact, work with the new bindings.

@jbrill jbrill force-pushed the update-deps-12-15-25 branch from bfe2b8e to 48cc963 Compare December 18, 2025 16:16
Copy link
Member

@jamaljsr jamaljsr left a comment

Choose a reason for hiding this comment

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

LGTM 🚀

Copy link
Collaborator

@ViktorT-11 ViktorT-11 left a comment

Choose a reason for hiding this comment

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

Nice, looks good 🚀!

Similar to #122, I think you want to include a last commit to this PR that bumps the version as well. We can do that in a separate PR though if needed, but I think it makes sense to do it in this PR.

@jbrill
Copy link
Author

jbrill commented Dec 19, 2025

Nice, looks good 🚀!

Similar to #122, I think you want to include a last commit to this PR that bumps the version as well. We can do that in a separate PR though if needed, but I think it makes sense to do it in this PR.

Huh I think this should be the same structure as #122 ? Were you looking at an old state of this PR by chance? Might be missing something!

{
"name": "@lightninglabs/lnc-web",
"version": "0.3.4-alpha",
"version": "0.3.5-alpha",
Copy link
Collaborator

Choose a reason for hiding this comment

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

Ah sorry, missed that and what I mean that this specific change should be in a separate commit that bumps the version only. We want that commit to be the last commit before the merge commit, as we don't want any additional changes to have happened in the commit tree after the version has been bumped. This is currently placed as the second last commit.

Hope that makes it more clear :)!

Copy link
Author

Choose a reason for hiding this comment

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

That makes sense! Thanks for the clarification!

I've addressed this PR with that structure -- I hope it looks ok now 🙏

@jbrill jbrill force-pushed the update-deps-12-15-25 branch from 48cc963 to 29f0a5b Compare December 19, 2025 18:12
@jbrill jbrill requested a review from ViktorT-11 December 19, 2025 18:13
Copy link
Collaborator

@ViktorT-11 ViktorT-11 left a comment

Choose a reason for hiding this comment

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

Nice, thanks for the change 🎉. LGTM 🔥

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.

4 participants