chrome-webstore-upload "version ... must be greater" in CI

By Daniel Zoghalchali·Latchkey

The Web Store requires each uploaded package to have a manifest version strictly greater than the version already in the store. Re-uploading the same or a lower version is rejected.

What this error means

The upload fails with an itemError noting the product version must be greater than the previously uploaded version.

{
  "uploadState": "FAILURE",
  "itemError": [
    { "error_detail": "The product version number ... 1.2.0 must be greater than the
       previously uploaded version in the store: 1.2.0." }
  ]
}

Common causes

The manifest version was not bumped

CI built the same version already published, so the store sees no increase and refuses the upload.

Version is lower than a previous draft

A higher version was uploaded earlier; a later build with a lower number is not allowed.

How to fix it

Bump the manifest version before upload

1. Set version in the manifest to a value above the published one.
2. Build the package with the new version.
3. Re-run the upload.

# derive version from the git tag and write it into the manifest
npm version --no-git-tag-version "${GITHUB_REF_NAME#v}"

Keep manifest version in sync with releases

Drive the manifest version from the release tag so every publish increments automatically.

"version": "1.2.1"

How to prevent it

• Bump the manifest version on every release.
• Derive the version from the release tag in CI.
• Only publish from tags so versions move monotonically.

Frequently asked questions

Related guides

References

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