chore(master): release execution 1.4.0

[StarpTech]

🤖 I have created a release beep boop

1.4.0 (2025-07-02)

Features

• improve apollo gateway compatible field selection validation (#1169) (8c1a063)

Bug Fixes

• support different kinds of close, correct client unsubscribe behaviour (#1174) (b6de322)

---

This PR was generated with Release Please. See documentation.

Summary by CodeRabbit

• Documentation

  • Added a changelog entry for version 1.4.0, highlighting improved field selection validation and enhanced client unsubscribe handling.

• Chores

  • Updated the component version to 1.4.0.

[coderabbitai]

Walkthrough

The changelog for the "execution" component was updated to document new features and bug fixes for version 1.4.0. Additionally, the version number in the release manifest was incremented from 1.3.1 to 1.4.0. No changes were made to public APIs or exported entities.

Changes

Files	Change Summary
execution/CHANGELOG.md	Added changelog entries for version 1.4.0, detailing a feature and a bug fix.
release-please-manifest.json	Updated "execution" component version from 1.3.1 to 1.4.0.

---

📜 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 4d770c7 and 0fcaa80.

📒 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)

• release-please-manifest.json
• execution/CHANGELOG.md

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: Build and test (go 1.23 / windows-latest)

---

🪧 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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

execution/CHANGELOG.md (1)

6-13: Polish changelog phrasing & spelling

A couple of micro-nitpicks for consistency and readability:

-* improve apollo gateway compatible field selection validation
-* support different kinds of close, correct client unsubscribe behaviour
+* Improve Apollo Gateway-compatible field-selection validation
+* Support different kinds of close events, correct client-unsubscribe behavior

– Capitalise proper noun “Apollo Gateway”.
– Hyphenate “Gateway-compatible” to clarify the compound adjective.
– Insert “events” for clarity.
– Use US-English spelling “behavior” (matches the rest of the changelog).
These tweaks keep the style uniform across versions.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 0a849ee and 0f2c191.

📒 Files selected for processing (2)

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

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: Build and test (go 1.23 / windows-latest)

🔇 Additional comments (1)

release-please-manifest.json (1)

2-4: Version bump looks correct

execution moves from 1.3.1 → 1.4.0, which is appropriate for the new feature + bug-fix release. No other manifest entries changed, so nothing further to do.

[StarpTech]

🤖 Created releases:

• execution/v1.4.0

🌻