Extension version is semver compliant and updated

Chrome Web Store requires the version field to use a dot-separated numeric format (e.g., 1.0.0). A version string prefixed with v or using fewer than three segments is rejected by the store validator. Beyond compliance, a version at 0.0.1 signals an untested pre-release to both reviewers and users, reducing install confidence even after approval. Proper semver also enables the store's update delivery mechanism — malformed versions cause update notifications to fail, leaving installed users on stale builds.

Set a proper three-segment numeric version in manifest.json. Never prefix with v.

{
  "version": "1.0.3"
}

Increment correctly: MAJOR for breaking changes, MINOR for new features, PATCH for bug fixes. If your extension is genuinely pre-release, use 0.x.x intentionally and note it in your store listing description. The Chrome Web Store rejects versions like 1.0, v1.0.0, or non-numeric segments.