[AdarshK15]

Slurm Security Patches: Upgraded Slurm to version 25.11.8 to address multiple CVEs:

CVE-2026-65107: Fixes sbcast shared objects skipping credential verification and addresses a possible slurmd crash on invalid sbcast filenames.
CVE-2026-65108: Fixes a slurmstepd stack overflow when a job environment contains an oversized SPANK option variable.
CVE-2026-65109: Fixes slurmstepd removing files outside the container spool directory when cleaning up an OCI container, and prevents leaving spool directories behind when ContainerPath contains a task id pattern.
CVE-2026-65138: Fixes a heap over-read when unpacking a malformed forward data RPC in slurmd, as well as a slurmd crash when handling a malformed forward data RPC with a missing socket address.
CVE-2026-65139: Enhance accounting database security by rejecting non-numeric ID values and validating cluster names against unsafe characters during queries, slurmdbd connections, and accounting usage, add, or runaway job paths.
CVE-2026-65140: Fixes a privilege escalation where an operator could alter Administrator accounts through the accounting database.
CVE-2026-65165: Fixes the node count for job steps that use an arbitrary distribution. It also rejects these job steps if they contain a hostlist function in their node list or if their node list disagrees with the node count.
CVE-2026-65168: Fixes a possible slurmstepd crash on invalid step socket requests.

[gemini-code-assist]

Summary of Changes

Hello, 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 updates the Slurm-GCP reference version to 6.12.3 across the repository's example blueprints and documentation. This ensures that deployments utilize the latest stable version of the Slurm-GCP integration.

Highlights

• Slurm Version Upgrade: Updated the Slurm reference version from 6.12.1 to 6.12.3 across various configuration files and documentation.

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

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 Slurm Git reference version from 6.12.1 to 6.12.3 across various example blueprints, configuration files, and documentation READMEs. As there are no review comments, I have no feedback to provide.

[arpit974]

LGTM,
please run tests.