Skip to content

Conversation

@guggero
Copy link
Contributor

@guggero guggero commented Sep 28, 2023

Copy link
Member

@ellemouton ellemouton left a comment

Choose a reason for hiding this comment

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

LGTM pending LiT version bump and Readme update.

Think we should also include these readme updates here: #543

@guggero
Copy link
Contributor Author

guggero commented Oct 3, 2023

Updated the README and also added a version bump for litd itself.

@guggero guggero requested a review from ellemouton October 3, 2023 15:25
Copy link
Contributor

@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.

tACK LGTM!

Tested the sessions, loop & pool flow with the new changes, and those seems to be working as expected!

Very nitty: I think the last 2 commits can be squashed into 1, but definitely not a blocker :)!

Just wanted to sanity check, since the description of the PR doesn't mention that this is dependent on lightninglabs/taproot-assets#536, but depends on all other bumps, should that not be the case?


| LiT | LND | Loop | Faraday | Pool | Taproot Assets |
|-------------------|--------------|--------------|---------------|--------------|----------------|
| **v0.11.0-alpha** | v0.17.0-beta | v0.26.3-beta | v0.2.11-alpha | v0.6.4-beta | v0.2.3-alpha |
Copy link
Contributor

@ViktorT-11 ViktorT-11 Oct 3, 2023

Choose a reason for hiding this comment

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

nit: taproot assets included is at v0.2.4.0.XXX in the go.mod file

Copy link
Contributor Author

Choose a reason for hiding this comment

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

You're right, Taproot Assets is a bit of an outlier here. Should've added that to the PR description: Since we're very close to releasing v0.3, we will be doing another litd release soon. But because a lot of things in the main branch for the v0.3 release are breaking changes, we need to stay on a v0.2.3 base for now. So I just pushed a branch with the lnd update and didn't create a PR for it, as we couldn't merge it anywhere anyway. But as soon as v0.3 is out, everything will be smooth again.

Oh and the v0.2.4 is just a weird thing go modules does, when it uses a commit based pseudo version, it actually increases the patch version. The closest tag to the commit used is actually v0.2.3, there is no v0.2.4.

Copy link
Contributor

Choose a reason for hiding this comment

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

Ah ok, makes sense. Thanks for explaining!

Copy link
Member

@ellemouton ellemouton left a comment

Choose a reason for hiding this comment

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

LGTM 🔥 tACK - tested the autopilot flow 👍

@guggero guggero changed the title multi: bump lnd to v0.17.0-beta.rc5 multi: bump lnd to v0.17.0-beta Oct 3, 2023
@guggero guggero requested a review from jamaljsr October 3, 2023 17:55
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.

tACK LGTM 🚀

Tested Loop & Pool UIs as well as integrated/remote modes w/ LND v0.17.

Great speedy work!!

@guggero guggero merged commit 8d7c53b into master Oct 3, 2023
@guggero guggero deleted the lnd-17-update branch October 3, 2023 18:21
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