WIP: go.mod: bump lnd, loop, taproot-assets, taprpc, lndclient

[ffranr]

Work in progress. PR opened for early CI feedback.

Target Versions

• [email protected]
• [email protected]
• [email protected]
• taproot-assets/[email protected]
• [email protected]

Remaining Steps

• Tag [email protected] and taproot-assets/[email protected] on main in tap.
• Update the loop PR with the new tap tags, merge it, then cut the loop tag.
• Update this PR with the final tags for loop, taproot-assets, and taproot-assets/taprpc, then merge this PR.

[gemini-code-assist]

Summary of Changes

Hello @ffranr, I'm Gemini Code Assist¹! 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 focuses on updating the project's Go module dependencies to newer versions. The changes ensure that the application integrates the latest iterations of critical components like lndclient, taproot-assets, taprpc, and runc, which can bring improved stability, performance, or new features. This is an initial step to validate the compatibility of these updates within the project's CI environment.

Highlights

• Dependency Updates: The go.mod file has been updated to bump several key dependencies, including lndclient, taproot-assets, taprpc, and runc to their latest versions.
• Work in Progress: This pull request is marked as a Work in Progress, primarily opened to gather early continuous integration feedback on the dependency changes.

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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

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 pull request 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. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

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

[gemini-code-assist]

Code Review

This pull request updates several dependencies in go.mod, including lndclient, taproot-assets, and taprpc. The changes look good overall. I've added one comment regarding a version inconsistency for taprpc in the litrpc submodule that should be addressed to keep the workspace tidy. Additionally, for clarity, you might want to update the PR title to reflect that taproot-assets is being bumped to a pseudo-version rather than the v0.7.0 release tag.

[ffranr]

I'll update this PR once we have new tags for tap.

[ViktorT-11]

Just FYI @ffranr, itests are failing as we need this fix:
#1170
& the dependent lndclient PR:
lightninglabs/lndclient#255

In order to use lnd v0.20.0-beta.rc3+.

[darioAnongba]

doesn't make sense to keep this update in the changelog right? Since 0.16.0 updates to 0.20.0-beta and not 0.20.0-beta.rc2

[ffranr]

I've been thinking about that also. I think it would be unnecessarily costly to, as standard, reconcile the release doc across all changes such that it reflected the final release state only. Personally, i think that it's sufficient that it's a sort of append only list of changes.

[darioAnongba]

Same remark here

[darioAnongba]

and here