Update package.json

[code-crusher]

No description provided.

[matterai-app]

Summary By MatterAI

🔄 What Changed

Bumped the package version in package.json from 6.9.1 (implied) to 6.9.2.

🔍 Impact of the Change

Prepares the CLI tool for a new release iteration and publication to the package registry.

📁 Total Files Changed

Click to Expand

File	ChangeLog
Version Bump package.json	Updated project version string to 6.9.2 for release.

🧪 Test Added/Recommended

Recommended

• Verify build and tag creation pipeline in CI/CD.

🔒Security Vulnerabilities

• None detected.

[matterai-app]

🧪 PR Review is completed: Straightforward version bump to 6.9.2, but it desyncs the committed package-lock.json (still 6.9.1), which will hard-fail npm ci in the release workflow, and CHANGELOG.md has no [6.9.2] entry for the current [Unreleased] changes.

⬇️ Low Priority Suggestions (1)

package.json (1 suggestion)

Location: package.json (Lines 3-3)

🟠 Release Integrity

Issue: This bump updates package.json to 6.9.2 but leaves the committed package-lock.json at 6.9.1 (root version fields at lines 3 and 9). npm ci — which the release workflow runs per RELEASE.md — hard-fails on that mismatch (Invalid: lock file's @matterailab/orbcode@6.9.1 does not satisfy @matterailab/orbcode@6.9.2), so the v6.9.2 publish would break at the install step. Additionally, CHANGELOG.md has no [6.9.2] entry — the [Unreleased] section still holds the changes that would ship as this version.

Fix: Sync the lockfile in this PR — run npm install --package-lock-only (or bump via npm version patch --no-git-tag-version, which updates both files) and commit the package-lock.json change. Also promote CHANGELOG's [Unreleased] section to ## [6.9.2] - <release date>.

Impact: Release workflow's npm ci succeeds, package.json and lockfile stay in sync, and the changelog matches the shipped version.

-    "version": "6.9.2",
+