[dependabot]

Bumps github.com/aws/aws-sdk-go-v2/config from 1.32.34 to 1.32.35.

Commits

• ebd1f6a Release 2026-08-05
• bc99825 Regenerated Clients
• 8868ff7 Update API model
• 9604fe3 Set FIPS-approved TLS curve preferences when the FIPS module is active (#3499)
• 4af61eb Release 2026-08-04
• 73d66ab Regenerated Clients
• e830452 Update API model
• 5d3779f Release 2026-08-03
• 27a73ff Regenerated Clients
• 8b197b7 Update API model
• Additional commits viewable in compare view

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	golang/​github.com/​aws/​aws-sdk-go-v2/​config@​v1.32.34 ⏵ v1.32.35

View full report

[cdalar]

The Vuln check is failing here, but it's not caused by this diff — govulncheck can't find the Go standard library on the self-hosted runner (onctl-4):

##[error]/opt/gocache/mod/golang.org/x/vuln@v1.6.0/cmd/govulncheck/main.go:8:2: package context is not in std (/opt/hostedtoolcache/go/1.26.5/x64/src/context)

This is a pre-existing runner/toolchain issue, not scoped to this PR — the same Vuln job has been failing the same way on unrelated PRs going back at least a week (e.g. runs on 08-03, 08-04, 08-06, 08-07) and on the scheduled main run on 2026-08-03. It also cancels the rest of the checks (Build, Lint, Test deployment, security, claude-review, dependabot-automerge) once it fails, so nothing else on this PR actually ran.

Nothing to fix in this dependency bump itself — the fix belongs on the onctl-4 runner's Go toolchain (or in .github/workflows/vuln.yml), outside this PR's scope. I'll re-check once the base pipeline recovers.

---

Generated by Claude Code

[cdalar]

Update after the branch was refreshed (new head e5b926d): Vuln still fails the same way (missing Go stdlib in /opt/hostedtoolcache/go/1.26.5/x64), and now Build (stable) is also failing — with a different, likely related runner problem:

go: github.com/cdalar/onctl: write /opt/gocache/go-build/.../...-a: no space left on device

The onctl-4 self-hosted runner is out of disk space. That's a separate, more urgent issue than the toolchain one above — it can affect any job that writes to /opt/gocache on that runner, not just this PR. security and claude-review did pass on this run, so it's not blocking everything, just anything that needs disk/build cache headroom.

Still nothing actionable in this dependency-bump diff — this needs disk cleanup (or cache eviction) on the runner itself.

---

Generated by Claude Code