Skip to content

chore(master): release 2.0.0-rc.250#1387

Merged
jensneuse merged 1 commit intomasterfrom
release-please--branches--master--components--graphql-go-tools
Feb 16, 2026
Merged

chore(master): release 2.0.0-rc.250#1387
jensneuse merged 1 commit intomasterfrom
release-please--branches--master--components--graphql-go-tools

Conversation

@StarpTech
Copy link
Copy Markdown
Collaborator

@StarpTech StarpTech commented Feb 16, 2026

🤖 I have created a release beep boop

2.0.0-rc.250 (2026-02-16)

Features

  • add flag for relaxed nullability checks on same shape (#1378) (6be2e74)

This PR was generated with Release Please. See documentation.

Summary by CodeRabbit

  • New Features

    • Added a new flag for relaxed nullability checks on shape validation.
  • Chores

    • Updated version to 2.0.0-rc.250.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Feb 16, 2026

No actionable comments were generated in the recent review. 🎉


📝 Walkthrough

Walkthrough

Update the v2 release candidate from 2.0.0-rc.249 to 2.0.0-rc.250 in the release manifest and add a v2 changelog entry documenting a new flag for relaxed nullability checks on shapes.

Changes

Cohort / File(s) Summary
Release manifest & changelog
release-please-manifest.json, v2/CHANGELOG.md
Bumps v2 to 2.0.0-rc.250 in the manifest; adds a changelog entry for 2.0.0-rc.250 noting a new flag for relaxed nullability checks on the same shape.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

Suggested labels

autorelease: tagged

🚥 Pre-merge checks | ✅ 3
✅ 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 'chore(master): release 2.0.0-rc.250' clearly and specifically identifies the main purpose of the PR—releasing version 2.0.0-rc.250, which is confirmed by the version bumps in release-please-manifest.json and the new changelog entry.
Merge Conflict Detection ✅ Passed ✅ No merge conflicts detected when merging into master

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ 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

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

@StarpTech StarpTech force-pushed the release-please--branches--master--components--graphql-go-tools branch from 009f58b to 0c216aa Compare February 16, 2026 15:26
@jensneuse jensneuse merged commit 1dcbd3b into master Feb 16, 2026
12 checks passed
@jensneuse jensneuse deleted the release-please--branches--master--components--graphql-go-tools branch February 16, 2026 15:30
@StarpTech
Copy link
Copy Markdown
Collaborator Author

🤖 Created releases:

🌻

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