[Snyk] Security upgrade golang from latest to 1.26rc2

[Dustin4444]

Snyk has created this PR to fix 5 vulnerabilities in the dockerfile dependencies of this project.

Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.

Snyk changed the following file(s):

• Dockerfile.pytest

We recommend upgrading to golang:1.26rc2, as this image has only 121 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.

Vulnerabilities that will be fixed with an upgrade:

	Issue
	CVE-2025-69421 SNYK-DEBIAN13-OPENSSL-15123186
	CVE-2026-22796 SNYK-DEBIAN13-OPENSSL-15123187
	CVE-2025-68160 SNYK-DEBIAN13-OPENSSL-15123204
	CVE-2025-69420 SNYK-DEBIAN13-OPENSSL-15123205
	CVE-2026-22795 SNYK-DEBIAN13-OPENSSL-15123206

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[gemini-code-assist]

Summary of Changes

Hello @Dustin4444, 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, automatically generated by Snyk, aims to enhance the security of the project's Docker build environment by updating the golang base image. The upgrade addresses multiple identified vulnerabilities, ensuring the project benefits from the latest security fixes in its dependencies.

Highlights

• Dependency Upgrade: Upgraded the golang base image from latest to 1.26rc2 in Dockerfile.pytest to resolve 5 low-severity security vulnerabilities.

🧠 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.pytest
  • Updated the base image from golang:latest to golang:1.26rc2.

Activity

• This pull request was automatically created by Snyk to propose a security upgrade based on identified vulnerabilities.

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

[coderabbitai]

Important

Review skipped

Ignore keyword(s) in the title.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

• 🔍 Trigger a full review

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch snyk-fix-6187cfd831b10c2f099608bb49ebc7e6

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Code Review

This pull request updates the golang base image in Dockerfile.pytest from latest to 1.26rc2 to address security vulnerabilities. While pinning dependencies is a good practice, this change introduces a release candidate (rc) version. My review highlights the stability risks of using a pre-release version and recommends using a stable release instead. If the rc version is necessary, I suggest documenting the reason and planning an upgrade to the stable version once it's available.

[gemini-code-assist]

Using a release candidate (rc) version for a base image can introduce instability, as these are pre-release versions not intended for production use. It is highly recommended to use a stable release of Go. If this rc version is intentionally chosen to mitigate security vulnerabilities not yet fixed in stable releases, consider adding a comment to the Dockerfile to document this decision and plan to upgrade to the stable 1.26.0 release as soon as it becomes available.