SDK upgrade changes behaviour: pre-release and first 30 minutes checklists

An SDK upgrade changes defaults such as consent, tracking or retry behaviour.

The pre-release checklist maps each item to a test class from the incident page. The first-30-minutes checklist covers detection, containment, the rollback decision and customer communication.

6 pre-release items · 7 first-30-minutes items · verified 2026-10-21

Pre-release checklist

PR-01Run the object storage integration suite against every third-party compatible provider the product supports as a custom endpoint, not only against the SDK vendor's own service. integration
PR-02When the lockfile changes the storage SDK module version, rerun the cache download and backup upload tests against each supported custom endpoint before release. integration
PR-03Confirm the client sets RequestChecksumCalculation and ResponseChecksumValidation to WhenRequired for custom non-vendor endpoints, and run one GetObject test against such an endpoint. integration
PR-04Record the signed headers each storage request sends in a contract, and fail the build when a new header such as x-amz-checksum-mode appears. contract
PR-05Keep a contract per supported third-party provider that lists the checksum headers it accepts, and check the client's recorded requests against it. contract
PR-06On the storage provider side, run a scheduled probe that uses the newest SDK release of each supported language with default configuration and alerts on any checksum header error. synthetic

First 30 minutes

FM-01Check whether the failing clients picked up a new storage SDK version, and read that version's changelog for changed checksum defaults.
FM-02Search request logs for SignatureDoesNotMatch, status 400 or unsupported header errors that name x-amz-checksum headers.
FM-03Split failures by storage endpoint to confirm that only third-party compatible providers fail.
FM-04Decide between pinning the SDK to the prior version and setting both checksum options back to WhenRequired for custom endpoints.
FM-05Publish the environment variable or client setting that restores the prior checksum behaviour, so users can unblock themselves before a fix ships.
FM-06Post a status update that names the affected SDK versions and the affected storage providers.
FM-07Rerun the cache downloads and backup jobs that failed during the incident window once the fix is in place.

Download the checklist

Pre-release checklist (Markdown)1.5 KB · v1.0.0
First 30 minutes checklist (Markdown)1.2 KB · v1.0.0

Only in this checklist

Every test class in this checklist also appears in at least one sibling checklist in the group; the item texts differ: Run the object storage integration suite against every third-party compatible provider the product supports as a custom endpoint, not only against the SDK vendor's own service.

Questions

What should be checked before a release to prevent SDK upgrade changes behaviour?

6 pre-release items, PR-01 to PR-06. PR-01: Run the object storage integration suite against every third-party compatible provider the product supports as a custom endpoint, not only against the SDK vendor's own service.

Is there a rollback plan for SDK upgrade changes behaviour?

The first-30-minutes checklist has 7 items. FM-01: Check whether the failing clients picked up a new storage SDK version, and read that version's changelog for changed checksum defaults.

What should a team do in the first 30 minutes after SDK upgrade changes behaviour is detected?

The first-30-minutes checklist has 7 items. FM-01: Check whether the failing clients picked up a new storage SDK version, and read that version's changelog for changed checksum defaults.

Is a SDK upgrade changes behaviour checklist still needed if deployment is automated?

Yes. Automation runs the steps; the checklist names what the tests must cover: integration tests, contract tests and synthetic monitoring.

Which pipeline stages does the SDK upgrade changes behaviour checklist cover?

The pre-release items map to the pre-deploy, pre-merge and post-deploy stages.

In what formats can the SDK upgrade changes behaviour checklist be downloaded?

Both checklists download as Markdown files: /downloads/sdk-upgrade-changes-behaviour-pre-release.md and /downloads/sdk-upgrade-changes-behaviour-first-30-minutes.md, licensed CC BY 4.0.