[MrHinsh]

Separate Prepare and Build jobs can select different Go patch versions from runner-local caches when setup-go receives >=1.24.5. OGP's tool-identity check correctly rejected the v1.1.3 release: the first attempt used 1.26.9 then 1.26.10, and the fresh retry reversed those versions.

Pin all three CI setup-go steps to 1.26.10 so the platform build and guide-site stages select the same executable. Preserve tool-identity checks, action tags, product minimums, triggers, secrets and deployment behavior. Dependency-lock regeneration leaves the lockfile unchanged.

Validation: full root acceptance exited 0: 578 tests passed, three existing skips; extracted packages, reference preview/production and both packaged contributor workflows passed; independent read-only diff review completed with no findings. The pinned version is present in the official setup-go manifest. Hosted Prepare/Build and the release pipeline must confirm the actual outcome before publication.

Summary by CodeRabbit

• Chores
  • Build workflows now use a fixed Go version, providing consistent tooling across the site and application build processes.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-22T14:31:54.058622Z	8076c7f	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: ca5d33e1-d210-47c2-9a6f-6859bfd284be

📥 Commits

Reviewing files that changed from the base of the PR and between 2da3865 and 8076c7f.

📒 Files selected for processing: 2

• .github/workflows/guide-site-build.yaml
• .github/workflows/main.yaml

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

Walkthrough

The main and guide-site build workflows now pin Go to version 1.26.10. Their setup steps include comments about executable identity verification and runner caches.

Changes

Go CI version

Layer / File(s)	Summary
Pin Go across CI workflows .github/workflows/main.yaml, .github/workflows/guide-site-build.yaml	The Go setup steps now specify version 1.26.10 instead of >=1.24.5. Comments describe executable identity verification and runner cache behaviour.

Priority: ⬆️ High

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Bug fix

Merge Risk: ⚪ Minimal · up to 8076c

The CI workflows consistently select an available Go version with no concrete merge-blocking risk identified.

Pre-merge checks: 5

Check name	Status	Explanation
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.
Title check		The title clearly and concisely describes the main change: keeping CI Go tooling identical across workflow stages by pinning the same Go version.
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (2 skipped: 2 unsupported.)

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

_{Three workflows steps hold Go in place
At one exact version, set with care
Identity checks are noted there
Runner caches cannot choose a patch
The builds proceed with pinned Go matches}

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

[github-actions]

Prepare completed. Workflow evidence. This is the candidate assessment, not independent policy or deployment approval.

Prepare: pass

Commit: 8076c7f · Platform: 1.1.4-PullRequest58.1 · Target: canary

Selection: v1.1.4-PullRequest58.1; resolved: v1.1.4-PullRequest58.1; OGP ring: preview.

Severity	Scope	Subject	Finding	What to fix
warning	platform	github.com/nkdAgility/OpenGuidePlatform/system/OpenGuidePlatform.Hugo.Guides	MODULE_FRESHNESS_UNAVAILABLE: Could not establish module freshness: Go module query failed (1): go: module github.com/nkdAgility/OpenGuidePlatform/system/OpenGuidePlatform.Hugo.Guides: not a known dependency	Review the module version through the coordinated platform update process; never change the pin during Prepare.

Guide status

No guide fixes identified by these checks.

Artifact and live-site checks run in later stages.

[github-actions]

Preview deployed for commit 8076c7f: https://blue-field-06cea8c03-58.westeurope.6.azurestaticapps.net/. Live verification follows in Actions.