[PATCH] manifest.json and package.json version fields should be bumped to 1.0.12 together

[ormidales]

Category: documentation
Severity: patch
File(s): manifest.json, package.json, package-lock.json

Description

The three version fields — manifest.json, package.json, and package-lock.json — must always be kept in sync for each release. As the next milestone is v1.0.12, all three files should be updated atomically. A mismatch between these files can confuse the AMO (addons.mozilla.org) submission pipeline and npm-based tooling.

Problematic code example

// manifest.json
{ "version": "1.0.11" }

// package.json
{ "version": "1.0.11" }

Suggested fix

Bump all three files to 1.0.12 in the same commit, ideally using npm version patch which updates package.json and package-lock.json automatically, followed by a manual update to manifest.json.

npm version patch   # updates package.json + package-lock.json to 1.0.12
# then manually set "version": "1.0.12" in manifest.json

Acceptance criteria

• manifest.json, package.json, and package-lock.json all carry version 1.0.12
• The version bump is in a single dedicated commit
• CI/tests pass after the bump