Skip to content

chore(deps-dev): bump pytest-randomly from 3.16.0 to 4.1.0#10966

Open
dependabot[bot] wants to merge 1 commit intomasterfrom
dependabot/pip/master/pytest-randomly-4.1.0
Open

chore(deps-dev): bump pytest-randomly from 3.16.0 to 4.1.0#10966
dependabot[bot] wants to merge 1 commit intomasterfrom
dependabot/pip/master/pytest-randomly-4.1.0

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github May 2, 2026

Bumps pytest-randomly from 3.16.0 to 4.1.0.

Changelog

Sourced from pytest-randomly's changelog.

4.1.0 (2026-04-20)

  • Fix a crash with Faker installed when explicitly enabling and disabling the plugin (via -p randomly -p no:randomly).

    Thanks to mojosan77 for the report in Issue [#718](https://github.com/pytest-dev/pytest-randomly/issues/718) <https://github.com/pytest-dev/pytest-randomly/issues/718>__.

  • Drop Python 3.9 support.

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 dependabot Bot added dependencies Dependabot Updates pip Dependabot Updates Python labels May 2, 2026
@dependabot dependabot Bot requested a review from a team as a code owner May 2, 2026 01:51
@dependabot dependabot Bot added the pip Dependabot Updates Python label May 2, 2026
Bumps [pytest-randomly](https://github.com/pytest-dev/pytest-randomly) from 3.16.0 to 4.1.0.
- [Changelog](https://github.com/pytest-dev/pytest-randomly/blob/main/CHANGELOG.rst)
- [Commits](pytest-dev/pytest-randomly@3.16.0...4.1.0)

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

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot force-pushed the dependabot/pip/master/pytest-randomly-4.1.0 branch from ca093b6 to fb29f74 Compare May 5, 2026 14:07
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 5, 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
Copy Markdown
Contributor

github-actions Bot commented May 5, 2026

Conflict Markers Resolved

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

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 5, 2026

🔒 Container Security Scan

Image: prowler:57712f7
Last scan: 2026-05-05 14:16:56 UTC

📊 Vulnerability Summary

Severity Count
🔴 Critical 4
Total 4

4 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:

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

Labels

dependencies Dependabot Updates pip Dependabot Updates Python

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants