Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update python-nonmajor #1131

Conversation

renovate-bot
Copy link
Contributor

@renovate-bot renovate-bot commented Jul 17, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
pytest (changelog) ==8.2.2 -> ==8.3.2 age adoption passing confidence
pytest-asyncio (changelog) ==0.23.7 -> ==0.23.8 age adoption passing confidence

Release Notes

pytest-dev/pytest (pytest)

v8.3.2

Compare Source

pytest 8.3.2 (2024-07-24)

Bug fixes

  • #​12652: Resolve regression [conda]{.title-ref} environments where no longer being automatically detected.

    -- by RonnyPfannschmidt{.interpreted-text role="user"}

v8.3.1

Compare Source

pytest 8.3.1 (2024-07-20)

The 8.3.0 release failed to include the change notes and docs for the release. This patch release remedies this. There are no other changes.

v8.3.0

Compare Source

pytest-dev/pytest-asyncio (pytest-asyncio)

v0.23.8: pytest-asyncio 0.23.8

Compare Source

0.23.8 (2024-07-17)

  • Fixes a bug that caused duplicate markers in async tests #​813

Known issues

As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see #​706). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved.


Configuration

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

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

@renovate-bot renovate-bot requested a review from a team as a code owner July 17, 2024 18:38
@renovate-bot renovate-bot changed the title chore(deps): update dependency pytest-asyncio to v0.23.8 chore(deps): update python-nonmajor Jul 20, 2024
@renovate-bot renovate-bot force-pushed the renovate/python-nonmajor branch from b26e13a to 13734a6 Compare July 20, 2024 19:33
@renovate-bot renovate-bot force-pushed the renovate/python-nonmajor branch from 13734a6 to f4bfd5e Compare July 22, 2024 13:01
@renovate-bot renovate-bot force-pushed the renovate/python-nonmajor branch from f4bfd5e to 5b19273 Compare July 22, 2024 18:53
@renovate-bot renovate-bot force-pushed the renovate/python-nonmajor branch from 5b19273 to eee90d5 Compare July 25, 2024 11:04
@renovate-bot renovate-bot force-pushed the renovate/python-nonmajor branch 2 times, most recently from aadab13 to 3845bb3 Compare July 29, 2024 18:02
@renovate-bot renovate-bot force-pushed the renovate/python-nonmajor branch from 3845bb3 to a6181d6 Compare July 29, 2024 19:34
@jackwotherspoon jackwotherspoon merged commit 2aa8447 into GoogleCloudPlatform:main Jul 29, 2024
8 checks passed
@renovate-bot renovate-bot deleted the renovate/python-nonmajor branch July 29, 2024 19:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants