Skip to content

chore(ci): move freezegun from hatch to riot [backport 2.21]#13615

Closed
github-actions[bot] wants to merge 1 commit into2.21from
backport-13612-to-2.21
Closed

chore(ci): move freezegun from hatch to riot [backport 2.21]#13615
github-actions[bot] wants to merge 1 commit into2.21from
backport-13612-to-2.21

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Jun 6, 2025

Backport 995e706 from #13612 to 2.21.

Checklist

  • PR author has checked that all the criteria below are met
  • The PR description includes an overview of the change
  • The PR description articulates the motivation for the change
  • The change includes tests OR the PR description describes a testing strategy
  • The PR description notes risks associated with the change, if any
  • Newly-added code is easy to change
  • The change follows the library release note guidelines
  • The change includes or references documentation updates if necessary
  • Backport labels are set (if applicable)

Reviewer Checklist

  • Reviewer has checked that all the criteria below are met
  • Title is accurate
  • All changes are related to the pull request's stated goal
  • Avoids breaking API changes
  • Testing strategy adequately addresses listed risks
  • Newly-added code is easy to change
  • Release note makes sense to a user of the library
  • If necessary, author has acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment
  • Backport labels are set in a manner that is consistent with the release branch maintenance policy

## Checklist
- [X] PR author has checked that all the criteria below are met
- The PR description includes an overview of the change
- The PR description articulates the motivation for the change
- The change includes tests OR the PR description describes a testing
strategy
- The PR description notes risks associated with the change, if any
- Newly-added code is easy to change
- The change follows the [library release note
guidelines](https://ddtrace.readthedocs.io/en/stable/releasenotes.html)
- The change includes or references documentation updates if necessary
- Backport labels are set (if
[applicable](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting))

## Reviewer Checklist
- [x] Reviewer has checked that all the criteria below are met
- Title is accurate
- All changes are related to the pull request's stated goal
- Avoids breaking
[API](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces)
changes
- Testing strategy adequately addresses listed risks
- Newly-added code is easy to change
- Release note makes sense to a user of the library
- If necessary, author has acknowledged and discussed the performance
implications of this PR as reported in the benchmarks PR comment
- Backport labels are set in a manner that is consistent with the
[release branch maintenance
policy](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)

Signed-off-by: Juanjo Alvarez <[email protected]>
(cherry picked from commit 995e706)
@github-actions github-actions bot added changelog/no-changelog A changelog entry is not required for this PR. CI labels Jun 6, 2025
@github-actions github-actions bot requested review from a team as code owners June 6, 2025 15:09
@github-actions github-actions bot requested review from lievan and wconti27 June 6, 2025 15:09
@github-actions github-actions bot added changelog/no-changelog A changelog entry is not required for this PR. CI labels Jun 6, 2025
@github-actions github-actions bot requested a review from juanjux June 6, 2025 15:09
@pr-commenter
Copy link

pr-commenter bot commented Jun 6, 2025

Benchmarks

Benchmark execution time: 2025-06-06 15:51:09

Comparing candidate commit 9284dc1 in PR branch backport-13612-to-2.21 with baseline commit 226ebd5 in branch 2.21.

Found 0 performance improvements and 0 performance regressions! Performance is the same for 162 metrics, 2 unstable metrics.

@juanjux
Copy link
Collaborator

juanjux commented Jun 9, 2025

Backport not needed for this, closing

@juanjux juanjux closed this Jun 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

changelog/no-changelog A changelog entry is not required for this PR. CI

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant