chore(master): release 2.0.0-rc.242

[StarpTech]

🤖 I have created a release beep boop

2.0.0-rc.242 (2025-12-19)

Bug Fixes

• skip invalid locations (#1357) (5154906)

---

This PR was generated with Release Please. See documentation.

Summary by CodeRabbit

• Bug Fixes
  • Fixed handling of invalid locations

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Updated version manifest and changelog for v2 release candidate 2.0.0-rc.242. Version incremented from rc.241 with a new changelog entry documenting a bug fix for invalid location handling.

Changes

Cohort / File(s)	Summary
Release v2.0.0-rc.242 release-please-manifest.json, v2/CHANGELOG.md	Version bumped from 2.0.0-rc.241 to 2.0.0-rc.242 in manifest; new changelog entry added for bug fix addressing invalid location skipping

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• chore(master): release 2.0.0-rc.241 #1353: Direct predecessor in the release sequence—bumped v2 to rc.241, this PR continues with rc.242
• chore(master): release 2.0.0-rc.232 #1330: Automated release bump following the same pattern of manifest and changelog updates
• chore(master): release 2.0.0-rc.210 #1247: Prior release bump updating the same release-related files

Suggested labels

autorelease: tagged

Pre-merge checks and finishing touches

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: releasing version 2.0.0-rc.242, which is confirmed by updates to the manifest and changelog.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch release-please--branches--master--components--graphql-go-tools

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5154906 and ea6d015.

📒 Files selected for processing (2)

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

🧰 Additional context used

🧠 Learnings (2)

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

Learnt from: ysmolski
Repo: wundergraph/graphql-go-tools PR: 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

📚 Learning: 2025-12-09T15:31:05.946Z

Learnt from: SkArchon
Repo: wundergraph/graphql-go-tools PR: 1351
File: v2/pkg/engine/resolve/context.go:160-162
Timestamp: 2025-12-09T15:31:05.946Z
Learning: In the graphql-go-tools repository, Context instances in v2/pkg/engine/resolve must be created using NewContext() rather than Context{} literals. The codebase intentionally avoids defensive nil checks for Context.subgraphErrors to enforce this pattern and fail fast on improper usage. Do not suggest adding defensive nil checks for map fields in Context that are initialized by NewContext().

Applied to files:

• v2/CHANGELOG.md

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (5)

• GitHub Check: Build and test (go 1.25 / windows-latest)
• GitHub Check: Build and test (go 1.25 / ubuntu-latest)
• GitHub Check: lint
• GitHub Check: Build and test (go 1.25 / windows-latest)
• GitHub Check: Build and test (go 1.25 / ubuntu-latest)

🔇 Additional comments (2)

release-please-manifest.json (1)

2-2: Version bump correctly applied.

The v2 version has been incremented from rc.241 to rc.242, and the execution version is correctly left unchanged.

v2/CHANGELOG.md (1)

3-9: Changelog entry properly formatted and linked.

The new release entry for 2.0.0-rc.242 is correctly structured with version link, date, and bug fix entry. Issue and commit references are properly formatted.

---

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

[StarpTech]

🤖 Created releases:

• v2.0.0-rc.242

🌻