Skip to content

Conversation

StarpTech
Copy link
Collaborator

@StarpTech StarpTech commented Sep 24, 2025

🤖 I have created a release beep boop

1.6.0 (2025-10-16)

Features

Bug Fixes

  • propagate fetch reasons for interface-related fields (#1312) (5ee3014)

This PR was generated with Release Please. See documentation.

Summary by CodeRabbit

Release Notes

  • New Features

    • Added validation for optional @requires dependencies.
  • Bug Fixes

    • Fixed propagation of fetch reasons for interface-related fields.

Copy link
Contributor

coderabbitai bot commented Sep 24, 2025

Walkthrough

Adds a 1.6.0 entry to execution/CHANGELOG.md documenting validation of optional @requires dependencies and a bug fix for propagation of fetch reasons for interface-related fields, and updates release-please-manifest.json to bump execution from 1.5.0 to 1.6.0. No code or public API changes.

Changes

Cohort / File(s) Summary
Changelog update
execution/CHANGELOG.md
Appends a 1.6.0 entry with a Features section documenting validation of optional @requires dependencies and a Bug Fixes section about propagation of fetch reasons for interface-related fields; no code changes.
Release manifest bump
release-please-manifest.json
Updates execution version from 1.5.0 to 1.6.0; no other fields or public declarations changed.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

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 succinctly describes the primary change by indicating a release bump of the execution component to version 1.6.0, which directly aligns with the updates in both the changelog and the manifest.
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 f53a1fb and 8945b0f.

📒 Files selected for processing (2)
  • execution/CHANGELOG.md (1 hunks)
  • release-please-manifest.json (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (2)
  • execution/CHANGELOG.md
  • release-please-manifest.json
⏰ 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). (2)
  • GitHub Check: Build and test (go 1.25 / windows-latest)
  • GitHub Check: Build and test (go 1.25 / ubuntu-latest)

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

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 ba75e25 and d0c1096.

📒 Files selected for processing (2)
  • execution/CHANGELOG.md (1 hunks)
  • release-please-manifest.json (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:

  • execution/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). (2)
  • GitHub Check: Build and test (go 1.25 / ubuntu-latest)
  • GitHub Check: Build and test (go 1.25 / windows-latest)
🔇 Additional comments (1)
release-please-manifest.json (1)

3-3: Version bump looks good.

Execution component correctly bumped to 1.6.0; aligns with the changelog entry.

@StarpTech StarpTech force-pushed the release-please--branches--master--components--execution branch 4 times, most recently from ffb7588 to cd48065 Compare September 25, 2025 13:29
@StarpTech StarpTech force-pushed the release-please--branches--master--components--execution branch 6 times, most recently from dfe32e7 to f53a1fb Compare October 9, 2025 14:05
@StarpTech StarpTech force-pushed the release-please--branches--master--components--execution branch from f53a1fb to 8945b0f Compare October 16, 2025 11:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants