search

opennaslab / kubespider

A global resource download orchestration system, build your home download center.
https://kubespider.netlify.app/
Apache License 2.0
2.05k stars 118 forks source link

chore(deps): update dependency coverage to v7.3.3 #395

Closed renovate[bot] closed 10 months ago

renovate[bot] commented 10 months ago

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
coverage ==7.3.0 -> ==7.3.3 age adoption passing confidence

Release Notes

nedbat/coveragepy (coverage) ### [`v7.3.3`](https://togithub.com/nedbat/coveragepy/blob/HEAD/CHANGES.rst#Version-733--2023-12-14) [Compare Source](https://togithub.com/nedbat/coveragepy/compare/7.3.2...7.3.3) - Fix: function definitions with multi-line signatures can now be excluded by matching any of the lines, closing `issue 684`*. Thanks, `Jan Rusak, Maciej Kowalczyk and Joanna Ejzel `*. - Fix: XML reports could fail with a TypeError if files had numeric components that were duplicates except for leading zeroes, like `file1.py` and `file001.py`. Fixes `issue 1709`\_. - The `coverage annotate` command used to announce that it would be removed in a future version. Enough people got in touch to say that they use it, so it will stay. Don't expect it to keep up with other new features though. - Added new :ref:`debug options `: - `pytest` writes the pytest test name into the debug output. - `dataop2` writes the full data being added to CoverageData objects. .. \_issue 684:[https://github.com/nedbat/coveragepy/issues/684](https://togithub.com/nedbat/coveragepy/issues/684)4 .. \_pull 1705[https://github.com/nedbat/coveragepy/pull/1705](https://togithub.com/nedbat/coveragepy/pull/1705)05 .. \_issue 170[https://github.com/nedbat/coveragepy/issues/1709](https://togithub.com/nedbat/coveragepy/issues/1709)709 .. \_changes\_7-3-2: ### [`v7.3.2`](https://togithub.com/nedbat/coveragepy/blob/HEAD/CHANGES.rst#Version-732--2023-10-02) [Compare Source](https://togithub.com/nedbat/coveragepy/compare/7.3.1...7.3.2) - The `coverage lcov` command ignored the `[report] exclude_lines` and `[report] exclude_also` settings (`issue 1684`*). This is now fixed, thanks `Jacqueline Lee `*. - Sometimes SQLite will create journal files alongside the coverage.py database files. These are ephemeral, but could be mistakenly included when combining data files. Now they are always ignored, fixing `issue 1605`\_. Thanks to Brad Smith for suggesting fixes and providing detailed debugging. - On Python 3.12+, we now disable SQLite writing journal files, which should be a little faster. - The new 3.12 soft keyword `type` is properly bolded in HTML reports. - Removed the "fullcoverage" feature used by CPython to measure the coverage of early-imported standard library modules. CPython `stopped using it <88054_>`\_ in 2021, and it stopped working completely in Python 3.13. .. \_issue 1605:[https://github.com/nedbat/coveragepy/issues/1605](https://togithub.com/nedbat/coveragepy/issues/1605)5 .. \_issue 1684[https://github.com/nedbat/coveragepy/issues/1684](https://togithub.com/nedbat/coveragepy/issues/1684)84 .. \_pull 168[https://github.com/nedbat/coveragepy/pull/1685](https://togithub.com/nedbat/coveragepy/pull/1685)685 .. \_880[https://github.com/python/cpython/issues/88054](https://togithub.com/python/cpython/issues/88054)8054 .. \_changes\_7-3-1: ### [`v7.3.1`](https://togithub.com/nedbat/coveragepy/blob/HEAD/CHANGES.rst#Version-731--2023-09-06) [Compare Source](https://togithub.com/nedbat/coveragepy/compare/7.3.0...7.3.1) - The semantics of stars in file patterns has been clarified in the docs. A leading or trailing star matches any number of path components, like a double star would. This is different than the behavior of a star in the middle of a pattern. This discrepancy was `identified by Sviatoslav Sydorenko `*, who `provided patient detailed diagnosis `* and graciously agreed to a pragmatic resolution. - The API docs were missing from the last version. They are now `restored `\_. .. \_apidocs: https://coverage.readthedocs.io/en/latest/api_coverage.html .. \_starbad[https://github.com/nedbat/coveragepy/issues/1407#issuecomment-1631085209](https://togithub.com/nedbat/coveragepy/issues/1407#issuecomment-1631085209)09 .. \_pull 165[https://github.com/nedbat/coveragepy/pull/1650](https://togithub.com/nedbat/coveragepy/pull/1650)650 .. \_changes\_7-3-0:

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 becomes conflicted, or you tick the rebase/retry checkbox.

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

This PR has been generated by Mend Renovate. View repository job log here.

richardli1598 commented 10 months ago

Hello, I am a code review bot on flows.network. Here are my reviews of changed source code files in this PR.

The patch updates the coverage dependency from version 7.3.0 to 7.3.3 in the requirements.txt file. Below are the areas requiring attention:

  1. Dependency Compatibility: Ensure that the new version of coverage is compatible with the versions of other packages and the codebase. It is important to check for any breaking changes or deprecations in the coverage library that might affect the project.

  2. Testing: After the dependency update, it would be necessary to run the full test suite to make certain that the update does not introduce any regressions or new issues.

  3. Changelog Review: Review the changelog or release notes of coverage version 7.3.3 to understand what has been changed, fixed, or improved. This can help identify potential areas of concern within the application that may be affected.

  4. Version Pinning: The version has been pinned to an exact version (7.3.3). While this is good for reproducibility, it's worth considering if a flexible versioning strategy (e.g., using >=7.3.3,<7.4.0 for semantic versioning) might be more appropriate to automatically receive patches while avoiding potential breaking changes.

  5. Documentation: If there is internal documentation referencing the dependency versions, it needs to be updated to reflect the change in the version of coverage.

No changes are required in the patch itself, as it directly achieves the intended purpose of updating the coverage dependency version. The patch is minimal and correct in syntax.

Make sure that these considerations are addressed before merging the patch to maintain the stability and integrity of the project.

netlify[bot] commented 10 months ago

Deploy Preview for kubespider ready!

Name Link
Latest commit eb02e98d21c82bce863ff61bac7010cd1010dbfe
Latest deploy log https://app.netlify.com/sites/kubespider/deploys/65815ebff3eac100083d9c3f
Deploy Preview https://deploy-preview-395--kubespider.netlify.app
Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

renovate[bot] commented 10 months ago

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (==7.3.3). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.