chrome-webstore-upload "ITEM_NOT_UPDATABLE" in CI

By Kaveh Alemi·Latchkey

The Chrome Web Store API returns ITEM_NOT_UPDATABLE when the listing cannot accept a new draft: it is pending review, in a takedown state, or otherwise locked. The upload is rejected until the item returns to an updatable state.

What this error means

The upload response status is FAILURE with an itemError code of "ITEM_NOT_UPDATABLE", and the CLI exits non-zero.

Upload failed
{
  "uploadState": "FAILURE",
  "itemError": [
    { "error_code": "ITEM_NOT_UPDATABLE",
      "error_detail": "Item cannot be updated now because it is in pending review state." }
  ]
}

Common causes

A previous submission is still in review

While an earlier version is pending review, the store will not accept another package upload for the same item.

The item is in a non-updatable lifecycle state

A taken-down, suspended, or disabled item cannot receive a new draft until its state changes.

How to fix it

Wait for review to finish, then re-upload

1. Check the item status in the Developer Dashboard.
2. Wait until the prior submission clears review or is published.
3. Re-run the upload once the item is updatable again.

Avoid overlapping submissions in CI

Gate publish so two pipeline runs do not upload to the same item while one is still in review.

# run upload only on tagged releases, not every push
if: startsWith(github.ref, 'refs/tags/')

How to prevent it

• Publish from tagged releases, not every commit.
• Serialize uploads so submissions do not overlap a review.
• Check item status before attempting an upload.

Frequently asked questions

Related guides

References

• Node.js documentation
• npm CLI documentation
• GitHub Actions documentation