Skip to content

Prepare for release of v0.15.1-alpha final #1115

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 4 commits into from
Jul 16, 2025
Merged

Conversation

guggero
Copy link
Member

@guggero guggero commented Jul 16, 2025

No description provided.

@guggero guggero requested review from jamaljsr and ellemouton July 16, 2025 14:58
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!

This pull request serves as the final preparation step for the v0.15.1-alpha release. It primarily involves updating the application's internal version, upgrading several core daemon dependencies to their latest stable or release candidate versions, and aligning the documentation to reflect these changes. Additionally, it incorporates a new channel event type into the LND protobufs, enhancing channel state monitoring.

Highlights

  • LiT Application Version Finalization: The application's internal version string has been updated from v0.15.1-alpha.rc1 to v0.15.1-alpha, signifying the finalization of this alpha release.
  • Daemon Dependency Upgrades: Key bundled daemons have been upgraded: LND is now v0.19.2-beta (from v0.19.2-beta.rc2), and the Taproot Assets Daemon (tapd) is updated to v0.6.1-alpha.
  • LND Protobuf Enhancements: A new CHANNEL_FUNDING_TIMEOUT event type has been added to the LND protobuf definitions, allowing for better handling of channel lifecycle events.
  • Documentation Alignment: The README.md and release notes have been updated to reflect the new version numbers and daemon dependencies, ensuring consistency.
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 is currently in preview and 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 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.

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.

Code Review

This pull request prepares for the v0.15.1-alpha release. The changes primarily consist of version bumps in version.go, go.mod, go.sum, and documentation updates in README.md and the release notes. The versions are consistent across all files. The protobuf definitions and generated TypeScript types are also updated to reflect changes from the upstream lnd dependency. The changes look correct and ready for the release.

@guggero guggero force-pushed the lnd-19-2-tapd-0-6-1 branch 2 times, most recently from cea5f93 to fc297ba Compare July 16, 2025 15:21
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 👌

@guggero guggero force-pushed the lnd-19-2-tapd-0-6-1 branch from fc297ba to b21046f Compare July 16, 2025 16:44
@guggero guggero merged commit 60a2b65 into master Jul 16, 2025
22 checks passed
@guggero guggero deleted the lnd-19-2-tapd-0-6-1 branch July 16, 2025 18:38
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