profitroll/LibBotUniversal
1
0
Fork 0
Code Issues 4 Pull Requests 3 Actions Packages Releases 39 Wiki Activity

Update dependency pytest-asyncio to v1 #208

Merged
Renovate merged 1 commits from renovate/pytest-asyncio-1.x into dev 2025-05-26 08:38:46 +03:00
Conversation 0 Commits 1 Files Changed 1 +1 -1
Renovate commented 2025-05-26 08:33:50 +03:00
Collaborator
Copy Link

This PR contains the following updates:

Package Update Change
pytest-asyncio (changelog) major ==0.26.0 -> ==1.0.0

Release Notes

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

v1.0.0: pytest-asyncio 1.0.0

Compare Source

1.0.0 - 2025-05-26

Removed

  • The deprecated event_loop fixture.
    (#​1106)

Added

  • Prelimiary support for Python 3.14
    (#​1025)

Changed

  • Scoped event loops (e.g. module-scoped loops) are created once rather
    than per scope (e.g. per module). This reduces the number of fixtures
    and speeds up collection time, especially for large test suites.
    (#​1107)
  • The loop_scope argument to pytest.mark.asyncio no longer forces
    that a pytest Collector exists at the level of the specified scope.
    For example, a test function marked with
    pytest.mark.asyncio(loop_scope="class") no longer requires a class
    surrounding the test. This is consistent with the behavior of the
    scope argument to pytest_asyncio.fixture.
    (#​1112)

Fixed

  • An error caused when using pytest's [--setup-plan]{.title-ref}
    option.
    (#​630)
  • Unsuppressed import errors with pytest option
    --doctest-ignore-import-errors
    (#​797)
  • A "fixture not found" error in connection with package-scoped loops
    (#​1052)

Notes for Downstream Packagers

  • Removed a test that had an ordering dependency on other tests.
    (#​1114)

Configuration

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

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, 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 has been generated by Renovate Bot.

This PR contains the following updates: | Package | Update | Change | |---|---|---| | [pytest-asyncio](https://github.com/pytest-dev/pytest-asyncio) ([changelog](https://pytest-asyncio.readthedocs.io/en/latest/reference/changelog.html)) | major | `==0.26.0` -> `==1.0.0` | --- ### Release Notes <details> <summary>pytest-dev/pytest-asyncio (pytest-asyncio)</summary> ### [`v1.0.0`](https://github.com/pytest-dev/pytest-asyncio/releases/tag/v1.0.0): pytest-asyncio 1.0.0 [Compare Source](https://github.com/pytest-dev/pytest-asyncio/compare/v0.26.0...v1.0.0) ### [1.0.0](https://github.com/pytest-dev/pytest-asyncio/tree/1.0.0) - 2025-05-26 #### Removed - The deprecated *event_loop* fixture. ([#&#8203;1106](https://github.com/pytest-dev/pytest-asyncio/issues/1106)) #### Added - Prelimiary support for Python 3.14 ([#&#8203;1025](https://github.com/pytest-dev/pytest-asyncio/issues/1025)) #### Changed - Scoped event loops (e.g. module-scoped loops) are created once rather than per scope (e.g. per module). This reduces the number of fixtures and speeds up collection time, especially for large test suites. ([#&#8203;1107](https://github.com/pytest-dev/pytest-asyncio/issues/1107)) - The *loop_scope* argument to `pytest.mark.asyncio` no longer forces that a pytest Collector exists at the level of the specified scope. For example, a test function marked with `pytest.mark.asyncio(loop_scope="class")` no longer requires a class surrounding the test. This is consistent with the behavior of the *scope* argument to `pytest_asyncio.fixture`. ([#&#8203;1112](https://github.com/pytest-dev/pytest-asyncio/issues/1112)) #### Fixed - An error caused when using pytest's \[--setup-plan]{.title-ref} option. ([#&#8203;630](https://github.com/pytest-dev/pytest-asyncio/issues/630)) - Unsuppressed import errors with pytest option `--doctest-ignore-import-errors` ([#&#8203;797](https://github.com/pytest-dev/pytest-asyncio/issues/797)) - A "fixture not found" error in connection with package-scoped loops ([#&#8203;1052](https://github.com/pytest-dev/pytest-asyncio/issues/1052)) #### Notes for Downstream Packagers - Removed a test that had an ordering dependency on other tests. ([#&#8203;1114](https://github.com/pytest-dev/pytest-asyncio/issues/1114)) </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNi4zNS4wIiwidXBkYXRlZEluVmVyIjoiMzYuMzUuMCIsInRhcmdldEJyYW5jaCI6ImRldiJ9-->
Renovate added 1 commit 2025-05-26 08:33:51 +03:00
Update dependency pytest-asyncio to v1
Some checks failed
Analysis / SonarCloud (pull_request) Successful in 50s
Details
Tests / Build and Test (3.11) (pull_request) Failing after 52s
Details
Tests / Build and Test (3.12) (pull_request) Successful in 1m20s
Details
Tests / Build and Test (3.13) (pull_request) Successful in 1m20s
Details
Analysis / SonarCloud (push) Successful in 50s
Details
dc05eb0ccb
Renovate scheduled this pull request to auto merge when all checks succeed 2025-05-26 08:33:52 +03:00
Renovate merged commit dc05eb0ccb into dev 2025-05-26 08:38:46 +03:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
Kind/Breaking
Breaking change that won't be backward compatible
Kind/Bug
Something is not working
Kind/Documentation
Documentation changes
Kind/Enhancement
Improve existing functionality
Kind/Feature
New functionality
Kind/Security
This is security issue
Kind/Testing
Issue or pull request related to testing
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Need More Info
Feedback is required to reproduce issue or to continue work
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
Renovate profitroll
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: profitroll/LibBotUniversal#208
No description provided.
Delete Branch "renovate/pytest-asyncio-1.x"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?