build with go 1.26

[mwennrich]

• build with go 1.26
• update deps
• update gh actions
• go fix

[gemini-code-assist]

Summary of Changes

Hello @mwennrich, 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 modernizing the project's build environment and codebase by upgrading to Go 1.26. This update involves adjusting the Go module definition and the Docker build image. Additionally, it leverages new language features by refactoring map manipulation to use the maps.Copy function, streamlining the code and aligning with current Go best practices.

Highlights

• Go Version Upgrade: The project's Go version has been upgraded from 1.25 to 1.26 across the Dockerfile and go.mod.
• Code Modernization: Map merging logic in alertlogger.go was refactored to utilize the new maps.Copy function, improving conciseness and efficiency.
• Dependency Updates: Dependencies were implicitly updated as part of the Go version bump and go fix operations, ensuring compatibility with Go 1.26.
• GitHub Actions: The PR description mentions updating GitHub Actions, though no related file changes were provided in the patch.

🧠 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

• Dockerfile
  • Updated the base Go image to version 1.26.
• alertlogger.go
  • Imported the maps package.
  • Refactored map merging logic to use maps.Copy for alert.Labels and alert.Annotations.
• go.mod
  • Updated the Go module's declared version to 1.26.

Ignored Files

• Ignored by pattern: .github/workflows/** (5)
  • .github/workflows/ghcr.yaml
  • .github/workflows/latest.yaml
  • .github/workflows/pull_request.yaml
  • .github/workflows/release-drafter.yaml
  • .github/workflows/release.yaml

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 project to build with Go 1.26. The changes include updating the Go version in the Dockerfile and go.mod, and refactoring the code to use the maps.Copy function. The changes are correct and improve code readability. The update is well-executed and I have no comments.