fix(deps): update all dependencies#198
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
Contributor
☂️ Python Coverage
Overall Coverage
New FilesNo new covered files... Modified FilesNo covered modified files...
|
27eeeaa to
af48d23
Compare
1ca8f16 to
5ec3aa0
Compare
9754097 to
abb2d23
Compare
424462b to
02c487b
Compare
02c487b to
8213346
Compare
Contributor
☂️ Code Coverage
Overall Coverage
New FilesNo new covered files... Modified FilesNo covered modified files...
|
f2fdbc4 to
e32c9b5
Compare
e32c9b5 to
deeb81f
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v4→v5.0.0v4→v5^1.2→^2.0.0v3.2→v3.34.5.1→4.6.0v1.19.1→v2.1.0v4.5.1→v4.6.026.3.0→26.3.17.0.0→7.1.0Note: The
pre-commitmanager in Renovate is not supported by thepre-commitmaintainers or community. Please do not report any problems there, instead create a Discussion in the Renovate repository if you have any questions.Release Notes
actions/dependency-review-action (actions/dependency-review-action)
v5.0.0: 5.0.0Compare Source
This is a new major version of the Dependency Review Action which updates the runtime to node24. This requires a minimum Actions Runner version v2.327.1 to run.
What's Changed
New Contributors
Full Changelog: actions/dependency-review-action@v4.9.0...v5.0.0
googleapis/release-please-action (googleapis/release-please-action)
v5.0.0Compare Source
⚠ BREAKING CHANGES
Features
Bug Fixes
v5.0Compare Source
v5Compare Source
v4.4.1Compare Source
v4.4.0Compare Source
Features
Bug Fixes
changelog-hostparameter ignored when using manifest configuration (#1151) (535c413)v4.4Compare Source
v4.3.0Compare Source
Features
v4.3Compare Source
v4.2.0Compare Source
Features
v4.2Compare Source
v4.1.5Compare Source
Bug Fixes
v4.1.4Compare Source
Bug Fixes
v4.1.3Compare Source
Bug Fixes
v4.1.2Compare Source
Bug Fixes
v4.1.1Compare Source
Bug Fixes
v4.1.0Compare Source
Features
changelog-hostinput toaction.yml(#948) (863b06f)v4.1Compare Source
v4.0.3Compare Source
Bug Fixes
v4.0.2Compare Source
Bug Fixes
v4.0.1Compare Source
Bug Fixes
python/mypy (mypy)
v2.1.0Compare Source
v2.0.0Compare Source
v1.20.2Compare Source
v1.20.1Compare Source
dict.__or__typeshed change (Ivan Levkivskyi, PR 21186)type[T]in type calls (Shantanu, PR 21174)Anytyped variables (Shantanu, PR 21142)--warn-unused-configshould not be a strict flag (Ivan Levkivskyi, PR 21139)v1.20.0Compare Source
orgoro/coverage (orgoro/coverage)
v3.3.1: — renamed files counted as modifiedCompare Source
Fix
compareCommitswas only counting files with statusaddedormodified. The GitHub compare API also returnsrenamedfor git rename detection — those files were silently dropped, so refactor PRs that rename files lost coverage tracking on them. Now renamed files are included as modified. (#350, originally proposed in #325 by @mangunowsky)Full changelog: orgoro/coverage@v3.3...v3.3.1
v3.3: — node24 runtime, configurable title, docsCompare Source
Runtime
node20tonode24^5.4,@types/node ^24,jest/ts-jest ^29Features
titleinput — heading text for the PR comment. Default changed fromPython CoveragetoCode Coveragesince the action works for any language producing cobertura xml. Setting a unique value per matrix entry (e.g.Python Coverage 3.10,Python Coverage 3.11) posts separate comments instead of overwriting one shared one. Closes #328, #320.Docs
contents: read,pull-requests: write). Closes #310.Fixes
Lines→Statementsto matchcoverage.pyterminology. Closes #250.The default
titlechanged fromPython CoveragetoCode Coverage. The first post-upgrade run will create a new comment instead of updating the existingPython Coverageone (the old comment becomes orphaned on each open PR). To preserve the old behavior, pin the title:Full changelog: orgoro/coverage@v3.2...v3.3
pre-commit/pre-commit (pre-commit)
v4.6.0Compare Source
==================
Features
pre-commit hook-impl: allow--hook-dirto be missing to enable easierusage with
git2.54+ git hooks.Fixes
pre-commit hook-impl:--hook-typeis required.pre-commit/mirrors-mypy (pre-commit/mirrors-mypy)
v2.1.0Compare Source
v2.0.0Compare Source
v1.20.2Compare Source
v1.20.1Compare Source
v1.20.0Compare Source
psf/black (psf/black)
v26.3.1Compare Source
Stable style
exact-length placeholders for short magics and aborting if a placeholder can no longer
be unmasked safely (#5038)
Configuration
--python-cell-magicsso custommagic names cannot affect cache paths (#5038)
Blackd
and request body limits, and bound executor submissions to improve backpressure
(#5039)
pytest-dev/pytest-cov (pytest-cov)
v7.1.0Compare 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
#​641 <https://github.com/pytest-dev/pytest-cov/issues/641>_.Improve handling of ResourceWarning from sqlite3.
The plugin adds warning filter for sqlite3
ResourceWarningunclosed 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
ResourceWarningfrom sqlite3 from command line::pytest -W "ignore:unclosed database in <sqlite3.Connection object at:ResourceWarning" ...
Various improvements to documentation.
Contributed by Art Pelling in
#​718 <https://github.com/pytest-dev/pytest-cov/pull/718>_ and"vivodi" in
#​738 <https://github.com/pytest-dev/pytest-cov/pull/738>.Also closed
#​736 <https://github.com/pytest-dev/pytest-cov/issues/736>.Fixed some assertions in tests.
Contributed by in Markéta Machová in
#​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).
Configuration
📅 Schedule: (UTC)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.