Skip to content

Monthly update: Go 1.27.0, module dependencies, tool pins, and Amazon Linux 2023 base image - #64

Merged
nickpell merged 6 commits into
mainfrom
cursor/dependencies-toolchain-base-image-e85e
Sep 8, 2026
Merged

nickpell merged 6 commits into
mainfrom
cursor/dependencies-toolchain-base-image-e85e

Conversation

@cursor

@cursor cursor Bot commented Sep 7, 2026 •

Copy link
Copy Markdown
Contributor

Monthly refresh of the Go module dependencies, the Go toolchain and the tool pins that move with it, and the pinned Amazon Linux 2023 enclave base image. Every verification named below was run locally against the updated tree.

The most consequential part of this update is the toolchain. govulncheck against the pre-change tree reports a reachable standard-library vulnerability, GO-2026-5972 / CVE-2026-33818, a missing recursion limit in encoding/asn1 that allows stack exhaustion on deeply nested input. It is reachable here, not merely present: the reported trace is validation.VerifyCOSESignature calling x509.ParseCertificate, which reaches asn1.Unmarshal, so it sits directly in the attestation certificate parsing path. It is fixed in go1.26.6 and in go1.27.0. The same scan lists seven further standard-library advisories fixed in go1.26.6 that this code does not call. After the update govulncheck reports no vulnerabilities.

Go module dependencies

  • github.com/fxamacker/cbor/v2 from v2.9.2 to v2.9.3.
  • github.com/stretchr/testify from v1.11.1 to v1.12.1. testify v1.12 absorbs its former go-spew and go-difflib dependencies and moves from gopkg.in/yaml.v3 to go.yaml.in/yaml/v3, so those three modules drop out of go.sum. No package in this repository imports testify, so go get -u -t ./... does not reach it and it was bumped explicitly.
  • github.com/mdlayher/socket is held at v0.6.1. v0.7.0 was published on 2026-09-06, the day before this run, and is below the minimum release age applied to versions this job resolves.
  • No direct dependency publishes a v2 or higher major, so no major-version migration was deferred.

Go toolchain 1.26.5 to 1.27.0

Every pin that names a Go version moves together:

  • go.mod: the go directive becomes 1.27, preserving its existing two-component precision.
  • .mise/config.toml and .mise/mise.lock: the go tool version plus all five platform archive URLs and sha256 checksums, read from https://go.dev/dl/?mode=json.
  • .github/workflows/docker.yml: the actions/setup-go go-version input. This job compiles the enclave binary that is packaged into the released image, so leaving it behind would ship an artifact built with a different Go than CI tests against.

golangci-lint 2.12.2 to 2.13.2

This is forced by the toolchain bump rather than chosen. golangci-lint refuses to start when the Go release it was built with is older than the language version the module targets, and 2.12.2 is built with go1.26.2, so against a go 1.27 module it fails with can't load config: the Go language version (go1.26) used to build golangci-lint is lower than the targeted Go version (1.27). 2.13.0 added go1.27 support and 2.13.2 is built with go1.27.0.

.golangci.yml needs no migration. 2.13.0 deprecates exhaustruct in favour of exhaustruct_v5 and renames the govet-modernize waitgroup analyzer to waitgroupgo, but this configuration enables neither. golangci-lint run reports no issues against the updated tree.

ratchet 0.11.4 to 0.12.0

0.12.0 fixes an index-out-of-range failure, hardens YAML parsing, adds support for parallel step blocks in workflows, accepts non-semver tags, and skips container refs containing CI variables. ratchet is installed from source through the mise go backend, so the lock records only a version.

ORAS 1.1.0 to 1.3.4

VERSION and SHA256 in the Install ORAS step of .github/workflows/eif-build.yml move together, with the checksum copied from the oras_1.3.4_linux_amd64.tar.gz line of that release's oras_1.3.4_checksums.txt. The step stays linux_amd64 because ORAS runs on the GitHub runner to push the built EIF, not inside the enclave.

This is a long jump, so the breaking changes were checked against actual usage. The workflow uses oras version, login, push and tag. The breaking changes in 1.2.0 and 1.3.0 apply to attach, discover and cp, none of which appear here.

Amazon Linux 2023 base image

The amazonlinux:2023 pin in enclave/Dockerfile moves to the current multi-architecture index digest, sha256:181f98c4...ce284, resolved with docker buildx imagetools inspect rather than copied by hand. The registry, repository and 2023 tag are unchanged, so this stays on the same major. The index is an OCI image index and contains both linux/amd64 and linux/arm64, the two platforms this repository builds.

The base moves from Amazon Linux 2023.12.20260727 to 2023.12.20260817, an update to the twelfth quarterly release. Comparing the two images directly shows the same 106 packages with none added or removed: openssl-libs and openssl-fips-provider-latest go from 3.5.5 to 3.5.7, alongside crypto-policies, gawk, glib2, libxml2, python3 and rpm. The OpenSSL step spans the 3.5.6 and 3.5.7 advisory batches, twenty-two CVEs of which one is rated High and five Moderate. Worth noting for scale: the enclave binary is built with CGO_ENABLED=0 and is statically linked with no reference to libssl or libcrypto, so it does not use the image's OpenSSL, and the Dockerfile already runs dnf update -y at build time. The digest pin governs the reproducibility of the starting layer more than it governs package currency.

Risk assessment

Go 1.27 is a language release rather than a patch, so its behavioural changes carry most of the risk here:

  • encoding/json is now backed by the new v2 implementation. Marshal and unmarshal behaviour is preserved but error message text may differ. This repository uses encoding/json in the enclave server, auction and proof paths, in enclaveapi, and in the validation commands. The full suite passes, including under -race. GOEXPERIMENT=nojsonv2 is the upstream opt-out if a problem surfaces later.
  • compress/flate changed its encoder, and that reaches compress/gzip. enclaveapi.AttestationCOSE.CompressGzip gzips COSE attestation bytes for URL-safe transport, so the compressed bytes may differ from a Go 1.26 build. Nothing depends on that: the determinism test asserts only that two calls in the same process agree rather than comparing against a stored value, and validation decompresses before verifying the COSE signature, so a different DEFLATE encoding is transparent to the receiver.
  • Size-specialized allocation routines are new and on by default. The statically linked enclave binary grows accordingly: arm64 from 5,753,898 to 6,645,213 bytes and amd64 from 6,173,649 to 7,176,381 bytes.
  • For go 1.27 modules go mod tidy now consolidates require blocks. go.mod already had exactly the two blocks it wants, so it is otherwise unchanged.

The remaining bumps are low risk. The two module updates are patch and minor releases whose only visible effect is the go.sum reshuffle described above, and the ratchet and ORAS bumps were exercised against this repository's own inputs rather than assessed from release notes alone.

Enclave measurements

Rebuilding the enclave image moves PCR0 and PCR2, which is routine for any change reaching the enclave image; here both the Go rebuild and the base image refresh reach it. After merge the update-pcrs job in .github/workflows/eif-build.yml appends the new set to validation/pcrs.json. That file is append-only and ValidatePCRs accepts a match against any recorded set, so previously built enclaves keep validating. No consumer of validation/pcrs.json outside this repository's own validation package is visible from this repository.

Upstream release age

Versions this job resolved were held to a minimum release age of seven days, judged from upstream publication timestamps. Two candidates were rejected. Go 1.27.1 and Go 1.26.8 were both published on 2026-09-01, six days before this run; the release notes describe both as bug-fix only with no security content, so the floor was not overridden and Go 1.27.0, published 2026-08-19, is the newest qualifying release. github.com/mdlayher/socket v0.7.0 was published on 2026-09-06 and is held as described above. golangci-lint 2.13.2 (2026-08-27), ratchet 0.12.0 (2026-07-18), ORAS 1.3.4 (2026-08-27) and the Amazon Linux image (pushed 2026-08-20) all qualify. .mise/config.toml already sets its own floor for mise-managed tools and is unchanged.

Pre-merge checklist

  • go build ./..., go vet ./..., go test ./... and go test -count=1 -race ./... all pass under Go 1.27.0. — CI test (mise run //:test under the mise.lock Go 1.27.0) passed on 709fd56: https://github.com/cloudx-io/openauction/actions/runs/34106036212/job/101691142033; -race and go vet are the author's local run, not exercised by PR CI.
  • golangci-lint run reports no issues with 2.13.2, and .golangci.yml needs no changes. — CI lint (mise run //:lint, golangci-lint 2.13.2 from mise.lock) passed on 709fd56: https://github.com/cloudx-io/openauction/actions/runs/34106036212/job/101691142334.
  • go mod tidy leaves go.mod and go.sum unchanged, which is what the //:tidy check enforces. — same lint job runs mise run //:tidy (git diff --exit-code go.mod go.sum); passed on 709fd56.
  • ratchet lint passes and ratchet pin leaves no diff under 0.12.0, which is what the Ratchet workflow enforces. — CI Ratchet Lint passed on 709fd56: https://github.com/cloudx-io/openauction/actions/runs/34106036691/job/101691143311; ratchet v0.12.0 exists on proxy.golang.org (tag v0.12.0, 9ca11815, 2026-07-18).
  • The enclave binary cross-compiles for linux/arm64 and linux/amd64 using the exact command from .github/workflows/docker.yml. PR CI runs only the Go and Ratchet workflows, so this is the only pre-merge coverage of the artifact that actually ships. — author's local run; not independently reproduced. First CI exercise is the post-merge Docker Build (workflow_run on Go).
  • enclave/Dockerfile builds for linux/arm64 and linux/amd64 against the new base digest with those cross-compiled binaries, so the dnf update and install layers were exercised on both architectures rather than only resolving the FROM. — build is the author's local run; the digest was independently confirmed: sha256:181f98c4…ce284 is the current library/amazonlinux:2023 index on Docker Hub (pushed 2026-08-20T19:30Z), an OCI image index with linux/amd64 + linux/arm64/v8 manifests, source revision amazonlinux/container-images@bdaec0a0 = "Add 2023.12.20260817.0 x86_64 image"; the outgoing 694092ae… resolves to revision 0c02d87a = 2023.12.20260727.0, matching the stated from/to.
  • Every Go and golangci-lint checksum written into .mise/mise.lock was verified by downloading the archive and comparing digests, not just transcribed. — independently re-checked: all 5 go1.27.0.* sha256 values match https://go.dev/dl/?mode=json and all 5 golangci-lint-2.13.2-* values match the release's golangci-lint-2.13.2-checksums.txt (v2.13.2 published 2026-08-27).
  • The pinned ORAS tarball downloads and matches its checksum, and the push and tag invocation shapes this workflow uses behave the same on 1.3.4. — f27adb93…c454 matches the oras_1.3.4_linux_amd64.tar.gz line of upstream oras_1.3.4_checksums.txt (release v1.3.4, 2026-08-27, not prerelease); the push/tag behaviour claim is the author's local run and is first exercised by the post-merge Build EIF.
  • govulncheck reports no known vulnerabilities against the updated tree. — author's local run; the vuln DB record for GO-2026-5972 (CVE-2026-33818, encoding/asn1) lists fixes at 1.25.13 / 1.26.6 / 1.27.0-rc.3, so 1.27.0 carries the fix.
  • Reviewer confirms the Go 1.27 encoding/json v2 switch is acceptable for the enclave request, proof and validation paths. — accepted by nickpell at the merge gate (merge requested 2026-09-08, squash f6cbe73).

Post-merge verification

Post-merge outcome (2026-09-08). Go, Docker Build (34249459364) and Build EIF (34249776263) all succeeded on f6cbe73. Install ORAS verified oras_1.3.4_linux_amd64.tar.gz: OK and reported Version: 1.3.4; oras push published enclave-eif:f6cbe73b… and oras tag applied f6cbe73-arm64. The EIF built on the refreshed base with PCR0 f5a297a8…938e7dd; update-pcrs committed dd5bd21 (validation/pcrs.json +7/−0, earlier entries intact).

  • Merging triggers Go, then Docker Build, then Build EIF, which publish the enclave image and EIF artifacts. That is artifact publication; no deployed version pin is changed by this PR.
  • Confirm the update-pcrs job appends a new PCR set to validation/pcrs.json in its [skip-build] commit and leaves the earlier entries intact.
  • Confirm the Install ORAS step and the subsequent oras push and oras tag succeed on the runner, since that first post-merge EIF build is the first CI run to exercise the 1.3.4 pin.
  • Confirm the EIF build succeeds against the refreshed base layer, and record the resulting PCR0 and PCR2 as the current expected measurements.
Open in Web View Automation 

Bump github.com/fxamacker/cbor/v2 from v2.9.2 to v2.9.3 and
github.com/stretchr/testify from v1.11.1 to v1.12.1.

testify v1.12 absorbs its former go-spew and go-difflib dependencies and
moves from gopkg.in/yaml.v3 to go.yaml.in/yaml/v3, so those three modules
drop out of go.sum. testify is a graph-only module here: no package in
this repository imports it, so it is bumped explicitly rather than by
go get -u.

github.com/mdlayher/socket is held at v0.6.1. v0.7.0 was published on
2026-09-06 and is below the minimum release age this update applies to
newly resolved versions.

The go directive moves from 1.26 to 1.26.0 as a side effect of go get -u;
the following commit sets it to the new toolchain version.
Bump every pin that names a Go version, keeping them in sync:

- go.mod: the go directive moves to 1.27, restoring the two-component
  precision go get -u had expanded to 1.26.0.
- .mise/config.toml and .mise/mise.lock: go 1.26.5 -> 1.27.0, with
  per-platform archive URLs and sha256 checksums taken from
  https://go.dev/dl/?mode=json. All five archives were downloaded and
  checked against the recorded digests.
- .github/workflows/docker.yml: the actions/setup-go go-version input,
  which compiles the enclave binary packaged into the released image.
  Leaving it behind would ship an artifact built with a different Go
  than CI tests against.

Go 1.27.1 and 1.26.8 were both published on 2026-09-01 and are below the
minimum release age this update applies; neither carries security fixes,
so 1.27.0 (2026-08-19) is the newest qualifying release.
golangci-lint refuses to run when the Go release it was built with is
older than the language version the module targets, so the move to Go
1.27 requires a linter that understands it:

  can't load config: the Go language version (go1.26) used to build
  golangci-lint is lower than the targeted Go version (1.27)

2.13.0 added go1.27 support; 2.13.2 is built with go1.27.0. Checksums
come from the release's golangci-lint-2.13.2-checksums.txt and every
archive was downloaded and checked against the recorded digest.

.golangci.yml needs no migration. 2.13.0 deprecates exhaustruct in
favour of exhaustruct_v5 and renames the govet-modernize waitgroup
analyzer, but this configuration enables neither. golangci-lint run
reports no issues against the updated tree.
ratchet is installed from source through the mise go backend, so the
lock records only the version. 0.12.0 fixes an index-out-of-range
failure, hardens YAML parsing, adds support for parallel step blocks in
workflows, accepts non-semver tags, and skips container refs containing
CI variables.

Verified against this repository with 0.12.0 built by Go 1.27.0:
ratchet lint passes on all four workflow files, and ratchet pin leaves
no diff, which is what the Ratchet workflow checks.
VERSION and SHA256 move together. The checksum is the
oras_1.3.4_linux_amd64.tar.gz line from the release's
oras_1.3.4_checksums.txt. The step stays linux_amd64: ORAS runs on the
GitHub runner to push the built EIF, not inside the enclave.

This workflow uses oras version, login, push and tag. The breaking
changes across 1.2.0 and 1.3.0 apply to attach, discover and cp, which
are not used here. Verified with 1.3.4 locally: the same push
invocation shape (--artifact-type, repeated --annotation, and two
file:mediatype arguments) and oras tag both behave as before, and the
non-interactive output stays plain when no TTY is attached.
Move the amazonlinux:2023 pin to the current multi-architecture index
digest, resolved with docker buildx imagetools inspect. The registry,
repository and 2023 tag are unchanged, so this stays on the same major.

The index is an OCI image index carrying both linux/amd64 and
linux/arm64, the two platforms this repository builds. The base moves
from Amazon Linux 2023.12.20260727 to 2023.12.20260817: the same 106
packages with none added or removed, updating openssl-libs and
openssl-fips-provider-latest from 3.5.5 to 3.5.7 along with
crypto-policies, gawk, glib2, libxml2, python3 and rpm.

Verified by building enclave/Dockerfile for linux/arm64 and linux/amd64
against the new digest with the locally cross-compiled binary, so the
dnf update and install layers were exercised on both architectures.
@nickpell
nickpell marked this pull request as ready for review September 8, 2026 13:31
@nickpell
nickpell self-requested a review as a code owner September 8, 2026 13:31
@nickpell
nickpell requested a balanced review from Copilot September 8, 2026 13:32

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔵 Needs a closer look

The major Go runtime change affects security-sensitive enclave serialization and artifact generation, warranting the requested human compatibility review.

Pull request overview

Refreshes the Go toolchain, dependencies, build tools, and enclave base image to address vulnerabilities and maintain current build infrastructure.

Changes:

  • Upgrades Go to 1.27.0 and refreshes module dependencies.
  • Updates golangci-lint, ratchet, and ORAS pins.
  • Refreshes the Amazon Linux 2023 enclave image digest.
File summaries
File Description
go.mod Updates Go and module versions.
go.sum Refreshes dependency checksums.
.mise/config.toml Updates local tool versions.
.mise/mise.lock Pins updated tool archives and checksums.
.github/workflows/docker.yml Builds release artifacts with Go 1.27.0.
.github/workflows/eif-build.yml Upgrades the ORAS installation.
enclave/Dockerfile Pins the refreshed Amazon Linux image.
Review details
  • Files reviewed: 5/7 changed files
  • Comments generated: 0
  • Review effort level: Balanced

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@nickpell
nickpell merged commit f6cbe73 into main Sep 8, 2026
4 checks passed
@nickpell
nickpell deleted the cursor/dependencies-toolchain-base-image-e85e branch September 8, 2026 16:09
nickpell added a commit that referenced this pull request Oct 26, 2026
## Summary

- Docker Build installs Go with `actions/setup-go` from
`go-version-file: go.mod` instead of a `go-version: "1.27.3"` literal,
so no workflow names a Go version. The `docker-build` PR check in
`go.yml` uses the same step, in place of mise, so the published image's
install step runs on every PR.
- `go.mod` gains `toolchain go1.27.3`, which setup-go reads ahead of the
`go` line. The `go` directive stays `1.27`: it is the minimum for every
module that imports this one, and the `toolchain` line of a dependency
is ignored, so importers are not held to the patch release.
- `.mise/config.toml`'s `go` pin is still the version tests and lint run
on. A new `check-go-version` task, run in the `lint` job, fails when
`go.mod`'s toolchain line or `.mise/mise.lock` disagrees with it. A Go
bump is: edit the pin, `MISE_LOCKED=0 mise lock go`, `go mod edit
-toolchain=go<version>`.
- The Go version does not change: 1.27.3 before and after.
- cloudx-io/openarbiter#64 makes the same change in openarbiter.

## Notes for reviewers

- #39 moved `go.yml` to mise and left `docker.yml`
on setup-go with pin-only changes; no reason to keep that split is
recorded. Since then each Go bump has edited `docker.yml`'s `go-version`
by hand next to the mise pin (#64,
#102, #117).
- Docker Build runs only from `workflow_run` on `main` or a manual
dispatch, and `workflow_run` uses the definition on `main`, so this PR
cannot run the changed `docker.yml`. The `docker-build` job runs the
identical setup-go step followed by the same `go build`.

## Pre-merge checklist

- [x] `mise run //:check-go-version` passes, and fails naming the file
when `go.mod` says `toolchain go1.27.2` or the pin says 1.27.4 with the
lock and `go.mod` left at 1.27.3
- [x] `mise run //:lint`, `//:test`, `//:tidy` (keeps the `toolchain`
line) and `//:ratchet:lint` pass locally on Go 1.27.3; actionlint
reports nothing
- [x] PR CI green on c6a1a24 (test, lint, docker-build, Ratchet Lint);
`docker-build`'s setup-go step logs `Setup go version spec 1.27.3` and
`go version go1.27.3`, and `lint` runs `check-go-version`
- [x] Diff contains no unintended changes: `docker.yml`, `go.yml`,
`go.mod` and the new task

## Post-merge verification

- [ ] On the merge commit the main pipeline is green: Go, then Docker
Build, then Build EIF, then the `[skip-build] Update PCR measurements`
commit
- [ ] Docker Build's setup-go step logs `Setup go version spec 1.27.3`

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants