Release v0.16.1

[jakub-przepiora]

OpenMES v0.16.1

Patch release. Bumps config/version.php → v0.16.1 and finalizes the CHANGELOG.

🐛 Fixed

• Release workflow couldn't build the distributable ZIP (CI) — the release workflow inlined the commit log into a shell LOG="${{ … }}", so a commit message with double quotes (… "Components & serials used" …) broke the script (serials: command not found, exit 127) and no openmmes-*.zip was attached. Release-notes vars now pass through env: instead of ${{ }} interpolation. (The fix itself already merged to main via fix(ci): pass release-notes vars via env, not ${{ }} shell interpolation #165; this release tags it + bumps the version so the tag-triggered build runs the corrected workflow.)

No app/runtime code changes, no new migrations.

---

After you merge this manually (main is branch-protected), I'll tag v0.16.1 — the tag-triggered Release workflow (now fixed on main) will build and attach openmmes-v0.16.1.zip.

[coderabbitai]

Warning

Review limit reached

@jakub-przepiora, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 48 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: ebd9dba2-8ceb-42ca-b91d-0ae9283707ca

📥 Commits

Reviewing files that changed from the base of the PR and between b0ef2c8 and b7be3e9.

📒 Files selected for processing (2)

• CHANGELOG.md
• backend/config/version.php

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release/v0.16.1

---

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.}