# SDK upgrade changes behaviour: pre-release checklist

Source: https://releasefailures.com/incidents/sdk-upgrade-changes-behaviour/
Content version: 1.0.0
Verified on: 2026-10-21
Licence: CC BY 4.0

Definition: An SDK upgrade changes defaults such as consent, tracking or retry behaviour.
- [ ] 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. (test class: Integration tests)
- [ ] PR-02 When the lockfile changes the storage SDK module version, rerun the cache download and backup upload tests against each supported custom endpoint before release. (test class: Integration tests)
- [ ] PR-03 Confirm the client sets RequestChecksumCalculation and ResponseChecksumValidation to WhenRequired for custom non-vendor endpoints, and run one GetObject test against such an endpoint. (test class: Integration tests)
- [ ] PR-04 Record 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. (test class: Contract tests)
- [ ] PR-05 Keep a contract per supported third-party provider that lists the checksum headers it accepts, and check the client's recorded requests against it. (test class: Contract tests)
- [ ] PR-06 On 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. (test class: Synthetic monitoring)