Skip to content

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jan 10, 2026

Bumps pytest-randomly from 3.16.0 to 4.0.1.

Changelog

Sourced from pytest-randomly's changelog.

4.0.1 (2025-09-12)

  • Remove the random state caching, which would grow without bound, leaking memory in long test runs. The caching was added to slightly speed up re-using the same (final) seed, but since the final seed is now different for each test, it has no effect.

    PR [#690](https://github.com/pytest-dev/pytest-randomly/issues/690) <https://github.com/pytest-dev/pytest-randomly/issues/687>__.

  • Modify Numpy seed restriction, replacing hashing with a modulo operation. The extra work to hash is unnecessary now that we generate a final seed per test with CRC32. This change saves ~500ns per test when Numpy is installed.

    PR [#691](https://github.com/pytest-dev/pytest-randomly/issues/691) <https://github.com/pytest-dev/pytest-randomly/issues/691>__.

4.0.0 (2025-09-10)

  • Support Python 3.14.

  • Use a different random seed per test, based on the test ID.

    This change should mean that tests exercise more random data values in a given run, and that any randomly-generated identifiers have a lower chance of collision when stored in a shared resource like a database.

    PR [#687](https://github.com/pytest-dev/pytest-randomly/issues/687) <https://github.com/pytest-dev/pytest-randomly/issues/687>. Thanks to Bryce Drennan for the suggestion in Issue [#600](https://github.com/pytest-dev/pytest-randomly/issues/600) <https://github.com/pytest-dev/pytest-randomly/issues/600> and initial implementation in PR [#617](https://github.com/pytest-dev/pytest-randomly/issues/617) <https://github.com/pytest-dev/pytest-randomly/pull/617>__.

  • Move from MD5 to CRC32 for hashing test IDs, as it’s 5x faster and we don’t need cryptographic security.

    Issue [#686](https://github.com/pytest-dev/pytest-randomly/issues/686) <https://github.com/pytest-dev/pytest-randomly/issues/686>__.

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot dependabot bot added dependencies Dependabot Updates pip Dependabot Updates Python labels Jan 10, 2026
@dependabot dependabot bot requested a review from a team as a code owner January 10, 2026 09:48
@dependabot dependabot bot added dependencies Dependabot Updates pip Dependabot Updates Python labels Jan 10, 2026
@github-actions github-actions bot added the community Opened by the Community label Jan 10, 2026
@github-actions
Copy link
Contributor

github-actions bot commented Jan 10, 2026

⚠️ Changes detected in the following folders without a corresponding update to the CHANGELOG.md:

  • prowler (root dependency files changed)

Please add an entry to the corresponding CHANGELOG.md file to maintain a clear history of changes.

@github-actions
Copy link
Contributor

github-actions bot commented Jan 10, 2026

Conflict Markers Resolved

All conflict markers have been successfully resolved in this pull request.

@github-actions
Copy link
Contributor

github-actions bot commented Jan 10, 2026

🔒 Container Security Scan

Image: prowler:b86b7f6
Last scan: 2026-01-20 12:38:31 UTC

📊 Vulnerability Summary

Severity Count
🔴 Critical 3
Total 3

3 package(s) affected

⚠️ Action Required

Critical severity vulnerabilities detected. These should be addressed before merging:

  • Review the detailed scan results
  • Update affected packages to patched versions
  • Consider using a different base image if updates are unavailable

📋 Resources:

@dependabot dependabot bot force-pushed the dependabot/pip/master/pytest-randomly-4.0.1 branch 4 times, most recently from b646370 to 9560e78 Compare January 15, 2026 13:33
Bumps [pytest-randomly](https://github.com/pytest-dev/pytest-randomly) from 3.16.0 to 4.0.1.
- [Changelog](https://github.com/pytest-dev/pytest-randomly/blob/main/CHANGELOG.rst)
- [Commits](pytest-dev/pytest-randomly@3.16.0...4.0.1)

---
updated-dependencies:
- dependency-name: pytest-randomly
  dependency-version: 4.0.1
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot force-pushed the dependabot/pip/master/pytest-randomly-4.0.1 branch from 9560e78 to 5caed45 Compare January 20, 2026 12:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

community Opened by the Community dependencies Dependabot Updates pip Dependabot Updates Python

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant