Skip to content

ci: patch-pin Go toolchain in release workflow for reproducible provenance #40

@millerjp

Description

@millerjp

Summary

release.yml uses go-version: "1.26" which resolves to latest 1.26.x at dispatch. A silent minor bump between releases changes binary provenance for identical source — undermines attestation reproducibility arguments.

Scope

Pin release workflow to a specific 1.26.X (the version recorded in bench.txt). CI workflow keeps floating 1.26.

Acceptance criteria

  1. release.yml pins 1.26.X explicitly.
  2. Dependabot gomod ecosystem picks up the patch.

Source: security-reviewer.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P1Important, not blockingci/cdCI/CD pipelines and release

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions