fix: align Composer release metadata

[superdav42]

Summary

• align the root Composer package version with the 2.15.1 plugin release
• refresh the committed lockfile content hash without changing dependencies

Context

Follow-up to #1732. The expanded release audit found that composer.json still reported 2.5.0 after the 2.15.1 release preparation merged.

Files changed:

• composer.json
• composer.lock

Verification

• composer validate --no-check-publish --no-interaction
• git diff --check origin/main..HEAD
• expanded release audit: 59/59 plugin runtime versions aligned and zero Composer version advisories

---

aidevops.sh v3.32.278 plugin for OpenCode v1.18.18 with gpt-5.6-sol spent 1d 13h and 3,045,628 tokens on this with the user in an interactive session.

Summary by CodeRabbit

• Chores
  • Updated the Composer package to version 2.15.1.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: dcddee53-f6b3-4e2f-a1ca-484adf7908c5

📥 Commits

Reviewing files that changed from the base of the PR and between 4c4020b and 45cbe01.

⛔ Files ignored due to path filters (1)

• composer.lock is excluded by !**/*.lock

📒 Files selected for processing (1)

• composer.json

Included review availability: Your plan provides up to 2 included reviews per hour; 1 remains after this review.

---

📝 Walkthrough

Walkthrough

The Composer package version changes from 2.5.0 to 2.15.1.

Changes

Composer package version

Layer / File(s)	Summary
Update package version composer.json	The package version changes from 2.5.0 to 2.15.1.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 45cbe

This PR aligns the Composer package version and lockfile metadata with the 2.15.1 release without changing dependencies; no actionable merge-blocking risk remains after normal checks and review.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main change: aligning Composer release metadata with the plugin release.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/release-version-alignment-20260820

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

🔨 Build Complete - Ready for Testing!

📦 Download Build Artifact (Recommended)

Download the zip build, upload to WordPress and test:

• Build: ultimate-multisite
• ⬇️ Download from GitHub Actions
• ⬇️ Download without Github Account (nightly.link)

🌐 Test in WordPress Playground (Very Experimental)

Click the link below to instantly test this PR in your browser - no installation needed!
Playground support for multisite is very limitied, hopefully it will get better in the future.

🚀 Launch in Playground

Login credentials: admin / password