Skip to content

Bump coverage[toml] from 5.3 to 6.1.1#128

Closed
dependabot[bot] wants to merge 1 commit intomasterfrom
dependabot/pip/coverage-toml--6.1.1
Closed

Bump coverage[toml] from 5.3 to 6.1.1#128
dependabot[bot] wants to merge 1 commit intomasterfrom
dependabot/pip/coverage-toml--6.1.1

Conversation

@dependabot
Copy link
Copy Markdown

@dependabot dependabot Bot commented on behalf of github Nov 3, 2021

Bumps coverage[toml] from 5.3 to 6.1.1.

Release notes

Sourced from coverage[toml]'s releases.

6.1.1

  • Fix: The sticky header on the HTML report didn’t work unless you had branch coverage enabled. This is now fixed: the sticky header works for everyone. (Do people still use coverage without branch measurement!? j/k)
  • Fix: When using explicitly declared namespace packages, the “already imported a file that will be measured” warning would be issued (issue 888). This is now fixed.

6.1

  • Deprecated: The annotate command and the Coverage.annotate function will be removed in a future version, unless people let me know that they are using it. Instead, the html command gives better-looking (and more accurate) output, and the report -m command will tell you line numbers of missing lines. Please get in touch if you have a reason to use annotate over those better options: https://github.com/nedbat/coveragepy/blob/HEAD/mailto:ned@nedbatchelder.com.
  • Feature: Coverage now sets an environment variable, COVERAGE_RUN when running your code with the coverage run command. The value is not important, and may change in the future. Closes issue 553.
  • Feature: The HTML report pages for Python source files now have a sticky header so the file name and controls are always visible.
  • Feature: The xml and json commands now describe what they wrote where.
  • Feature: The html, combine, xml, and json commands all accept a -q/--quiet option to suppress the messages they write to stdout about what they are doing (issue 1254).
  • Feature: The html command writes a .gitignore file into the HTML output directory, to prevent the report from being committed to git. If you want to commit it, you will need to delete that file. Closes issue 1244.
  • Feature: Added support for PyPy 3.8.
  • Fix: More generated code is now excluded from measurement. Code such as attrs boilerplate, or doctest code, was being measured though the synthetic line numbers meant they were never reported. Once Cython was involved though, the generated .so files were parsed as Python, raising syntax errors, as reported in issue 1160. This is now fixed.
  • Fix: When sorting human-readable names, numeric components are sorted correctly: file10.py will appear after file9.py. This applies to file names, module names, environment variables, and test contexts.
  • Performance: Branch coverage measurement is faster, though you might only notice on code that is executed many times, such as long-running loops.
  • Build: jQuery is no longer used or vendored (issue 840 and issue 1118). Huge thanks to Nils Kattenbeck (septatrix) for the conversion to vanilla JavaScript in pull request 1248.

6.0.2

6.0.1

  • In 6.0, the coverage.py exceptions moved from coverage.misc to coverage.exceptions. These exceptions are not part of the public supported API, CoverageException is. But a number of other third-party packages were importing the exceptions from coverage.misc, so they are now available from there again (issue 1226).
  • Changed an internal detail of how tomli is imported, so that tomli can use coverage.py for their own test suite (issue 1228).
  • Defend against an obscure possibility under code obfuscation, where a function can have an argument called “self”, but no local named “self” (pull request 1210). Thanks, Ben Carlsson.

6.0

  • The coverage html command now prints a message indicating where the HTML report was written. Fixes issue 1195.
  • The coverage combine command now prints messages indicating each data file being combined. Fixes issue 1105.
  • The HTML report now includes a sentence about skipped files due to skip_covered or skip_empty settings. Fixes issue 1163.
  • Unrecognized options in the configuration file are no longer errors. They are now warnings, to ease the use of coverage across versions. Fixes issue 1035.
  • Fix handling of exceptions through context managers in Python 3.10. A missing exception is no longer considered a missing branch from the with statement. Fixes issue 1205.
  • Fix another rarer instance of “Error binding parameter 0 - probably unsupported type.” (issue 1010).
  • Creating a directory for the coverage data file now is safer against conflicts when two coverage runs happen simultaneously (pull 1220). Thanks, Clément Pit-Claudel.

6.0b1

  • Dropped support for Python 2.7, PyPy 2, and Python 3.5.
  • Added support for the Python 3.10 match/case syntax.
  • Data collection is now thread-safe. There may have been rare instances of exceptions raised in multi-threaded programs.
  • Plugins (like the Django coverage plugin) were generating “Already imported a file that will be measured” warnings about Django itself. These have been fixed, closing issue 1150.
  • Warnings generated by coverage.py are now real Python warnings.
  • Using --fail-under=100 with coverage near 100% could result in the self-contradictory message total of 100 is less than fail-under=100. This bug (issue 1168) is now fixed.
  • The COVERAGE_DEBUG_FILE environment variable now accepts stdout and stderr to write to those destinations.
  • TOML parsing now uses the tomli library.
  • Some minor changes to usually invisible details of the HTML report:
    • Use a modern hash algorithm when fingerprinting, for high-security environments (issue 1189). When generating the HTML report, we save the hash of the data, to avoid regenerating an unchanged HTML page. We used to use MD5 to generate the hash, and now use SHA-3-256. This was never a security concern, but security scanners would notice the MD5 algorithm and raise a false alarm.
    • Change how report file names are generated, to avoid leading underscores (issue 1167), to avoid rare file name collisions (issue 584), and to avoid file names becoming too long (issue 580).

coverage-5.6b1

... (truncated)

Changelog

Sourced from coverage[toml]'s changelog.

Version 6.1.1 — 2021-10-31

  • Fix: The sticky header on the HTML report didn't work unless you had branch coverage enabled. This is now fixed: the sticky header works for everyone. (Do people still use coverage without branch measurement!? j/k)

  • Fix: When using explicitly declared namespace packages, the "already imported a file that will be measured" warning would be issued (issue 888_). This is now fixed.

.. _issue 888: nedbat/coveragepy#888

.. _changes_61:

Version 6.1 — 2021-10-30

  • Deprecated: The annotate command and the Coverage.annotate function will be removed in a future version, unless people let me know that they are using it. Instead, the html command gives better-looking (and more accurate) output, and the report -m command will tell you line numbers of missing lines. Please get in touch if you have a reason to use annotate over those better options: ned@nedbatchelder.com.

  • Feature: Coverage now sets an environment variable, COVERAGE_RUN when running your code with the coverage run command. The value is not important, and may change in the future. Closes issue 553_.

  • Feature: The HTML report pages for Python source files now have a sticky header so the file name and controls are always visible.

  • Feature: The xml and json commands now describe what they wrote where.

  • Feature: The html, combine, xml, and json commands all accept a -q/--quiet option to suppress the messages they write to stdout about what they are doing (issue 1254_).

  • Feature: The html command writes a .gitignore file into the HTML output directory, to prevent the report from being committed to git. If you want to commit it, you will need to delete that file. Closes issue 1244_.

  • Feature: Added support for PyPy 3.8.

  • Fix: More generated code is now excluded from measurement. Code such as attrs_ boilerplate, or doctest code, was being measured though the synthetic line numbers meant they were never reported. Once Cython was involved though, the generated .so files were parsed as Python, raising

... (truncated)

Commits
  • ff59658 docs: sample HTML report for 6.1.1
  • 7957d0a build: prep for 6.1.1
  • 4a772b5 perf(test): run pip just once, shaves 1.2s off the fixture
  • adff230 test: use the coverage-command fixture throughout the venv tests
  • 1a6844a fix: don't warn about already imported files for namespace packages #888
  • 7589066 refactor(test): the virtualenv tests deserve their own file
  • 3b7f8c1 test: check pylint for new files before adding them to git
  • 56713f2 docs: another link for the no-jquery changelog entry
  • bb78d7e test: when we measure our coverage, get a json report also
  • 79f832f build: clean up the Makefile a bit
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [coverage[toml]](https://github.com/nedbat/coveragepy) from 5.3 to 6.1.1.
- [Release notes](https://github.com/nedbat/coveragepy/releases)
- [Changelog](https://github.com/nedbat/coveragepy/blob/master/CHANGES.rst)
- [Commits](coveragepy/coveragepy@coverage-5.3...6.1.1)

---
updated-dependencies:
- dependency-name: coverage[toml]
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Nov 3, 2021
@dependabot @github
Copy link
Copy Markdown
Author

dependabot Bot commented on behalf of github Nov 17, 2021

Superseded by #142.

@dependabot dependabot Bot closed this Nov 17, 2021
@dependabot dependabot Bot deleted the dependabot/pip/coverage-toml--6.1.1 branch November 17, 2021 19:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants