fix: go.mod references to security merge commit

[SkArchon]

Summary by CodeRabbit

• Chores
  • Updated several dependencies to newer versions for improved stability and compatibility.
  • Promoted a previously indirect dependency to a direct dependency in one module.

Update references to go.mod router

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

Dependency versions were updated in the go.mod files of both the demo and router-tests modules. Several dependencies were upgraded to newer versions, one new indirect dependency was added, and one indirect dependency was promoted to a direct dependency.

Changes

Files	Change Summary
demo/go.mod	Updated github.com/wundergraph/cosmo/router, github.com/go-chi/chi/v5, and github.com/wundergraph/graphql-go-tools/v2 to newer versions; added indirect dependency github.com/cep21/circuit/v4.
router-tests/go.mod	Upgraded github.com/wundergraph/cosmo/router, github.com/wundergraph/cosmo/demo, and subgraphs dependencies; promoted github.com/wundergraph/astjson from indirect to direct dependency.

---

📜 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 7e36d17 and b9a13ce.

📒 Files selected for processing (1)

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

🚧 Files skipped from review as they are similar to previous changes (1)

• 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). (8)

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

---

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

🪧 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.
  • @coderabbitai modularize this function.
• 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.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

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

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

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 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]

Router image scan passed

✅ No security vulnerabilities found in image:

ghcr.io/wundergraph/cosmo/router:sha-dd7cfdd78ceed5aefb73de58fd8b36cf6cae2230

[coderabbitai]

Actionable comments posted: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 10f2e5f and 7e36d17.

⛔ Files ignored due to path filters (1)

• demo/go.sum is excluded by !**/*.sum

📒 Files selected for processing (2)

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

🔇 Additional comments (5)

router-tests/go.mod (1)

25-25: Confirm the need for astjson as a direct dependency

github.com/wundergraph/astjson is promoted from indirect to direct, yet no code changes accompany this bump in the PR. If the package is not imported directly in router-tests, go mod tidy will revert this.
Double-check that a forthcoming change really imports it; otherwise keep it indirect.

demo/go.mod (4)

14-14: Router bumped – verify local replace directives & downstream callers

github.com/wundergraph/cosmo/router now tracks commit 10f2e5f9c79e.
Ensure every workspace replace (e.g. in router-tests/go.mod) or downstream repo is also updated so that a single router SHA is built everywhere; otherwise go work/go mod vendor will pick the highest version and silently shadow older builds.

---

42-42: New indirect cep21/circuit/v4 – dead code check

The circuit-breaker library is newly introduced as indirect. If no packages import it directly or via another new dependency, it will vanish on go mod tidy.
Run go mod why github.com/cep21/circuit/v4 to confirm it is genuinely needed.

---

63-63: Minor chi patch looks good

go-chi/chi patched from v5.2.1 → v5.2.2. Only bug-fixes, no breaking API; safe bump.

---

154-154: Large jump in graphql-go-tools RC – smoke-test parser

RC 186 → RC 203 includes several AST and validation changes. Run router/unit tests that compile query plans to catch regressions early.