Atlassian
Atlassian Forge Object Store rejects non-SHA256 upload checksums from December 10, 2026
21 days left — Dec 10, 2026
- What stops working
- The Forge Object Store upload APIs (createUploadUrl and createPublicUploadUrl in @forge/object-store, and GeneratedMetadata in the @forge/bridge objectStore API) accept only checksumType SHA256. From December 10, 2026 requests that use SHA1, CRC32 or CRC32C return HTTP 400 with error code CHECKSUM_TYPE_UNSUPPORTED. A future major version of the package removes the other checksum types.
- Who is affected
- Atlassian Marketplace vendors and in-house teams whose Forge apps upload files to the Forge Object Store with a non-SHA256 checksum.
- Official migration path
- Hash objects with SHA256, set checksumType to SHA256 wherever it is passed, and upgrade to the new @forge/object-store major version when released.
- What the official path does not cover
- Atlassian does not patch deployed app versions; each vendor must ship a new app version and get customers onto it before December 10 or production uploads fail.
- Source
- Forge changelog: Deprecation Notice, Forge Object Store: Deprecating checksumType in upload APIs (Nov 9, 2026) · announced 2026-11-09 · verified 2026-11-19
Need this done before Dec 10, 2026?
Fixed price, fixed scope, fixed date. From $2,500 for a single integration or workflow; you get the working replacement, the code, and a before/after check. Quote within one business day.
One short form (company, email, what runs on this, needed-by). Reply within one business day.
Not ready yet? Get an email when Atlassian deadlines approach · Firms: get listed for Atlassian work.
Spotted a wrong date? Report it — corrected with the source within one business day.