chore: sync release-please manifest for wren 0.4.0

[goldmedal]

Summary

wren-engine 0.4.0 is already published on PyPI and the wren-v0.4.0 git tag exists, but .release-please-manifest.json still points at 0.3.0 because release-please PR #2228 was never merged.

This bumps core/wren in the manifest from 0.3.0 to 0.4.0 so release-please's state matches reality.

Effects

• After this merges, release-please will reconcile on the next push and auto-close PR chore(main): release wren 0.5.0 #2228 (and delete release-please--branches--main--components--wren) because there are no conventional commits between the new manifest baseline and HEAD that warrant a release.
• The next wren release will be computed from 0.4.0 once new conventional commits land.
• RC dispatch for wren (per fix(ci): read next-release version from release-please branch in rc-release #2232) will now correctly fail-fast with "no pending release" until that happens — this is the intended behaviour.

core/wren-core-py (manifest 0.4.0, tag wren-core-py-v0.4.0) is already aligned and is not changed here.

Test plan

• Confirmed wren-v0.4.0 tag and PyPI release exist.
• After merge, observe release-please workflow run on main close PR chore(main): release wren 0.5.0 #2228.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Version updated to 0.4.0.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: b8a8c16f-5636-48a5-ac41-0107bd41bd77

📥 Commits

Reviewing files that changed from the base of the PR and between 1394f10 and bc7a915.

📒 Files selected for processing (1)

• .release-please-manifest.json

---

Walkthrough

The .release-please-manifest.json file is updated to bump the core/wren package version from 0.3.0 to 0.4.0, aligning it with the core/wren-core-py version already at 0.4.0.

Changes

Version Manifest Update

Layer / File(s)	Summary
Version Increment .release-please-manifest.json	core/wren version is bumped from 0.3.0 to 0.4.0 to match core/wren-core-py.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• fix(ci): resolve component to manifest path in rc-release workflow #2231: Updates workflow lookup logic that consumes the version entry modified in this manifest file.

Suggested labels

core, ci, python

Suggested reviewers

• PaulChen79

Poem

🐰 A version bump hops along the way,
From 0.3 to 0.4 today!
Core and core-py now align,
A manifest dance, perfectly fine. ✨

🚥 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 accurately reflects the main change: syncing the release-please manifest to update core/wren version to 0.4.0.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/sync-release-please-manifest-wren

---

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

_{Review rate limit: 7/8 reviews remaining, refill in 7 minutes and 30 seconds.}

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