Skip to content

Conversation

@rayz
Copy link
Contributor

@rayz rayz commented Jul 31, 2025

What does this PR do?

Title

Description of the Change

Alternate Designs

Possible Drawbacks

Verification Process

Additional Notes

Release Notes

Review checklist (to be filled by reviewers)

  • Feature or bug fix MUST have appropriate tests (unit, integration, etc...)
  • PR title must be written as a CHANGELOG entry (see why)
  • Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
  • PR must have one changelog/ label attached. If applicable it should have the backward-incompatible label attached.
  • PR should not have do-not-merge/ label attached.
  • If Applicable, issue must have kind/ and severity/ labels attached at least.

@rayz rayz requested a review from a team as a code owner July 31, 2025 15:52
@rayz rayz added the changelog/no-changelog Changes don't appear in changelog label Jul 31, 2025
@rayz rayz merged commit 30da093 into master Jul 31, 2025
12 of 13 checks passed
@rayz rayz deleted the rayz/0.52.2-dev branch July 31, 2025 16:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

changelog/no-changelog Changes don't appear in changelog

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants