chore(deps): bump the go-dependencies group with 6 updates

[dependabot]

Bumps the go-dependencies group with 6 updates:

Package	From	To
github.com/aws/aws-sdk-go-v2/config	1.32.25	1.32.26
github.com/aws/aws-sdk-go-v2/credentials	1.19.24	1.19.25
github.com/aws/aws-sdk-go-v2/feature/s3/transfermanager	0.2.11	0.2.12
github.com/aws/aws-sdk-go-v2/service/ecs	1.85.0	1.86.0
github.com/aws/aws-sdk-go-v2/service/lambda	1.93.0	1.94.0
github.com/aws/aws-sdk-go-v2/service/s3	1.104.0	1.104.1

Updates github.com/aws/aws-sdk-go-v2/config from 1.32.25 to 1.32.26

Commits

• 26060c5 Release 2026-06-29
• 24e918a Regenerated Clients
• 334471f Update API model
• 96d81dc Deprecate iotevents, ioteventsdata, panorama and simspaceweaver (#3458)
• 30502cb feat: mark common plugins and fix per-op ordering for invokeOperation refacto...
• 8881653 Revert "feat: mark common plugins and fix per-op ordering for invokeOperation...
• eba2f01 feat: mark common plugins and fix per-op ordering for invokeOperation… (#3443)
• 2c5e1db Release 2026-06-23
• d09eeb5 Regenerated Clients
• 2f5f5f9 Update API model
• Additional commits viewable in compare view

Updates github.com/aws/aws-sdk-go-v2/credentials from 1.19.24 to 1.19.25

Commits

• 26060c5 Release 2026-06-29
• 24e918a Regenerated Clients
• 334471f Update API model
• 96d81dc Deprecate iotevents, ioteventsdata, panorama and simspaceweaver (#3458)
• 30502cb feat: mark common plugins and fix per-op ordering for invokeOperation refacto...
• 8881653 Revert "feat: mark common plugins and fix per-op ordering for invokeOperation...
• eba2f01 feat: mark common plugins and fix per-op ordering for invokeOperation… (#3443)
• 2c5e1db Release 2026-06-23
• d09eeb5 Regenerated Clients
• 2f5f5f9 Update API model
• Additional commits viewable in compare view

Updates github.com/aws/aws-sdk-go-v2/feature/s3/transfermanager from 0.2.11 to 0.2.12

Commits

• 26060c5 Release 2026-06-29
• 24e918a Regenerated Clients
• 334471f Update API model
• 96d81dc Deprecate iotevents, ioteventsdata, panorama and simspaceweaver (#3458)
• 30502cb feat: mark common plugins and fix per-op ordering for invokeOperation refacto...
• 8881653 Revert "feat: mark common plugins and fix per-op ordering for invokeOperation...
• eba2f01 feat: mark common plugins and fix per-op ordering for invokeOperation… (#3443)
• 2c5e1db Release 2026-06-23
• d09eeb5 Regenerated Clients
• 2f5f5f9 Update API model
• Additional commits viewable in compare view

Updates github.com/aws/aws-sdk-go-v2/service/ecs from 1.85.0 to 1.86.0

Commits

• 711cf64 Release 2025-08-04
• 699889e Regenerated Clients
• 5a94577 Update endpoints model
• 240e984 Update API model
• 2e08461 support configurable auth scheme preference (#3153)
• 5462033 Release 2025-08-01
• a84b1c6 Regenerated Clients
• 3325d43 Update endpoints model
• 2ddc428 Update API model
• eb0a91b Release 2025-07-31
• Additional commits viewable in compare view

Updates github.com/aws/aws-sdk-go-v2/service/lambda from 1.93.0 to 1.94.0

Commits

• 3297582 Release 2025-12-15
• 682a1b6 Regenerated Clients
• f2a67b1 Update API model
• fbe0776 Release 2025-12-12
• 91070ff Regenerated Clients
• 67f5776 Update endpoints model
• a154798 Update API model
• 76d0a55 Release 2025-12-11
• 72bae88 Regenerated Clients
• 9b57b96 Update endpoints model
• Additional commits viewable in compare view

Updates github.com/aws/aws-sdk-go-v2/service/s3 from 1.104.0 to 1.104.1

Commits

• 26060c5 Release 2026-06-29
• 24e918a Regenerated Clients
• 334471f Update API model
• 96d81dc Deprecate iotevents, ioteventsdata, panorama and simspaceweaver (#3458)
• 30502cb feat: mark common plugins and fix per-op ordering for invokeOperation refacto...
• 8881653 Revert "feat: mark common plugins and fix per-op ordering for invokeOperation...
• eba2f01 feat: mark common plugins and fix per-op ordering for invokeOperation… (#3443)
• 2c5e1db Release 2026-06-23
• d09eeb5 Regenerated Clients
• 2f5f5f9 Update API model
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[claude]

Claude finished @dependabot[bot]'s task in 1m 3s —— View job

---

Dependency Update Review

• Identify changed dependencies
• Assess semver / breaking-change risk
• Check repo usage of upgraded SDKs
• Verify build compiles (could not run — see note)
• Post findings

Summary

This is a routine Dependabot bump of 6 AWS SDK for Go v2 modules, all staying within the same major version. AWS SDK v2 follows semver, and these are regenerated-client releases (new/updated API models) — additive and backward-compatible by design.

Module	From → To	Bump	Risk
config	1.32.25 → 1.32.26	patch	none
credentials	1.19.24 → 1.19.25	patch	none
feature/s3/transfermanager	0.2.11 → 0.2.12	patch (pre-1.0)	low
service/ecs	1.85.0 → 1.86.0	minor	low (additive)
service/lambda	1.93.0 → 1.94.0	minor	low (additive)
service/s3	1.104.0 → 1.104.1	patch	none

Plus transitive bumps (s3shared, signin, sso, ssooidc, sts) — all patch-level.

Usage in this repo

All AWS SDK usage lives in internal/aws/aws.go (exercised by tests in internal/aws/ and cmd/kosli/snapshotLambda_test.go). The APIs touched are long-stable core operations:

• config / credentials — config.LoadDefaultConfig, config.WithRegion, config.WithCredentialsProvider, config.WithRetryer, credentials.NewStaticCredentialsProvider, retry.NewAdaptiveMode (aws.go:87-123). Unchanged signatures.
• ecs — ListClusters/DescribeClusters, ListServices/DescribeServices, ListTasks/DescribeTasks (aws.go:528-785). The minor bump only adds new model fields; existing input/output structs and the ECSServicesAPI interface are unaffected.
• lambda — ListFunctions, GetFunctionConfiguration (aws.go:143-301). Reads FunctionName, LastModified, CodeSha256, PackageType — all stable.
• s3 + transfermanager — ListObjectsV2Paginator, transfermanager.New/DownloadObject with WriterAt (aws.go:442-526). transfermanager is pre-1.0 (v0.x), so technically the only module where a minor could carry breaking changes, but this is a 0.2.11 → 0.2.12 patch and the DownloadObjectInput{Bucket, Key, WriterAt} shape is unchanged.

Risks / breaking changes

None identified. No removed APIs, no signature changes, no new required fields on the operations this codebase calls. New defaults in regenerated clients (e.g. auth-scheme/endpoint-resolution refactors mentioned in the changelogs) don't affect the static-credentials + explicit-region path used here.

Suggested follow-up

• ⚠️ I could not run go build ./... / go vet or the integration tests — the build commands were blocked by the sandbox in this environment. Please rely on CI to confirm compilation and that internal/aws tests pass before merging.
• The transfermanager module is still v0.x (pre-stable). Worth keeping an eye on it specifically across future bumps, since its API isn't yet under the semver stability guarantee.

Recommendation: Low-risk, safe to merge once CI is green.