Skip to content

Conversation

@rickystewart
Copy link
Collaborator

@rickystewart rickystewart commented Nov 17, 2025

Backport 1/1 commits from #157927 on behalf of @rickystewart.


Release note: none
Epic: none


Release justification: Non-production code changes

Release note: none
Epic: none
@rickystewart rickystewart force-pushed the blathers/backport-release-25.2-157927 branch from 508269e to 4af870d Compare November 17, 2025 20:27
@blathers-crl blathers-crl bot added blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot. labels Nov 17, 2025
@blathers-crl blathers-crl bot requested a review from rail November 17, 2025 20:27
@blathers-crl
Copy link

blathers-crl bot commented Nov 17, 2025

Thanks for opening a backport.

Before merging, please confirm that it falls into one of the following categories (select one):

  • Non-production code changes. Includes test-only changes, build system changes, etc.
  • Fixes for serious issues. Defined in the policy as correctness, stability, or security issues, data corruption/loss, significant performance regressions, breaking working and widely used functionality, or an inability to detect and debug production issues.
  • Other approved changes. These changes must be gated behind a disabled-by-default feature flag unless there is a strong justification not to.

Add a brief release justification to the PR description explaining your selection.

Also, confirm that the change does not break backward compatibility and complies with all aspects of the backport policy.

All backports must be reviewed by the TL and EM for the owning area.

@blathers-crl blathers-crl bot added backport Label PR's that are backports to older release branches T-code-systems labels Nov 17, 2025
@blathers-crl
Copy link

blathers-crl bot commented Nov 17, 2025

✅ PR #157935 is compliant with backport policy

Confidence: high
Backward compatible: true
Explanation: The PR changes a file classified as non-production under development tools ('pkg/cmd/roachtest/'). According to the policy, changes that only affect non-production code such as tests, development tools, or build configurations do not require a critical bug justification or a feature flag. These types of changes are exempt from the standard backport requirements.

🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.

@cockroach-teamcity
Copy link
Member

This change is Reviewable

@blathers-crl blathers-crl bot added the backport-test-only Used to denote the backport has only non-production changes label Nov 17, 2025
@rickystewart rickystewart merged commit 33e58ca into cockroachdb:release-25.2 Nov 17, 2025
16 checks passed
@rickystewart rickystewart deleted the blathers/backport-release-25.2-157927 branch November 17, 2025 21:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport Label PR's that are backports to older release branches backport-test-only Used to denote the backport has only non-production changes blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot. T-code-systems v25.2.10

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants