Skip to content

Conversation

@rayz
Copy link
Contributor

@rayz rayz commented Jul 30, 2025

What does this PR do?

Creates the 0.52.1 release.

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 review from a team as code owners July 30, 2025 16:15
@github-actions github-actions bot added the documentation Documentation related changes label Jul 30, 2025
@rayz rayz added the changelog/Fixed Fixed features results into a bug fix version bump label Jul 30, 2025
@rayz rayz closed this Jul 30, 2025
@iamsfkhan
Copy link

@rayz When are you releasing the new version?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

changelog/Fixed Fixed features results into a bug fix version bump documentation Documentation related changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants