docs: Add new release notes for v0.17.1-alpha#1355
Conversation
Summary of ChangesHello, 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
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 AssistThe 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
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 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
|
There was a problem hiding this comment.
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.
| * [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. |
There was a problem hiding this comment.
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
left a comment
There was a problem hiding this comment.
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.
59417e8 to
7604bd2
Compare
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 forv0.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-alphadespite not being part of that release.