Skip to content

chore(dev): update dev dependencies (non-major)#855

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/dev-dependencies
Open

chore(dev): update dev dependencies (non-major)#855
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/dev-dependencies

Conversation

@renovate

@renovate renovate Bot commented Dec 10, 2025 •
edited
Loading

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
basedpyright 1.35.0 → 1.39.7 age confidence
coverage 7.12.0 → 7.14.1 age confidence
mypy (changelog) 1.19.0 → 1.20.2 age confidence
pendulum 3.1.0 → 3.2.0 age confidence
pre-commit 4.5.0 → 4.6.0 age confidence
pytest-asyncio (changelog) 1.3.0 → 1.4.0 age confidence
pytest-cov (changelog) 7.0.0 → 7.1.0 age confidence
ruff (source, changelog) 0.14.8 → 0.15.16 age confidence

Release Notes

detachhead/basedpyright (basedpyright)

v1.39.7: (pyright 1.1.410)

Compare Source

What's Changed

  • don't create a copy of the basedpyright-langserver executable in the vscode extension unless running on windows by @​DetachHead in DetachHead#1810
    • this was a hacky way to try to avoid issues updating basedpyright while the language server is running, but this was never actually a problem on linux & macOS because executables can be deleted while running
  • fix empty semantic tokens response interfering with other language servers when basedpyright.disableLanguageServices is set by @​DetachHead in DetachHead#1815
  • avoid duplicated capability registrations by @​DetachHead in DetachHead#1816

Full Changelog: DetachHead/basedpyright@v1.39.6...v1.39.7

v1.39.6: (pyright 1.1.410)

Compare Source

What's Changed

New Contributors

Full Changelog: DetachHead/basedpyright@v1.39.5...v1.39.6

v1.39.5: (pyright 1.1.409)

Compare Source

What's Changed

  • fix error attempting to baseline diagnostics from the new string.templatelib module when targeting python 3.14 by @​DetachHead in DetachHead#1801

Full Changelog: DetachHead/basedpyright@v1.39.4...v1.39.5

v1.39.4: (pyright 1.1.409)

Compare Source

What's Changed

New Contributors

Full Changelog: DetachHead/basedpyright@v1.39.3...v1.39.4

v1.39.3: (pyright 1.1.409)

Compare Source

What's Changed

  • fix docs site not being deployed, which was caused by some changes I made to improve the security of our CI by @​DetachHead in DetachHead#1782

Full Changelog: DetachHead/basedpyright@v1.39.2...v1.39.3

v1.39.2: (pyright 1.1.409)

Compare Source

What's Changed

  • fix basedpyright being broken in the playground caused by browser-basedpyright being published with nothing in it by @​DetachHead in DetachHead#1778

Full Changelog: DetachHead/basedpyright@v1.39.1...v1.39.2

v1.39.1: (pyright 1.1.409)

Compare Source

What's Changed

Full Changelog: DetachHead/basedpyright@v1.39.0...v1.39.1

v1.39.0: (pyright 1.1.408)

Compare Source

What's Changed

new diagnostic rule - reportEmptyAbstractUsage

pyright only reports an error when you instantiate an abstract class that has unimplemented abstract methods. but a class that explicitly extends ABC (or uses ABCMeta) with no abstract methods can also be instantiated, and pyright has no issue with that:

from abc import ABC

class Foo(ABC):
    """abstract class with no abstract methods"""

foo = Foo()  # no error

but the author of the class likely intended this class not to be used directly, and instead subtyped. so if a class extends ABC but defines no abstract methods, instantiating it is likely unintentional.

the reportEmptyAbstractUsage rule flags such instantiations. see the docs for more info.

implemented by @​KotlinIsland in DetachHead#1748 (some fixes by @​detachhead in DetachHead#1766)

Full Changelog: DetachHead/basedpyright@v1.38.4...v1.39.0

v1.38.4: (pyright 1.1.408)

Compare Source

What's Changed

Full Changelog: DetachHead/basedpyright@v1.38.3...v1.38.4

v1.38.3: (pyright 1.1.408)

Compare Source

What's Changed

  • fix ordering of code actions and don't show # pyright:ignore[reportImportCycles] code action because it doesn't work by @​NCBM in DetachHead#1753

Full Changelog: DetachHead/basedpyright@v1.38.2...v1.38.3

v1.38.2: (pyright 1.1.408)

Compare Source

What's Changed

Full Changelog: DetachHead/basedpyright@v1.38.1...v1.38.2

v1.38.1: (pyright 1.1.408)

Compare Source

What's Changed

New Contributors

Full Changelog: DetachHead/basedpyright@v1.38.0...v1.38.1

v1.38.0: (pyright 1.1.408)

Compare Source

What's Changed

  • show the default value from the implementation signature when displaying an overload signature (eg. hover and signature help) if its default value is an ellipsis by @​DetachHead in DetachHead#1717
  • fix: don't comment out return types in stub generation by @​veeceey in DetachHead#1724
  • add more quick fixes for specific error types by @​NCBM in DetachHead#1721
    • reportUnnecessaryCast
    • reportUnusedCallResult
    • reportSelfClsDefault
  • fix logged message for pyright executable fallback in vscode extension by @​veeceey in DetachHead#1723

New Contributors

Full Changelog: DetachHead/basedpyright@v1.37.4...v1.38.0

v1.37.4: (pyright 1.1.408)

Compare Source

What's Changed

New Contributors

Full Changelog: DetachHead/basedpyright@v1.37.3...v1.37.4

v1.37.3: (pyright 1.1.408)

Compare Source

What's Changed

  • fix infinite recursion crash when subject of match statement of type Never is used in the left side of a call in the case block by @​DetachHead in DetachHead#1711

Full Changelog: DetachHead/basedpyright@v1.37.2...v1.37.3

v1.37.2: (pyright 1.1.408)

Compare Source

What's Changed

Full Changelog: DetachHead/basedpyright@v1.37.1...v1.37.2

v1.37.1: (pyright 1.1.408)

Compare Source

What's Changed

Full Changelog: DetachHead/basedpyright@v1.37.0...v1.37.1

v1.37.0: (pyright 1.1.407)

Compare Source

What's Changed

New Contributors

Full Changelog: DetachHead/basedpyright@v1.36.2...v1.37.0

v1.36.2: (pyright 1.1.407)

Compare Source

What's Changed

New Contributors

Full Changelog: DetachHead/basedpyright@v1.36.1...v1.36.2

v1.36.1: (pyright 1.1.407)

Compare Source

What's Changed

Full Changelog: DetachHead/basedpyright@v1.36.0...v1.36.1

v1.36.0: (pyright 1.1.407)

Compare Source

What's Changed

Full Changelog: DetachHead/basedpyright@v1.35.0...v1.36.0

coveragepy/coveragepy (coverage)

v7.14.1

Compare Source

  • Fix: the HTML report used typographic niceties to make file paths more
    readable by adding a small amount of space around slashes. Those spaces
    interfered with searching the page for file paths of interest. Now the report
    uses CSS to accomplish the same visual tweak so that searches with slashes
    work correctly. Closes issue 2170_.

  • Add a 3.16 PyPI classifier <hugo-316_>_ since we test on the 3.16 main
    branch.

.. _issue 2170: #​2170
.. _hugo-316: https://mastodon.social/@​hugovk/116588523571204490

.. _changes_7-14-0:

v7.14.0

Compare Source

  • Feature: now when running one of the reporting commands, if there are
    parallel data files that need combining, they will be implicitly combined
    before creating the report. There is no option to avoid the combination; let
    us know if you have a use case that requires it. Thanks, Tim Hatch <pull 2162_>. Closes issue 1781.

  • Fix: the output from combine was too verbose, listing each file
    considered. Now it shows a single line with the counts of files combined,
    files skipped, and files with errors. The -q flag suppresses this line.
    The old detailed lines are available with the new --debug=combine option.

  • Fix: running a Python file through a symlink now sets the sys.path correctly,
    matching regular Python behavior. Fixes issue 2157_.

  • Fix: Collector.flush_data could fail with "RuntimeError: Set changed
    size during iteration" when a tracer in another thread added a line to the
    per-file set that add_lines (or add_arcs) was iterating. The values
    passed to CoverageData are now snapshotted via dict.copy() and
    set.copy(), which are atomic under the GIL. Thanks, Alex Vandiver <pull 2165_>_.

  • Fix: the soft keyword lazy is now bolded in HTML reports.

  • We are no longer testing eventlet support. Eventlet started issuing stern
    deprecation warnings that break our tests. Our support code is still there.

.. _issue 1781: #​1781
.. _issue 2157: #​2157
.. _pull 2162: #​2162
.. _pull 2165: #​2165

.. _changes_7-13-5:

v7.13.5

Compare Source

  • Fix: issue 2138_ describes a memory leak that happened when repeatedly
    using the Coverage API with in-memory data. This is now fixed.

  • Fix: the markdown-formatted coverage report didn't fully escape special
    characters in file paths (issue 2141). This would be very unlikely to
    cause a problem, but now it's done properly, thanks to Ellie Ayla <pull 2142_>    .

  • Fix: the C extension wouldn't build on VS2019, but now it does (issue 2145_).

.. _issue 2138: #​2138
.. _issue 2141: #​2141
.. _pull 2142: #​2142
.. _issue 2145: #​2145

.. _changes_7-13-4:

v7.13.4

Compare Source

  • Fix: the third-party code fix in 7.13.3 required examining the parent
    directories where coverage was run. In the unusual situation that one of the
    parent directories is unreadable, a PermissionError would occur, as
    described in issue 2129_. This is now fixed.

  • Fix: in test suites that change sys.path, coverage.py could fail with
    "RuntimeError: Set changed size during iteration" as described and fixed in
    pull 2130_. Thanks, Noah Fatsi.

  • We now publish ppc64le wheels, thanks to Pankhudi Jain <pull 2121_>_.

.. _pull 2121: #​2121
.. _issue 2129: #​2129
.. _pull 2130: #​2130

.. _changes_7-13-3:

v7.13.3

Compare Source

  • Fix: in some situations, third-party code was measured when it shouldn't have
    been, slowing down test execution. This happened with layered virtual
    environments such as uv sometimes makes. The problem is fixed, closing issue 2082_. Now any directory on sys.path that is inside a virtualenv is
    considered third-party code.

.. _issue 2082: #​2082

.. _changes_7-13-2:

v7.13.2

Compare Source

  • Fix: when Python is installed via symlinks, for example with Homebrew, the
    standard library files could be incorrectly included in coverage reports.
    This is now fixed, closing issue 2115_.

  • Fix: if a data file is created with no read permissions, the combine step
    would fail completely. Now a warning is issued and the file is skipped.
    Closes issue 2117_.

.. _issue 2115: #​2115
.. _issue 2117: #​2117

.. _changes_7-13-1:

v7.13.1

Compare Source

  • Added: the JSON report now includes a "start_line" key for function and
    class regions, indicating the first line of the region in the source. Closes
    issue 2110_.

  • Added: The debug data command now takes file names as arguments on the
    command line, so you can inspect specific data files without needing to set
    the COVERAGE_FILE environment variable.

  • Fix: the JSON report used to report module docstrings as executed lines,
    which no other report did, as described in issue 2105_. This is now fixed,
    thanks to Jianrong Zhao.

  • Fix: coverage.py uses a more disciplined approach to detecting where
    third-party code is installed, and avoids measuring it. This shouldn't change
    any behavior. If you find that it does, please get in touch.

  • Performance: data files that will be combined now record their hash as part
    of the file name. This lets us skip duplicate data more quickly, speeding the
    combining step.

  • Docs: added a section explaining more about what is considered a missing
    branch and how it is reported: :ref:branch_explain, as requested in issue 1597. Thanks to Ayisha Mohammed <pull 2092_>.

  • Tests: the test suite misunderstood what core was being tested if
    COVERAGE_CORE wasn't set on 3.14+. This is now fixed, closing issue 2109_.

.. _issue 1597: #​1597
.. _pull 2092: #​2092
.. _issue 2105: #​2105
.. _issue 2109: #​2109
.. _issue 2110: #​2110

.. _changes_7-13-0:

v7.13.0

Compare Source

  • Feature: coverage.py now supports :file:.coveragerc.toml configuration
    files. These files use TOML syntax and take priority over
    :file:pyproject.toml but lower priority than :file:.coveragerc files.
    Closes issue 1643_ thanks to Olena Yefymenko <pull 1952_>_.

  • Fix: we now include a permanent .pth file which is installed with the code,
    fixing issue 2084. In 7.12.1b1 this was done incorrectly: it didn't work
    when using the source wheel (py3-none-any). This is now fixed. Thanks,
    Henry Schreiner <pull 2100_>    .

  • Deprecated: when coverage.py is installed, it creates three command entry
    points: coverage, coverage3, and coverage-3.10 (if installed for
    Python 3.10). The second and third of these are not needed and will
    eventually be removed. They still work for now, but print a message about
    their deprecation.

.. _issue 1643: #​1643
.. _pull 1952: #​1952
.. _pull 2100: #​2100

.. _changes_7-12-1b1:

python/mypy (mypy)

v1.20.2

Compare Source

v1.20.1

Compare Source

  • Always disable sync in SQLite cache (Ivan Levkivskyi, PR 21184)
  • Temporarily skip few base64 tests (Ivan Levkivskyi, PR 21193)
  • Revert dict.__or__ typeshed change (Ivan Levkivskyi, PR 21186)
  • Fix narrowing for match case with variadic tuples (Shantanu, PR 21192)
  • Avoid narrowing type[T] in type calls (Shantanu, PR 21174)
  • Fix regression for catching empty tuple in except (Shantanu, PR 21153)
  • Fix reachability for frozenset and dict view narrowing (Shantanu, PR 21151)
  • Fix narrowing with chained comparison (Shantanu, PR 21150)
  • Avoid narrowing to unreachable at module level (Shantanu, PR 21144)
  • Allow dangerous identity comparisons to Any typed variables (Shantanu, PR 21142)
  • --warn-unused-config should not be a strict flag (Ivan Levkivskyi, PR 21139)

v1.20.0

Compare Source

v1.19.1

Compare Source

  • Fix noncommutative joins with bounded TypeVars (Shantanu, PR 20345)
  • Respect output format for cached runs by serializing raw errors in cache metas (Ivan Levkivskyi, PR 20372)
  • Allow types.NoneType in match cases (A5rocks, PR 20383)
  • Fix mypyc generator regression with empty tuple (BobTheBuidler, PR 20371)
  • Fix crash involving Unpack-ed TypeVarTuple (Shantanu, PR 20323)
  • Fix crash on star import of redefinition (Ivan Levkivskyi, PR 20333)
  • Fix crash on typevar with forward ref used in other module (Ivan Levkivskyi, PR 20334)
  • Fail with an explicit error on PyPy (Ivan Levkivskyi, PR 20389)
sdispater/pendulum (pendulum)

v3.2.0

Compare Source

Added
  • Added support for Python 3.14 #​923
  • Added upper limit to time-machine dependency #​931
Changed
  • Dropped support for PyPy below PyPy3.11 #​937
  • Optimize usage of re. methods #​741
  • Fixed pendulum.parse not being marked as exported #​693
  • Fixed pendulum.parse('now', tz='...') ignoring the timezone #​701
  • Use pathlib to read Unix TZ data #​742
  • Fixed Interval deepcopying #​850
  • Fixed typo in end_of('century') docs #​910
  • Bumped PyO3 to 0.27 #​922
  • Fixed incorrect date offset calculation in Rust extensions #​918
  • Changed locales and pytest to be lazy loaded #​926
  • Fixed error of Duration deepcopy not including weeks #​933
  • Fixed empty Durations not being an error in Python ISO8601 parser implementation #​903
  • Fixed parsing invalid interval string #​860
  • Fixed pluralization bug in Duration.in_words() #​826
Locales
Removed
  • Removed dependency on pytz #​911
pre-commit/pre-commit (pre-commit)

v4.6.0

Compare Source

==================

Features
  • pre-commit hook-impl: allow --hook-dir to be missing to enable easier
    usage with git 2.54+ git hooks.
Fixes

v4.5.1

Compare Source

==================

Fixes
  • Fix language: python with repo: local without additional_dependencies.
pytest-dev/pytest-asyncio (pytest-asyncio)

v1.4.0: pytest-asyncio v1.4.0

Compare Source

1.4.0 - 2026-05-26

Deprecated

  • Overriding the event_loop_policy fixture is deprecated. Use the pytest_asyncio_loop_factories hook instead. (#​1419)

Added

  • Added the pytest_asyncio_loop_factories hook to parametrize asyncio tests with custom event loop factories.

    The hook returns a mapping of factory names to loop factories, and pytest.mark.asyncio(loop_factories=[...]) selects a subset of configured factories per test. When a single factory is configured, test names are unchanged.

    Synchronous @pytest_asyncio.fixture functions now see the correct event loop when custom loop factories are configured, even when test code disrupts the current event loop (e.g., via asyncio.run() or asyncio.set_event_loop(None)). (#​1164)

Changed

  • Improved the readability of the warning message that is displayed when asyncio_default_fixture_loop_scope is unset (#​1298)
  • Only import asyncio.AbstractEventLoopPolicy for type checking to avoid raising
    a DeprecationWarning. (#​1394)
  • Updated minimum supported pytest version to v8.4.0. (#​1397)

Fixed

  • Fixed a ResourceWarning: unclosed event loop warning that could occur when a synchronous test called asyncio.run() or otherwise unset the current event loop after pytest-asyncio had run an async test or fixture. (#​724)

Notes for Downstream Packagers

  • Added dependency on sphinx-tabs >= 3.5 to organize documentation examples into tabs. (#​1395)
pytest-dev/pytest-cov (pytest-cov)

v7.1.0

Compare Source

  • Fixed total coverage computation to always be consistent, regardless of reporting settings.
    Previously some reports could produce different total counts, and consequently can make --cov-fail-under behave different depending on
    reporting options.
    See #&#8203;641 <https://github.com/pytest-dev/pytest-cov/issues/641>_.

  • Improve handling of ResourceWarning from sqlite3.

    The plugin adds warning filter for sqlite3 ResourceWarning unclosed database (since 6.2.0).
    It checks if there is already existing plugin for this message by comparing filter regular expression.
    When filter is specified on command line the message is escaped and does not match an expected message.
    A check for an escaped regular expression is added to handle this case.

    With this fix one can suppress ResourceWarning from sqlite3 from command line::

    pytest -W "ignore:unclosed database in <sqlite3.Connection object at:ResourceWarning" ...

  • Various improvements to documentation.
    Contributed by Art Pelling in #&#8203;718 <https://github.com/pytest-dev/pytest-cov/pull/718>_ and
    "vivodi" in #&#8203;738 <https://github.com/pytest-dev/pytest-cov/pull/738>.
    Also closed #&#8203;736 <https://github.com/pytest-dev/pytest-cov/issues/736>    .

  • Fixed some assertions in tests.
    Contributed by in Markéta Machová in #&#8203;722 <https://github.com/pytest-dev/pytest-cov/pull/722>_.

  • Removed unnecessary coverage configuration copying (meant as a backup because reporting commands had configuration side-effects before coverage 5.0).

astral-sh/ruff (ruff)

v0.15.16

Compare Source

Released on 2026-06-04.

Preview features
  • [flake8-async] Implement yield-in-context-manager-in-async-generator (ASYNC119) (#​24644)
  • [pylint] Narrow diagnostic range and exclude cases without exception handlers (PLW0717) (#​25440)
  • [ruff] Treat yield before break from a terminal loop as terminal (RUF075) (#​25447)
Bug fixes
  • [eradicate] Avoid flagging ruff:ignore comments as code (ERA001) (#​25537)
  • [eradicate] Fix ERA001/RUF100 conflict when noqa is on commented-out code (#​25414)
  • [pyflakes] Avoid removing the format call when it would change behavior (F523) (#​25320)
  • [pylint] Avoid syntax errors in invalid character replacements in f-strings before Python 3.12 (PLE2510, PLE2512, PLE2513, PLE2514, PLE2515) (#​25544)
  • [pyupgrade] Avoid converting format calls with more kinds of side effects (UP032) (#​25484)
Rule changes
  • [flake8-pytest-style] Avoid fixes for ambiguous argnames and argvalues combinations (PT006) (#​24776)
Performance
  • Drop excess capacity from statement suites during parsing (#​25368)
Documentation
  • [pydocstyle] Improve discoverability of rules enabled for each convention (#​24973)
  • [ruff] Restore example code for Python versions before 3.15 (RUF017) (#​25439)
  • Fix typo bin/active → bin/activate in tutorial (#​25473)
Other changes
  • Shrink additional parser AST collections (#​25465)
Contributors

v0.15.15

Compare Source

Released on 2026-05-28.

Preview features
  • Fix Markdown closing fence handling (#​25310)
  • [pyflakes] Report duplicate imports in typing.TYPE_CHECKING block (F811) (#​22560)
Bug fixes
  • [pyflakes] Treat function-scope bare annotations as locals per PEP 526 (F821) (#​21540)
Performance
  • Avoid redundant TokenValue drops in the lexer (#​25300)
  • Reduce memory usage by dropping token-excess capacity and improve performance by approximating the initial tokens Vec size (#​25354)
  • Use ThinVec in AST to shrink Stmt (#​25361)
Documentation
  • Fix line-length example for --config option (#​25389)
  • [flake8-comprehensions] Document RecursionError edge case in __len__ (C416) (#​25286)
  • [mccabe] Improve example (C901) (#​25287)
  • [pyupgrade] Clarify fix safety docs (UP007, UP045) (#​25288)
  • [refurb] Document FURB192 exception change for empty sequences (#​25317)
  • [ruff] Document false negative for user-defined types (RUF013) (#​25289)
Formatter
  • Fix formatting of lambdas nested within f-strings (#​25398)
Server
  • Return code action for codeAction/resolve requests that contain no or no valid URL (#​25365)
Other changes
  • Expand semantic syntax errors for invalid walruses (#​25415)
Contributors

v0.15.14

Compare Source

Released on 2026-05-21.

Preview features
  • [airflow] Implement airflow-task-implicit-multiple-outputs (AIR202) (#​25152)
  • [flake8-use-pathlib] Mark PTH101 fix as unsafe when first argument is a class attribute annotated as int (#​25086)
  • [pylint] Implement too-many-try-statements (W0717) (#​23970)
  • [ruff] Add incorrect-decorator-order (RUF074) (#​23461)
  • [ruff] Add fallible-context-manager (RUF075) (#​22844)
Bug fixes
  • Fix lambda formatting in interpolated string expressions (#​25144)
  • Treat generic frozenset annotations as immutable (#​25251)
  • [flake8-type-checking] Avoid strict behavior when future-annotations are enabled (TC001, TC002, TC003) (#​25035)
  • [pylint] Avoid false positives in else clause (PLR1733) (#​25177)
Rule changes
  • [flake8-comprehensions] Skip C417 for lambdas with positional-only parameters (#​25272)
  • [flake8-simplify] Preserve f-string source verbatim in SIM101 fix (#​25061)
Performance
  • Avoid unnecessary parser lookahead for operators (#​25290)
Documentation
  • Update code example setting Neovim LSP log level (#​25284)
Other changes
Contributors

v0.15.13

Compare Source

Released on 2026-05-14.

Preview features
  • Add a rule to flag lazy imports that are eagerly evaluated (#​25016)
  • [pylint] Standardize diagnostic message (PLR0914, PLR0917) (#​24996)
Bug fixes
  • Fix F811 false positive for class methods (#​24933)
  • Fix setting selection for multi-folder workspace (#​24819)
  • [eradicate] Fix false positive for lines with leading whitespace (ERA001) (#​25122)
  • [flake8-pyi] Fix false positive for f-string debug specifier (PYI016) (#​24098)
Rule changes
  • Always include panic payload in panic diagnostic message (#​24873)
  • Restrict PYI034 for in-place operations to enclosing class (#​24511)
  • Improve error message for parameters that are declared global (#​24902)
  • Update known stdlib (#​25103)
Performance
  • [isort] Avoid constructing glob::Patterns for literal known modules (#​25123)
CLI
  • Add TOML examples to --config help text (#​25013)
  • Colorize ruff check 'All checks passed' (#​25085)
Configuration
  • Increase max allowed value of line-length setting (#​24962)
Documentation
  • Add D203 to rules that conflict with the formatter (#​25044)
  • Clarify COM819 and formatter interaction (#​25045)
  • Clarify that NotImplemented is a value, not an exception (F901) (#​25054)
  • Update number of lint rules supported (#​24942)
Other changes
  • Simplify the playground's markdown template (#​24924)
Contributors

v0.15.12

Compare Source

Released on 2026-04-24.

Preview features

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (in timezone America/Chicago)

  • Branch creation
    • Between 12:00 AM and 03:59 AM (* 0-3 * * *)
  • Automerge
    • At any time (no schedule defined)

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

♻ Rebasing: Whenever PR becomes conflicted, 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.

@codecov

codecov Bot commented Dec 10, 2025 •
edited
Loading

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 65.99%. Comparing base (eeb24a6) to head (c6421d7).

Additional details and impacted files 
@@           Coverage Diff           @@
##           master     #855   +/-   ##
=======================================
  Coverage   65.99%   65.99%           
=======================================
  Files          46       46           
  Lines        2926     2926           
  Branches      342      342           
=======================================
  Hits         1931     1931           
  Misses        954      954           
  Partials       41       41

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@renovate renovate Bot force-pushed the renovate/dev-dependencies branch from 84773ad to d31981a Compare December 10, 2025 14:32
@renovate renovate Bot changed the title chore: update dependency coverage to v7.13.0 chore: update dev dependencies (non-major) Dec 10, 2025
@renovate renovate Bot changed the title chore: update dev dependencies (non-major) chore(dev): update dev dependencies (non-major) Dec 11, 2025
@renovate renovate Bot force-pushed the renovate/dev-dependencies branch 4 times, most recently from afa5605 to f0eba7e Compare December 18, 2025 02:12
@renovate renovate Bot force-pushed the renovate/dev-dependencies branch 2 times, most recently from 49af733 to a0a7334 Compare December 24, 2025 05:55
@renovate renovate Bot force-pushed the renovate/dev-dependencies branch 2 times, most recently from 9a48be8 to 21c3ff5 Compare January 5, 2026 11:01
@renovate renovate Bot force-pushed the renovate/dev-dependencies branch 2 times, most recently from b5f4607 to 215613e Compare January 9, 2026 21:15
@renovate renovate Bot force-pushed the renovate/dev-dependencies branch 2 times, most recently from 88dd1b6 to 9050e10 Compare January 16, 2026 21:04
@renovate renovate Bot force-pushed the renovate/dev-dependencies branch 3 times, most recently from e13c00b to c6421d7 Compare January 26, 2026 13:40
@renovate renovate Bot force-pushed the renovate/dev-dependencies branch from c6421d7 to 654c64d Compare January 31, 2026 12:25
@renovate

renovate Bot commented Jan 31, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor Author

⚠️ 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...


Because botus-receptus[sqlalchemy,uvloop] (25.6.1) @ git+https://github.com/bryanforbes/botus_receptus.git@v25.6.1 depends on pendulum (~3.1.0)
 and pendulum[test] (3.2.0) depends on pendulum (3.2.0), botus-receptus[sqlalchemy,uvloop] (25.6.1) @ git+https://github.com/bryanforbes/botus_receptus.git@v25.6.1 is incompatible with pendulum[test] (3.2.0).
So, because erasmus depends on both botus_receptus[sqlalchemy,uvloop] (25.6.1) @ git+https://github.com/bryanforbes/botus_receptus.git@v25.6.1 and pendulum[test] (3.2.0), version solving failed.

@renovate renovate Bot force-pushed the renovate/dev-dependencies branch 4 times, most recently from 6c6b72a to c2ffc3d Compare February 5, 2026 05:34
@renovate renovate Bot force-pushed the renovate/dev-dependencies branch 2 times, most recently from 084d59e to d8df259 Compare March 6, 2026 21:40
@renovate renovate Bot force-pushed the renovate/dev-dependencies branch 2 times, most recently from dbffc90 to adcab1a Compare March 18, 2026 14:09
@renovate renovate Bot force-pushed the renovate/dev-dependencies branch 3 times, most recently from 41ab64b to 4c86be9 Compare April 3, 2026 21:42
@renovate renovate Bot force-pushed the renovate/dev-dependencies branch 3 times, most recently from 09a88fe to a073de9 Compare April 17, 2026 15:55
@renovate renovate Bot force-pushed the renovate/dev-dependencies branch 5 times, most recently from 9633609 to 5f41395 Compare April 22, 2026 23:03
@renovate renovate Bot force-pushed the renovate/dev-dependencies branch from 5f41395 to 0068299 Compare April 25, 2026 20:38
@renovate renovate Bot force-pushed the renovate/dev-dependencies branch 5 times, most recently from 38b91d4 to 0af2848 Compare May 15, 2026 17:50
@renovate renovate Bot force-pushed the renovate/dev-dependencies branch 3 times, most recently from 73eb465 to cfc8c6b Compare May 25, 2026 08:34
@renovate renovate Bot force-pushed the renovate/dev-dependencies branch 3 times, most recently from 3ae0849 to adb7b11 Compare May 29, 2026 19:00
@renovate renovate Bot force-pushed the renovate/dev-dependencies branch 5 times, most recently from 6e29457 to ec9c4b1 Compare June 6, 2026 02:35
@renovate renovate Bot force-pushed the renovate/dev-dependencies branch from ec9c4b1 to 56694a6 Compare June 8, 2026 17:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

@bryanforbes bryanforbes

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@bryanforbes