Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Oct 1, 2025

This PR contains the following updates:

Package Change Age Confidence
pytest-randomly (changelog) >=3.10.1,<4>=4.0.1,<5 age confidence

Release Notes

pytest-dev/pytest-randomly (pytest-randomly)

v4.0.1

Compare Source

  • 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 #&#8203;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 #&#8203;691 <https://github.com/pytest-dev/pytest-randomly/issues/691>__.

v4.0.0

Compare Source

  • 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 #&#8203;687 <https://github.com/pytest-dev/pytest-randomly/issues/687>.
    Thanks to Bryce Drennan for the suggestion in Issue #&#8203;600 <https://github.com/pytest-dev/pytest-randomly/issues/600>
    and initial implementation in PR #&#8203;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 #&#8203;686 <https://github.com/pytest-dev/pytest-randomly/issues/686>__.

v3.16.0

Compare Source

  • Drop Python 3.8 support.

  • Support Python 3.13.


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the dependencies Changes related to dependencies label Oct 1, 2025
@renovate renovate bot enabled auto-merge (rebase) October 1, 2025 20:57
@renovate
Copy link
Contributor Author

renovate bot commented Oct 1, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: poetry.lock
Updating dependencies
Resolving dependencies...


The current project's supported Python range (>=3.8,<4.0) is not compatible with some of the required packages Python requirement:
  - pytest-randomly requires Python >=3.9, so it will not be satisfied for Python >=3.8,<3.9

Because no versions of pytest-randomly match >4.0.1,<5
 and pytest-randomly (4.0.1) requires Python >=3.9, pytest-randomly is forbidden.
So, because protoletariat depends on pytest-randomly (>=4.0.1,<5), version solving failed.

  • Check your dependencies Python requirement: The Python requirement can be specified via the `python` or `markers` properties
    
    For pytest-randomly, a possible solution would be to set the `python` property to ">=3.9,<4.0"

    https://python-poetry.org/docs/dependency-specification/#python-restricted-dependencies,
    https://python-poetry.org/docs/dependency-specification/#using-environment-markers

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

Labels

dependencies Changes related to dependencies

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants