Skip to content

docs: Release notes updated to remove entries for coop close reorg ha…#10533

Open
saubyk wants to merge 1 commit intolightningnetwork:masterfrom
saubyk:20.1-releasenotes-fix
Open

docs: Release notes updated to remove entries for coop close reorg ha…#10533
saubyk wants to merge 1 commit intolightningnetwork:masterfrom
saubyk:20.1-releasenotes-fix

Conversation

@saubyk
Copy link
Collaborator

@saubyk saubyk commented Jan 31, 2026

Release notes update in the master for 0.20.1.

Removed the entries for the coop close reorg handling change which was rolled back from the release scope.

@saubyk saubyk added this to the v0.20.1 milestone Jan 31, 2026
@saubyk saubyk self-assigned this Jan 31, 2026
@saubyk saubyk added the documentation Documentation changes that do not affect code behaviour label Jan 31, 2026
@saubyk saubyk requested a review from ziggie1984 January 31, 2026 00:32
@gemini-code-assist
Copy link

Summary of Changes

Hello @saubyk, 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 updates the release notes for version 0.20.1 to accurately reflect the final scope of the release. It removes specific feature descriptions that were initially planned but later excluded, ensuring that the documentation aligns with the shipped product.

Highlights

  • Release Notes Correction: Removed two entries from the 0.20.1 release notes that pertained to changes which were ultimately rolled back from the release scope.
  • Cooperative Close Reorg Handling: The entry detailing 'Improved confirmation scaling for cooperative closes' was removed from the release notes.
  • MinCLTVDelta Increase: The entry describing the 'Increased MinCLTVDelta from 18 to 24' was removed from the release notes.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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.

@saubyk saubyk added the backport-v0.20.x-branch This label is used to trigger the creation of a backport PR to the branch `v0.20.x-branch`. label Jan 31, 2026
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 updates the release notes for version 0.20.1. The changes involve removing entries for features that have been rolled back from this release, specifically the 'Improved confirmation scaling for cooperative closes' and the 'Increased MinCLTVDelta' breaking change. The modifications are correct and align with the PR's objective of keeping the release notes accurate. The resulting document is clean and I have no further suggestions.

ensures dependencies are properly freed and logs the panic trace for
debugging.

* [Improved confirmation scaling for cooperative
Copy link
Collaborator

Choose a reason for hiding this comment

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

you need to move them to 21

@saubyk saubyk removed the backport-v0.20.x-branch This label is used to trigger the creation of a backport PR to the branch `v0.20.x-branch`. label Feb 6, 2026
@saubyk saubyk modified the milestones: v0.20.1, v0.21.0 Feb 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Documentation changes that do not affect code behaviour

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants