[SergK]

Pull Request

Description

Bump the toolchain to Go 1.26.9:

• go.mod: 1.26.2 -> 1.26.9
• README.md: documented Go prerequisite 1.24+ -> 1.26+
• actions/setup-go v5 -> v7 in the codeql and release workflows (action.yml is unchanged, no input changes)
• check-latest: true on every setup-go step so the runner resolves the newest 1.26.x instead of a cached older patch (go.mod requires >= 1.26.9)

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

go build ./..., go vet ./..., go test ./... and make lint (0 issues) pass on Go 1.26.9.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I have squashed my commits

[epmd-edp]

Pipeline review-gitfusion-main-jvpgj — ✓ Passed

Status	Task	Duration
✓ Passed	github-set-pending-status	6s
✓ Passed	fetch-repository	18s
✓ Passed	init-values	6s
✓ Passed	get-cache	7s
✓ Passed	commit-validate	5s
✓ Passed	dockerfile-lint	7s
✓ Passed	helm-lint	6s
✓ Passed	helm-docs	15s
✓ Passed	build	2m17s
✓ Passed	sonar	16s
✓ Passed	buildkit-verify	14s
✓ Passed	save-cache	36s
✓ Passed	github-report-pipeline-status	6s

Pushing new commits re-runs this pipeline automatically.
To re-run it without new commits, comment /recheck.