fix: fix rewriting an interface object implementing interface

[devsergiy]

Update engine to 2.0.0-rc.218 (2025-08-07)

Bug Fixes

• fix rewriting an interface object implementing interface (#1265) (8c8c9de)

Summary by CodeRabbit

• Chores
  • Updated several internal dependencies to their latest versions for improved stability and compatibility. No user-facing features or changes were introduced.

Checklist

• I have discussed my proposed changes in an issue and have received approval to proceed.
• I have followed the coding standards of the project.
• Tests or benchmarks have been added or updated.
• Documentation has been updated on https://github.com/wundergraph/cosmo-docs.
• I have read the Contributors Guide.

[coderabbitai]

Walkthrough

This change updates dependency versions in the go.mod files for both the router and router-tests components. The updates include newer commits for github.com/wundergraph/cosmo/demo, github.com/wundergraph/cosmo/router, and a version bump for github.com/wundergraph/graphql-go-tools/v2. No application code or exported declarations were modified.

Changes

Cohort / File(s)	Change Summary
Router and Router-Tests Dependency Bumps router/go.mod, router-tests/go.mod	Updated dependency versions: github.com/wundergraph/graphql-go-tools/v2 bumped from rc.217 to rc.218; in router-tests/go.mod, github.com/wundergraph/cosmo/demo and github.com/wundergraph/cosmo/router updated to newer commits. No other dependency or code changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• fix: go.mod references to security merge commit #2048: Updates versions of github.com/wundergraph/cosmo/router and github.com/wundergraph/graphql-go-tools/v2 in go.mod files, similar dependency version bumps.
• fix: fix checking presence of type fragment mapped to interface object #2001: Updates the same dependencies in router-tests/go.mod and router/go.mod, but to earlier versions.
• fix: fix merging fetches and add dependencies update #2053: Updates github.com/wundergraph/cosmo/demo, github.com/wundergraph/cosmo/router, and github.com/wundergraph/graphql-go-tools/v2 dependencies in the same files, indicating direct relation in dependency management.

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch sergiy/eng-7751-fix-rewriting-abstract-selection-for-interface-object

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[github-actions]

❌ Internal Query Planner CI checks failed

The Internal Query Planner CI checks failed in the celestial repository, and this is going to stop the merge of this PR.
If you are part of the WunderGraph organization, you can see the PR with more details.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

router/go.mod (1)

162-164: Run go mod tidy to clean up transitive drift

After removing (or updating) the replace, run go mod tidy so the go.sum reflects the new version set and any redundant entries disappear.
Keeps CI reproducible and prevents accidental mismatches between router and router-tests.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0bf88c3 and 0bddafb.

⛔ Files ignored due to path filters (2)

• router-tests/go.sum is excluded by !**/*.sum
• router/go.sum is excluded by !**/*.sum

📒 Files selected for processing (2)

• router-tests/go.mod (1 hunks)
• router/go.mod (1 hunks)

🧰 Additional context used

🧠 Learnings (3)

📓 Common learnings

Learnt from: SkArchon
PR: wundergraph/cosmo#2067
File: router/pkg/authentication/jwks_token_decoder.go:80-106
Timestamp: 2025-07-21T14:46:34.879Z
Learning: In the Cosmo router project, required field validation for JWKS configuration (Secret, Algorithm, KeyId) is handled at the JSON schema level in config.schema.json rather than through runtime validation in the Go code at router/pkg/authentication/jwks_token_decoder.go.

Learnt from: SkArchon
PR: wundergraph/cosmo#2067
File: router/pkg/config/config.schema.json:1637-1644
Timestamp: 2025-07-21T15:06:36.664Z
Learning: In the Cosmo router project, when extending JSON schema validation for security-sensitive fields like JWKS secrets, backwards compatibility is maintained by implementing warnings in the Go code rather than hard validation constraints in the schema. This allows existing configurations to continue working while alerting users to potential security issues.

📚 Learning: in the cosmo router project, required field validation for jwks configuration (secret, algorithm, ke...

Learnt from: SkArchon
PR: wundergraph/cosmo#2067
File: router/pkg/authentication/jwks_token_decoder.go:80-106
Timestamp: 2025-07-21T14:46:34.879Z
Learning: In the Cosmo router project, required field validation for JWKS configuration (Secret, Algorithm, KeyId) is handled at the JSON schema level in config.schema.json rather than through runtime validation in the Go code at router/pkg/authentication/jwks_token_decoder.go.

Applied to files:

• router-tests/go.mod

📚 Learning: in the cosmo router project, when extending json schema validation for security-sensitive fields lik...

Learnt from: SkArchon
PR: wundergraph/cosmo#2067
File: router/pkg/config/config.schema.json:1637-1644
Timestamp: 2025-07-21T15:06:36.664Z
Learning: In the Cosmo router project, when extending JSON schema validation for security-sensitive fields like JWKS secrets, backwards compatibility is maintained by implementing warnings in the Go code rather than hard validation constraints in the schema. This allows existing configurations to continue working while alerting users to potential security issues.

Applied to files:

• router-tests/go.mod

⏰ 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). (12)

• GitHub Check: build-router
• GitHub Check: build_test
• GitHub Check: image_scan
• GitHub Check: build_push_image
• GitHub Check: image_scan (nonroot)
• GitHub Check: build_push_image (nonroot)
• GitHub Check: integration_test (./. ./fuzzquery ./lifecycle ./modules)
• GitHub Check: integration_test (./telemetry)
• GitHub Check: integration_test (./events)
• GitHub Check: build_test
• GitHub Check: Analyze (go)
• GitHub Check: Analyze (javascript-typescript)

🔇 Additional comments (2)

router/go.mod (1)

34-34: Outdated suggestion: no active replace directive

The replace github.com/wundergraph/graphql-go-tools/v2 => ../../graphql-go-tools/v2 lines in router/go.mod (lines 165–166) are already commented out, so Go will pull v2.0.0-rc.218 as declared on line 34. You can safely remove those commented-out replace lines to clean up the file.

Likely an incorrect or invalid review comment.

router-tests/go.mod (1)

26-30: Local replace paths must mirror the bumped commits

You upgraded:

• cosmo/demo → 0bf88c35298d
• cosmo/router → 0bf88c35298d
• graphql-go-tools/v2 → v2.0.0-rc.218

But replace lines (176-180) still map these modules to local directories.
Ensure those directories are checked out at the same commits / tags, otherwise the test module will compile different code than the version string suggests, obscuring regressions.

Consider dropping the replace for graphql-go-tools here as well, matching what you decide in router/go.mod.