Skip to content

Bump litd to version v0.13.4-alpha #843

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

Conversation

ViktorTigerstrom
Copy link
Contributor

This PR bumps the litd version to v0.13.4-alpha.

This PR also bumps lnd to version v0.18.3-beta & loop v0.28.7-beta.

As lnd v0.18.3-beta adds explicitly declared optional protos fields with commit lightningnetwork/lnd@3de6c54, we this PR also needed to update the protoc version used for the protos generation script. Optional proto fields are only available in Proto3 after protoc version 3.15+.

When doing so, we mimic the protobuf-compiler version used in lnd, which is 3.21.12. As protobuf-compiler 3.21.x+ is only available for Node.js base images with Debian 12 (bookworm), we also update our NodeJS base image to version 22.8.0-bookworm.

@@ -1,10 +1,10 @@
# Start with a NodeJS base image that also contains yarn.
FROM node:16.14.2-buster as nodejsbuilder
FROM node:22.8.0-bookworm as nodejsbuilder
Copy link
Contributor Author

Choose a reason for hiding this comment

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

@jamaljsr, let me know if you think this NodeJS base image version is ok, or if you'd like me to use 18.20-bookworm instead :)!

Copy link
Member

Choose a reason for hiding this comment

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

I tested this and it works for me, so this is fine.

I would suggest bumping the image version in Dockerfile and dev.Dockerfile as well, just to be consistent.

@ViktorTigerstrom
Copy link
Contributor Author

Sorry, will solve the failing CI checks asap!

Copy link
Member

@guggero guggero left a comment

Choose a reason for hiding this comment

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

utACK, LGTM 🎉

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.

Looks good - just a release notes comment

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 the litd UI and Terminal UI over LNC. No issues on my end.

@@ -1,10 +1,10 @@
# Start with a NodeJS base image that also contains yarn.
FROM node:16.14.2-buster as nodejsbuilder
FROM node:22.8.0-bookworm as nodejsbuilder
Copy link
Member

Choose a reason for hiding this comment

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

I tested this and it works for me, so this is fine.

I would suggest bumping the image version in Dockerfile and dev.Dockerfile as well, just to be consistent.

In the next commit, we'll bump our lnd dependency to `v0.18.3-beta`.
That version adds explicitly declared optional protos fields with commit
lightningnetwork/lnd@3de6c54

Optional proto fields are only available in Proto3 after protoc version
`3.15+`, and we therefore need to bump our protoc version for the protos
generation script to support them.

When doing so, we mimic the protobuf-compiler version used in `lnd`,
which is `3.21.12`. As protobuf-compiler 3.21.x+ is only available for
Node.js base images with Debian 12 (bookworm), we also update our NodeJS
base image to version 22.8.0-bookworm.
Bump lnd to v0.18.3-beta & loop to v0.28.7-beta.
Also bump lnd/sqldb to v1.0.4, as it's required by lnd v0.18.3-beta.
@ViktorTigerstrom ViktorTigerstrom force-pushed the 2024-09-litd_0_13_4 branch 2 times, most recently from e8ab33a to c788a46 Compare September 16, 2024 06:13
@ViktorTigerstrom ViktorTigerstrom merged commit 414733c into lightninglabs:master Sep 16, 2024
13 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.

4 participants