Repository navigation
chore(deps): bump cloud-commitments-go to pick up go #451, #455 and #456 #1051
Description
Problem
go.mod pins the four cloud-commitments-go modules at 551be568 (go#428). That pin predates go #451, #455 and #456, which are on go main. As a result platform still lacks the returned-offering verification from those PRs, and an empty platform still defaults to Linux/UNIX at the pin (ec2/client.go:953-960 in the go module).
Raised as a non-blocking note in the independent review of #1018 (merged as 07439f5).
Expected
Bump all four cloud-commitments-go modules to current go main (56785bfe or later), run go build ./... and make test-unit, and adapt any call sites that changed.
Activity
IAmJSD commentedon Oct 20, 2026
Claiming: working on this
IAmJSD commentedon Oct 20, 2026
Closing as already fixed on main.
551be568to3def3f89and adaptedhandler_ri_exchange.goand the test fakes for the new offering verification. It said "Refs feat(insurance): per-recommendation Archera quotes (blocked on an Archera API mapping) #799", so this issue wasn't auto-closed.pkgto541e05e5andproviders/awstoaeb8a6f7.The merge commits of go #451 (60a8c70d), #455 (bc8905f4) and #456 (56785bfe) are all ancestors of the current
providers/awspin (checked withgit merge-base --is-ancestor), and those three PRs only touchproviders/aws.FYI for #521: go main is ahead of the platform pins again, by 11 commits in providers/aws, 13 in pkg and 31 in azure/gcp. It adds exported errors such as
ErrNotUSDandErrUnsupportedPartition(go #566). @cristim