[PR #6992] ci(real-go-binary): pin Go 1.26.10 #7555

Open
opened 2026-11-03 13:38:40 +00:00 by bsakaguchi · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/6992
Author: @lotar
Created: 10/24/2026
Status: 🔄 Open

Base: main ← Head: chore/ci-go-1.26.10


📝 Commits (1)

  • 39fa428 ci: pin real-go-binary Go toolchain to 1.26.10

📊 Changes

1 file changed (+1 additions, -1 deletions)

View changed files

📝 .github/workflows/real-go-binary.yml (+1 -1)

📄 Description

Summary

Pin the Go toolchain used by the real-go-binary workflow to the current 1.26 patch release.

Problem and expected behavior

.github/workflows/real-go-binary.yml pins Go 1.26.1. Go 1.26.10 is the latest 1.26 patch release on go.dev/dl and carries the toolchain/stdlib security fixes released since 1.26.1. Expected: the job builds its fixture binary with 1.26.10.

Change and scope

One-line change: go-version 1.26.1 -> 1.26.10. Nothing else; no product code, no new capability. Scope decision: not applicable (CI maintenance within existing boundaries).

Contract and boundary impact

  • Semantic owner and earliest changed stage: CI workflow only

  • Contribution scope fit and linked maintainer decision: not applicable

  • CLI and MCP/tool-catalog contract: none

  • Provider, bridge, target-format, or platform compatibility: Go fixture binary is built with a newer 1.26 patch release

  • Evidence, artifact, provenance, or reconstruction contract: none

  • Target selection, authority, upstream behavior, and cleanup details: not applicable

  • Generated metadata, package, or installation impact: none

  • Read existing files or captured data.

  • Launch or attach to a process.

  • Inject instrumentation or run scripts/code.

  • Change process memory, registers, files, or configuration.

  • Contact network services.

  • Recover protected code or work around protections.

  • Documentation or usability only; no target interaction.

  • Not sure yet; investigation or maintainer guidance needed.

Evidence and regression coverage

Source-derived: workflow YAML parses; go1.26.10 is listed on go.dev/dl. The Go job itself was not executed locally. Opened as a draft; readiness and merge checklists left for the maintainer.

  • Tests added or updated: none (CI toolchain pin only)
  • Base reproduction or other evidence: source-derived; real-go-binary.yml on main pins go-version: 1.26.1; go1.26.10 is published on go.dev/dl
  • User-visible CLI/MCP output (if applicable): not applicable
  • Remaining proof gaps: the real-go-binary job itself has not been executed with 1.26.10 (Go not installed on the authoring machine); this PR's CI run is the first execution

For evidence-bearing changes:

  • Observed, derived, and inferred claims remain distinguishable.
  • Artifact identity, source provenance, and failed attempts remain preserved.
  • Unsupported, incomplete, unavailable, or uncertain outcomes remain visible.

Validation performed

  • YAML parse of .github/workflows/real-go-binary.yml — parses
  • Diff vs main — 1 line changed (go-version)
  • Greptile review — 5/5, no actionable defect

Compatibility, safety, and release

  • Breaking changes or migration steps: none
  • Real Hopper/Ghidra, browser, or OS coverage: not applicable
  • Package or release metadata impact: none
  • Security, privacy, process, or containment review: picks up Go 1.26.x patch-release security fixes for the CI-built fixture binary; no product code change

Author readiness

Human owner: @lotar (declarations below dictated by the owner to an AI agent, 2026-10-24)

  • I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work.
  • I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps.
  • I declare this PR ready for initial maintainer review.

Before merge

  • This PR addresses a concrete problem or an agreed enhancement.
  • Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff.
  • The PR has one focused outcome and the title follows type(scope): outcome.
  • Related issue is linked, or the reason for not linking one is stated above.
  • Tests cover changed observable behavior and meaningful failure paths.
  • Owning docs, contracts, and generated metadata are updated where needed.
  • User-visible CLI/MCP changes include representative output.
  • I checked the final diff for secrets, unrelated cleanup, and unsupported claims.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/6992 **Author:** [@lotar](https://github.com/lotar) **Created:** 10/24/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `chore/ci-go-1.26.10` --- ### 📝 Commits (1) - [`39fa428`](https://github.com/morluto/rea/commit/39fa42862e9fc669bdefdcd75ae39e26d0385425) ci: pin real-go-binary Go toolchain to 1.26.10 ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/real-go-binary.yml` (+1 -1) </details> ### 📄 Description ## Summary Pin the Go toolchain used by the `real-go-binary` workflow to the current 1.26 patch release. ## Problem and expected behavior `.github/workflows/real-go-binary.yml` pins Go 1.26.1. Go 1.26.10 is the latest 1.26 patch release on go.dev/dl and carries the toolchain/stdlib security fixes released since 1.26.1. Expected: the job builds its fixture binary with 1.26.10. ## Change and scope One-line change: `go-version` 1.26.1 -> 1.26.10. Nothing else; no product code, no new capability. Scope decision: not applicable (CI maintenance within existing boundaries). ## Contract and boundary impact - Semantic owner and earliest changed stage: CI workflow only - Contribution scope fit and linked maintainer decision: not applicable - CLI and MCP/tool-catalog contract: none - Provider, bridge, target-format, or platform compatibility: Go fixture binary is built with a newer 1.26 patch release - Evidence, artifact, provenance, or reconstruction contract: none - Target selection, authority, upstream behavior, and cleanup details: not applicable - Generated metadata, package, or installation impact: none - [ ] Read existing files or captured data. - [ ] Launch or attach to a process. - [ ] Inject instrumentation or run scripts/code. - [ ] Change process memory, registers, files, or configuration. - [ ] Contact network services. - [ ] Recover protected code or work around protections. - [ ] Documentation or usability only; no target interaction. - [ ] Not sure yet; investigation or maintainer guidance needed. ## Evidence and regression coverage Source-derived: workflow YAML parses; go1.26.10 is listed on go.dev/dl. The Go job itself was not executed locally. Opened as a draft; readiness and merge checklists left for the maintainer. - Tests added or updated: none (CI toolchain pin only) - Base reproduction or other evidence: source-derived; `real-go-binary.yml` on main pins `go-version: 1.26.1`; go1.26.10 is published on go.dev/dl - User-visible CLI/MCP output (if applicable): not applicable - Remaining proof gaps: the `real-go-binary` job itself has not been executed with 1.26.10 (Go not installed on the authoring machine); this PR's CI run is the first execution For evidence-bearing changes: - [ ] Observed, derived, and inferred claims remain distinguishable. - [ ] Artifact identity, source provenance, and failed attempts remain preserved. - [ ] Unsupported, incomplete, unavailable, or uncertain outcomes remain visible. ## Validation performed - YAML parse of `.github/workflows/real-go-binary.yml` — parses - Diff vs `main` — 1 line changed (`go-version`) - Greptile review — 5/5, no actionable defect ## Compatibility, safety, and release - Breaking changes or migration steps: none - Real Hopper/Ghidra, browser, or OS coverage: not applicable - Package or release metadata impact: none - Security, privacy, process, or containment review: picks up Go 1.26.x patch-release security fixes for the CI-built fixture binary; no product code change ## Author readiness Human owner: @lotar (declarations below dictated by the owner to an AI agent, 2026-10-24) - [x] I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work. - [x] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps. - [x] I declare this PR ready for initial maintainer review. ## Before merge - [ ] This PR addresses a concrete problem or an agreed enhancement. - [ ] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [ ] The PR has one focused outcome and the title follows `type(scope): outcome`. - [ ] Related issue is linked, or the reason for not linking one is stated above. - [ ] Tests cover changed observable behavior and meaningful failure paths. - [ ] Owning docs, contracts, and generated metadata are updated where needed. - [ ] User-visible CLI/MCP changes include representative output. - [ ] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#7555
No description provided.