build: bump version to v0.7.99-alpha

[Roasbeef]

Bump version to v0.7.99-alpha so that master builds are distinguishable from release builds.

[gemini-code-assist]

Summary of Changes

Hello @Roasbeef, 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 a minor but important build configuration update. By incrementing the patch version to 99 and maintaining the alpha status, the change aims to clearly differentiate development builds from the master branch from any official releases. This practice is crucial for maintaining clarity in the development lifecycle and preventing confusion between stable and in-progress versions.

Highlights

• Version Bump: The application version has been updated to v0.7.99-alpha.
• Build Distinguishability: This version change ensures that builds originating from the master branch are clearly distinguishable from official release builds.

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

[gemini-code-assist]

Code Review

This pull request updates the application patch version to 99 in version.go. This change sets the development version string to v0.7.99-alpha, aligning with the stated goal of making master builds distinguishable from release builds. The change is straightforward and correct, and I have no specific feedback.

[coveralls]

Pull Request Test Coverage Report for Build 20765619590

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 86 unchanged lines in 20 files lost coverage.
• Overall coverage decreased (-0.002%) to 56.974%

---

Files with Coverage Reduction	New Missed Lines	%
rfqmsg/records.go	1	71.05%
lndservices/block_header_cache.go	2	97.52%
tapdb/sqlc/transfers.sql.go	2	82.65%
tapdb/sqlc/universe.sql.go	2	73.71%
tapdb/universe_federation.go	2	88.96%
itest/assertions.go	3	87.42%
itest/multisig.go	3	97.94%
tapchannel/aux_leaf_signer.go	3	43.18%
tapgarden/planter.go	3	80.26%
universe/supplycommit/env.go	3	75.6%

Totals
Change from base Build 20468127774:	-0.002%
Covered Lines:	65509
Relevant Lines:	114981

---

💛 - Coveralls

[jtobin]

This convention looks a little unusual to me, but I guess that's the point. 😁

LGTM if this is already being used in lnd, in particular; a unified presentation for this type of thing is desirable.