Bump github.com/aws/aws-sdk-go-v2/service/s3 from 1.27.11 to 1.97.3

[dependabot]

Bumps github.com/aws/aws-sdk-go-v2/service/s3 from 1.27.11 to 1.97.3.

Commits

• 90650dd Release 2026-03-26
• dd88818 Regenerated Clients
• b662c50 Update endpoints model
• 500a9cb Update API model
• 6221102 fix stale skew and delayed skew healing (#3359)
• 0a39373 fix order of generated event header handlers (#3361)
• 098f389 Only generate resolveAccountID when it's required (#3360)
• 6ebab66 Release 2026-03-25
• b2ec3be Regenerated Clients
• abc126f 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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[greptile-apps]

Greptile Summary

This Dependabot PR bumps the AWS SDK Go v2 S3 package and its transitive dependencies from v1.27.11 to v1.97.3. All aws-sdk-go-v2 packages in this repo are indirect dependencies (no first-party code imports them directly); the repo's own S3 source driver uses the v1 SDK (github.com/aws/aws-sdk-go).

One notable inconsistency is that feature/s3/manager v1.11.33 and credentials v1.12.20 are left behind while the core SDK and service/s3 advance significantly — see the inline comment for details.

Confidence Score: 5/5

Safe to merge; all aws-sdk-go-v2 packages are indirect dependencies and the repo's own S3 driver uses the v1 SDK.

No first-party code imports aws-sdk-go-v2 directly, so the version mismatch between feature/s3/manager and service/s3 is a best-practice concern rather than a present defect. All remaining findings are P2.

go.mod — the feature/s3/manager and credentials packages should be co-updated with service/s3 for a coherent SDK version set.

Vulnerabilities

No security concerns identified. This is a routine dependency bump of indirect AWS SDK v2 packages; no auth logic, secrets handling, or input validation paths are modified.

Important Files Changed

Filename	Overview
go.mod	Core SDK bumped to v1.41.5 and service/s3 to v1.97.3; feature/s3/manager (v1.11.33) and credentials (v1.12.20) are not co-updated, creating a significant version skew within the aws-sdk-go-v2 ecosystem.
go.sum	Checksum file updated to match new dependency versions; retains old hashes for packages that weren't updated (expected for packages pinned at older versions).

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["golang-migrate/migrate<br/>(this repo)"] -->|direct, v1 SDK| B["aws/aws-sdk-go v1.49.6"]
    A -->|indirect| C["aws-sdk-go-v2 v1.41.5 ⬆️"]
    C --> D["service/s3 v1.97.3 ⬆️"]
    C --> E["feature/s3/manager v1.11.33 ⚠️ not updated"]
    C --> F["credentials v1.12.20 ⚠️ not updated"]
    C --> G["smithy-go v1.24.2 ⬆️"]
    D --> H["service/internal/s3shared v1.19.21 ⬆️"]
    D --> I["service/internal/checksum v1.9.13 ⬆️"]
    D --> J["service/internal/presigned-url v1.13.21 ⬆️"]

    style E fill:#fff3cd,stroke:#ffc107
    style F fill:#fff3cd,stroke:#ffc107

Loading

Prompt To Fix All With AI

This is a comment left during a code review.
Path: go.mod
Line: 103-104

Comment:
**Stale sibling packages not co-updated with `service/s3`**

`feature/s3/manager v1.11.33` and `credentials v1.12.20` are tightly coupled to the AWS SDK v2 release train but are left at versions that predate this bump. `feature/s3/manager` in particular wraps `service/s3` types directly; a ~70-minor-version gap (1.27 → 1.97) between the two raises the risk of subtle behavioral drift even if compilation succeeds under Go MVS. Consider running `go get github.com/aws/aws-sdk-go-v2/feature/s3/manager@latest github.com/aws/aws-sdk-go-v2/credentials@latest && go mod tidy` to bring all SDK v2 siblings to a coherent version set.

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (1): Last reviewed commit: "Bump github.com/aws/aws-sdk-go-v2/servic..." | Re-trigger Greptile}

[greptile-apps]

Stale sibling packages not co-updated with service/s3

feature/s3/manager v1.11.33 and credentials v1.12.20 are tightly coupled to the AWS SDK v2 release train but are left at versions that predate this bump. feature/s3/manager in particular wraps service/s3 types directly; a ~70-minor-version gap (1.27 → 1.97) between the two raises the risk of subtle behavioral drift even if compilation succeeds under Go MVS. Consider running go get github.com/aws/aws-sdk-go-v2/feature/s3/manager@latest github.com/aws/aws-sdk-go-v2/credentials@latest && go mod tidy to bring all SDK v2 siblings to a coherent version set.

Prompt To Fix With AI

This is a comment left during a code review.
Path: go.mod
Line: 103-104

Comment:
**Stale sibling packages not co-updated with `service/s3`**

`feature/s3/manager v1.11.33` and `credentials v1.12.20` are tightly coupled to the AWS SDK v2 release train but are left at versions that predate this bump. `feature/s3/manager` in particular wraps `service/s3` types directly; a ~70-minor-version gap (1.27 → 1.97) between the two raises the risk of subtle behavioral drift even if compilation succeeds under Go MVS. Consider running `go get github.com/aws/aws-sdk-go-v2/feature/s3/manager@latest github.com/aws/aws-sdk-go-v2/credentials@latest && go mod tidy` to bring all SDK v2 siblings to a coherent version set.

How can I resolve this? If you propose a fix, please make it concise.