Skip to content

chore(deps): update pytest-randomly requirement from >=3.12.0 to >=4.1.0 - #43

Merged
unasra merged 1 commit into
mainfrom
dependabot/pip/pytest-randomly-gte-4.1.0
Jul 13, 2026
Merged

chore(deps): update pytest-randomly requirement from >=3.12.0 to >=4.1.0#43
unasra merged 1 commit into
mainfrom
dependabot/pip/pytest-randomly-gte-4.1.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 13, 2026

Copy link
Copy Markdown
Contributor

Updates the requirements on pytest-randomly to permit the latest version.

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>__.

3.16.0 (2024-10-25)

  • Drop Python 3.8 support.

  • Support Python 3.13.

3.15.0 (2023-08-15)

  • Support Python 3.12.

... (truncated)

Commits

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file python Pull requests that update python code labels Jul 13, 2026
Updates the requirements on [pytest-randomly](https://github.com/pytest-dev/pytest-randomly) to permit the latest version.
- [Changelog](https://github.com/pytest-dev/pytest-randomly/blob/main/CHANGELOG.rst)
- [Commits](pytest-dev/pytest-randomly@3.12.0...4.1.0)

---
updated-dependencies:
- dependency-name: pytest-randomly
  dependency-version: 4.1.0
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/pip/pytest-randomly-gte-4.1.0 branch from 448bed9 to 19dd142 Compare July 13, 2026 11:47
@unasra
unasra merged commit 6e5f0da into main Jul 13, 2026
10 checks passed
@dependabot
dependabot Bot deleted the dependabot/pip/pytest-randomly-gte-4.1.0 branch July 13, 2026 12:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file python Pull requests that update python code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant