Skip to content

docs: Add new release notes for v0.17.1-alpha#1355

Merged
ViktorT-11 merged 2 commits into
lightninglabs:masterfrom
ViktorT-11:2026-07-add-new-release-notes
Jul 16, 2026
Merged

docs: Add new release notes for v0.17.1-alpha#1355
ViktorT-11 merged 2 commits into
lightninglabs:masterfrom
ViktorT-11:2026-07-add-new-release-notes

Conversation

@ViktorT-11

Copy link
Copy Markdown
Contributor

This PR adds a release notes doc for v0.17.1-alpha, as we have many open PRs which still currently adds their respective release notes entry for the doc for v0.17.0-alpha, despite that release already being published.

We also move 2 entries that were accidentally merged to the doc for v0.17.0-alpha despite not being part of that release.

@ViktorT-11
ViktorT-11 requested a review from bitromortac July 16, 2026 11:33
@ViktorT-11 ViktorT-11 added the no-changelog This PR is does not require a release notes entry label Jul 16, 2026
@gemini-code-assist

Copy link
Copy Markdown

Summary of Changes

Hello, 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 initializes the release notes for version v0.17.1-alpha. It also cleans up the v0.17.0-alpha documentation by removing entries that were merged prematurely, ensuring that the release history accurately reflects the contents of each specific version.

Highlights

  • Release Notes Creation: Added a new release notes document for v0.17.1-alpha to track upcoming changes.
  • Documentation Cleanup: Removed two entries from the v0.17.0-alpha release notes that were incorrectly included and moved them to the new v0.17.1-alpha document.
New Features

🧠 You can now enable Memory (public preview) 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 the 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 counterproductive. 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.

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 gemini-code-assist Bot left a comment

Copy link
Copy Markdown

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 moves two release note entries from the 0.17.0 release notes to a new 0.17.1 release notes file. The review feedback suggests keeping inline code backticks on a single line in the markdown file to prevent potential rendering issues across different parsers.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

Comment on lines +30 to +32
* [Report litd's own version for `litd
-V`](https://github.com/lightninglabs/lightning-terminal/pull/1337): The `-V`
flag now prints litd's version instead of the integrated lnd version.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

medium

Splitting inline code backticks (`litd and -V`) across a line break can cause rendering issues in some Markdown parsers, potentially breaking the link or the code block formatting.

Consider keeping the inline code on a single line:

* [Report litd's own version for `litd -V`](https://github.com/lightninglabs/lightning-terminal/pull/1337):
  The `-V` flag now prints litd's version instead of the integrated lnd version.

@bitromortac bitromortac left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

We also move 2 entries that were accidentally merged to the doc for v0.17.0-alpha despite not being part of that release.

Ah right, thanks! Perhaps you could also update the contributor list.

Move the release note entries that were added after v0.17.0-alpha to the
v0.17.1 release notes.
@ViktorT-11
ViktorT-11 force-pushed the 2026-07-add-new-release-notes branch from 59417e8 to 7604bd2 Compare July 16, 2026 12:09
@ViktorT-11
ViktorT-11 merged commit 745f70f into lightninglabs:master Jul 16, 2026
22 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

no-changelog This PR is does not require a release notes entry

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants