release: version bump + changelog left behind by the merge

[namixai]

The source fix merged; the release metadata did not travel with it. The version bump and changelog were pushed to the same branch after the merge had already been taken at an earlier commit, and the branch was deleted on merge — so main still carries the old version while main's code is the fixed one.

That combination is worth naming, because it fails quietly: publishing from main today would either be rejected by npm (version exists) or, if someone bumped by hand, ship a number nobody can trace to a commit.

This PR is only the two files that were left behind:

package.json	version bump
CHANGELOG.md	the entry describing what shipped

No source changes — the fix itself is already on main.

Minor, not patch: VenueEntry gained a required field, the manifest gained an entry, and the meaning of the list changed. Only TypeScript code that constructs or implements the interface breaks; readers just see one more venue and one more field.

⚠️ Reminder carried from the release runbook: files lists dist and there is no prepublishOnly, so npm will not build for you. Publishing without npm run build ships a version whose changelog promises the fix and whose code is unchanged — and that looks exactly like a successful release.

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 16 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: 171d476a-ea4f-4561-82f5-0905445ddd9e

📥 Commits

Reviewing files that changed from the base of the PR and between 91aa07e and 1ef6dfb.

📒 Files selected for processing (2)

• CHANGELOG.md
• package.json

---

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