Skip to content

release: prepare for v0.15.2-alpha.rc1 that contains lnd v0.19.3-alpha.rc1 #1130

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 5 commits into from
Aug 11, 2025

Conversation

guggero
Copy link
Member

@guggero guggero commented Aug 8, 2025

We want to be able to test lnd v0.19.3-alpha.rc1 within litd as early as possible, so we create an RC here as well.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Summary of Changes

Hello @guggero, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

I've prepared this release candidate for litd version v0.15.2-alpha.rc1. The primary purpose of this update is to integrate and allow for early testing of lnd v0.19.3-alpha.rc1 within litd. This involves updating the application's internal versioning and adjusting the lnd dependency in the Go modules. Additionally, the README.md has been synchronized to reflect these new version compatibilities.

Highlights

  • LiT Version Update: The LiT application's version has been updated to v0.15.2-alpha.rc1.
  • LND Dependency Upgrade: The lnd dependency has been upgraded to v0.19.3-beta.rc1 to facilitate early testing within litd.
  • Documentation Update: The README.md file has been updated to reflect the new LiT and LND version compatibility.
  • Go Module Dependency Updates: Minor dependency updates for btclog/v2 and btcwallet have been included.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments or fill out our survey to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@guggero
Copy link
Member Author

guggero commented Aug 8, 2025

We should probably get #1128 in as well before merging this.

Copy link

Warning

Gemini encountered an error creating the review. You can try again by commenting /gemini review.

Copy link
Contributor

@ViktorTigerstrom ViktorTigerstrom left a comment

Choose a reason for hiding this comment

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

LGTM! Could potentially bump the lnd version in the /litrpc + /perms package as well, but ok from my end as is since this is only an rc release. Will hit the ACK button once I've completed testing in combination with #1128

@ViktorTigerstrom
Copy link
Contributor

Could also add an entry for the lnd bump in the release notes.

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!! thanks 🙏

Copy link
Contributor

@ViktorTigerstrom ViktorTigerstrom left a comment

Choose a reason for hiding this comment

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

Nice, LGTM 🎉!

@guggero guggero merged commit f71840e into master Aug 11, 2025
82 of 86 checks passed
@guggero guggero deleted the lnd-19-3-rc1 branch August 11, 2025 06:42
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.

3 participants