Skip to content

build: bump version to v0.20.1#10551

Merged
ziggie1984 merged 1 commit intov0.20.x-branchfrom
v-0-20-1-final
Feb 10, 2026
Merged

build: bump version to v0.20.1#10551
ziggie1984 merged 1 commit intov0.20.x-branchfrom
v-0-20-1-final

Conversation

@Roasbeef
Copy link
Copy Markdown
Member

@Roasbeef Roasbeef commented Feb 4, 2026

No description provided.

@gemini-code-assist
Copy link
Copy Markdown

Summary of Changes

Hello @Roasbeef, 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 simplifies the application's pre-release version string by removing the release candidate identifier. This change streamlines the versioning scheme, reflecting a progression in the development cycle.

Highlights

  • Version Update: The AppPreRelease constant in build/version.go has been updated from "beta.rc1" to "beta".

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

Changelog
  • build/version.go
    • Updated the AppPreRelease constant from "beta.rc1" to "beta".
Activity
  • No specific activity (comments, reviews, progress) has been recorded for this pull request yet.
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.

Copy link
Copy Markdown

@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 application's pre-release version identifier. My review highlights a potential mismatch between the resulting version string (0.20.1-beta) and the pull request title, which seems to imply a final release (v0.20.1). I've suggested setting the pre-release identifier to an empty string if a final release is indeed the goal.

Comment thread build/version.go
@lightninglabs-deploy
Copy link
Copy Markdown
Collaborator

🟢 PR Severity: LOW

Version bump | 1 file | 2 lines changed

🟢 Low (1 file)
  • build/version.go - Version bump to v0.20.1 (build metadata)

Analysis

This PR is a straightforward version bump that modifies only build/version.go to update the version string from v0.20.0 to v0.20.1. This is a standard release preparation change that:

  • Contains no logic changes
  • Affects only build metadata
  • Has minimal risk of introducing bugs
  • Requires only best-effort review to verify the version string is correct

Severity: LOW - This is routine release infrastructure work suitable for best-effort review.


To override, add a severity-override-{critical,high,medium,low} label.

@ziggie1984
Copy link
Copy Markdown
Collaborator

needs a rebase

@Roasbeef
Copy link
Copy Markdown
Member Author

Roasbeef commented Feb 5, 2026

Blocking on this so we can add #10540

Copy link
Copy Markdown
Collaborator

@saubyk saubyk left a comment

Choose a reason for hiding this comment

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

Ack

@lightninglabs-deploy
Copy link
Copy Markdown
Collaborator

🟢 PR Severity: LOW

version bump | 1 file | 2 lines changed

🟢 Low (1 file)
  • build/version.go - Version metadata file (trivial change)

Analysis

This PR is a straightforward version bump from v0.20.0 to v0.20.1, modifying only the version constant in build/version.go. This is purely metadata and does not affect any runtime behavior, protocol logic, or critical systems.

Severity Justification:

  • Single configuration file change
  • No functional code modifications
  • Standard release process task
  • Minimal risk

This qualifies for LOW severity as it falls under build configuration changes that require only best-effort review.


To override, add a severity-override-{critical,high,medium,low} label.

Copy link
Copy Markdown
Collaborator

@ziggie1984 ziggie1984 left a comment

Choose a reason for hiding this comment

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

LGTM

@ziggie1984 ziggie1984 merged commit 848b72c into v0.20.x-branch Feb 10, 2026
39 of 40 checks passed
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.

4 participants