chore(master): release 2.0.0-rc.229

[StarpTech]

🤖 I have created a release beep boop

2.0.0-rc.229 (2025-09-25)

Bug Fixes

• remove index after _entities in the path (#1306) (7d0586e)

---

This PR was generated with Release Please. See documentation.

Summary by CodeRabbit

• New Version
  • Incremented to 2.0.0-rc.229.
• Bug Fixes
  • Corrected path handling by removing a redundant “index” segment after “_entities,” improving link resolution and navigation.
• Documentation
  • Added changelog entry for 2.0.0-rc.229 detailing the bug fix.

[coderabbitai]

Walkthrough

Bumps v2 version in release-please-manifest.json from 2.0.0-rc.228 to 2.0.0-rc.229 and adds a corresponding entry to v2/CHANGELOG.md describing a bug fix. No other files or logic are changed.

Changes

Cohort / File(s)	Summary of changes
Release manifest update release-please-manifest.json	Updated v2 value from "2.0.0-rc.228" to "2.0.0-rc.229".
Changelog entry v2/CHANGELOG.md	Added 2.0.0-rc.229 (2025-09-25) entry noting bug fix: remove index after _entities in the path; retained prior entries.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• chore(master): release 2.0.0-rc.228 #1304 — Consecutive rc version bump in release-please-manifest.json with matching v2 changelog update.
• chore(master): release 2.0.0-rc.227 #1302 — Updates the same v2 field and adds a corresponding v2/CHANGELOG.md entry.
• chore(master): release 2.0.0-rc.226 #1296 — Similar release metadata update: v2 version bump and changelog addition.

Pre-merge checks

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title “chore(master): release 2.0.0-rc.229” clearly and concisely describes the primary purpose of the changeset, namely bumping the project to version 2.0.0-rc.229. It follows a recognized commit convention, is immediately understandable to other developers, and avoids extraneous detail.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7d0586e and a02fa09.

📒 Files selected for processing (2)

• release-please-manifest.json (1 hunks)
• v2/CHANGELOG.md (1 hunks)

🧰 Additional context used

🧠 Learnings (1)

📚 Learning: 2025-08-29T09:35:47.969Z

Learnt from: ysmolski
PR: wundergraph/graphql-go-tools#1282
File: v2/pkg/engine/plan/visitor.go:5-5
Timestamp: 2025-08-29T09:35:47.969Z
Learning: The wundergraph/graphql-go-tools project does not support Go versions < 1.23, so compatibility concerns for features available in Go 1.21+ (like cmp.Or) should not be raised.

Applied to files:

• v2/CHANGELOG.md

🔇 Additional comments (2)

release-please-manifest.json (1)

2-3: Version bump matches release notes.

v2 now points to 2.0.0-rc.229 and aligns with the newly added changelog entry; no additional actions needed.

v2/CHANGELOG.md (1)

3-8: Changelog entry looks correct.

The 2.0.0-rc.229 section cites the right compare link, date, and bug-fix reference; formatting stays consistent with previous entries.

---

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

[StarpTech]

🤖 Created releases:

• v2.0.0-rc.229

🌻