Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps) Update all non-major dependencies #103

Open
wants to merge 1 commit into
base: dev
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 12, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update Pending
@semantic-release/github 10.0.3 -> 10.3.3 age adoption passing confidence devDependencies minor 10.3.4
@semantic-release/npm 12.0.0 -> 12.0.1 age adoption passing confidence devDependencies patch
asottile/pyupgrade v3.15.2 -> v3.17.0 age adoption passing confidence repository minor
black (changelog) 23.3.0 -> 23.12.1 age adoption passing confidence dev minor
coverage 7.2.7 -> 7.6.1 age adoption passing confidence dev minor
isort (source, changelog) 5.11.5 -> 5.13.2 age adoption passing confidence dev minor
macisamuele/language-formatters-pre-commit-hooks v2.13.0 -> v2.14.0 age adoption passing confidence repository minor
mypy (source, changelog) 1.4.1 -> 1.11.2 age adoption passing confidence dev minor
psf/black 24.1.1 -> 24.8.0 age adoption passing confidence repository minor
semantic-release 23.0.8 -> 23.1.1 age adoption passing confidence devDependencies minor
tox (changelog) 4.8.0 -> 4.19.0 age adoption passing confidence dev minor

Note: The pre-commit manager in Renovate is not supported by the pre-commit maintainers or community. Please do not report any problems there, instead create a Discussion in the Renovate repository if you have any questions.


Release Notes

semantic-release/github (@​semantic-release/github)

v10.3.3

Compare Source

Bug Fixes
  • Revert: feat: verify OAuth scopes of classic GitHub PATs (#​915) (990bd73)

v10.3.2

Compare Source

Bug Fixes
  • missing "PullRequest".canBeRebased field on GHES graphql api (#​913) (4393578)

v10.3.1

Compare Source

Bug Fixes
  • max_node_limit_exceeded error when fetching associatedPRs (#​912) (bb806af)

v10.3.0

Compare Source

Features
  • allow conditional skip on success and fail comments (#​874) (e097d1c)

v10.2.0

Compare Source

Features

v10.1.7

Compare Source

Bug Fixes

v10.1.6

Compare Source

v10.1.5

Compare Source

Bug Fixes

v10.1.4

Compare Source

Bug Fixes
  • docs: correct docs branch for fail-comment links (#​893) (b591730)

v10.1.3

Compare Source

Bug Fixes

v10.1.2

Compare Source

Bug Fixes

v10.1.1

Compare Source

Bug Fixes
  • invalid GraphQL query generated when no release commits are found (#​876) (8ee2744)

v10.1.0

Compare Source

Features

v10.0.7

Compare Source

Bug Fixes
  • replace github search api with graphql in success lifecycle method (#​857) (be394cf)

v10.0.6

Compare Source

Bug Fixes
  • corrected homepage link in package.json so the generated links in the errors are valid (#​848) (865762d)

v10.0.5

Compare Source

Bug Fixes

v10.0.4

Compare Source

Bug Fixes
  • introduce dedicated option for GitHub API endpoint (#​829) (908ff83)
semantic-release/npm (@​semantic-release/npm)

v12.0.1

Compare Source

Bug Fixes
  • deps: update dependency execa to v9 (9ac5ed0)
asottile/pyupgrade (asottile/pyupgrade)

v3.17.0

Compare Source

v3.16.0

Compare Source

psf/black (black)

v23.12.1

Compare Source

Packaging
  • Fixed a bug that included dependencies from the d extra by default (#​4108)

v23.12.0

Compare Source

Highlights

It's almost 2024, which means it's time for a new edition of Black's stable style!
Together with this release, we'll put out an alpha release 24.1a1 showcasing the draft
2024 stable style, which we'll finalize in the January release. Please try it out and
share your feedback.

This release (23.12.0) will still produce the 2023 style. Most but not all of the
changes in --preview mode will be in the 2024 stable style.

Stable style
  • Fix bug where # fmt: off automatically dedents when used with the --line-ranges
    option, even when it is not within the specified line range. (#​4084)
  • Fix feature detection for parenthesized context managers (#​4104)
Preview style
  • Prefer more equal signs before a break when splitting chained assignments (#​4010)
  • Standalone form feed characters at the module level are no longer removed (#​4021)
  • Additional cases of immediately nested tuples, lists, and dictionaries are now
    indented less (#​4012)
  • Allow empty lines at the beginning of all blocks, except immediately before a
    docstring (#​4060)
  • Fix crash in preview mode when using a short --line-length (#​4086)
  • Keep suites consisting of only an ellipsis on their own lines if they are not
    functions or class definitions (#​4066) (#​4103)
Configuration
  • --line-ranges now skips Black's internal stability check in --safe mode. This
    avoids a crash on rare inputs that have many unformatted same-content lines. (#​4034)
Packaging
Integrations

v23.11.0

Compare Source

Highlights
  • Support formatting ranges of lines with the new --line-ranges command-line option
    (#​4020)
Stable style
  • Fix crash on formatting bytes strings that look like docstrings (#​4003)
  • Fix crash when whitespace followed a backslash before newline in a docstring (#​4008)
  • Fix standalone comments inside complex blocks crashing Black (#​4016)
  • Fix crash on formatting code like await (a ** b) (#​3994)
  • No longer treat leading f-strings as docstrings. This matches Python's behaviour and
    fixes a crash (#​4019)
Preview style
  • Multiline dicts and lists that are the sole argument to a function are now indented
    less (#​3964)
  • Multiline unpacked dicts and lists as the sole argument to a function are now also
    indented less (#​3992)
  • In f-string debug expressions, quote types that are visible in the final string are
    now preserved (#​4005)
  • Fix a bug where long case blocks were not split into multiple lines. Also enable
    general trailing comma rules on case blocks (#​4024)
  • Keep requiring two empty lines between module-level docstring and first function or
    class definition (#​4028)
  • Add support for single-line format skip with other comments on the same line (#​3959)
Configuration
  • Consistently apply force exclusion logic before resolving symlinks (#​4015)
  • Fix a bug in the matching of absolute path names in --include (#​3976)
Performance
  • Fix mypyc builds on arm64 on macOS (#​4017)
Integrations
  • Black's pre-commit integration will now run only on git hooks appropriate for a code
    formatter (#​3940)

v23.10.1

Compare Source

Highlights
  • Maintenance release to get a fix out for GitHub Action edge case (#​3957)
Preview style
  • Fix merging implicit multiline strings that have inline comments (#​3956)
  • Allow empty first line after block open before a comment or compound statement (#​3967)
Packaging
  • Change Dockerfile to hatch + compile black (#​3965)
Integrations
  • The summary output for GitHub workflows is now suppressible using the summary
    parameter. (#​3958)
  • Fix the action failing when Black check doesn't pass (#​3957)
Documentation

v23.10.0

Compare Source

Stable style
  • Fix comments getting removed from inside parenthesized strings (#​3909)
Preview style
  • Fix long lines with power operators getting split before the line length (#​3942)
  • Long type hints are now wrapped in parentheses and properly indented when split across
    multiple lines (#​3899)
  • Magic trailing commas are now respected in return types. (#​3916)
  • Require one empty line after module-level docstrings. (#​3932)
  • Treat raw triple-quoted strings as docstrings (#​3947)
Configuration
  • Fix cache versioning logic when BLACK_CACHE_DIR is set (#​3937)
Parser
  • Fix bug where attributes named type were not acccepted inside match statements
    (#​3950)
  • Add support for PEP 695 type aliases containing lambdas and other unusual expressions
    (#​3949)
Output
  • Black no longer attempts to provide special errors for attempting to format Python 2
    code (#​3933)
  • Black will more consistently print stacktraces on internal errors in verbose mode
    (#​3938)
Integrations
  • The action output displayed in the job summary is now wrapped in Markdown (#​3914)

v23.9.1

Compare Source

Due to various issues, the previous release (23.9.0) did not include compiled mypyc
wheels, which make Black significantly faster. These issues have now been fixed, and
this release should come with compiled wheels once again.

There will be no wheels for Python 3.12 due to a bug in mypyc. We will provide 3.12
wheels in a future release as soon as the mypyc bug is fixed.

Packaging
Performance
  • Store raw tuples instead of NamedTuples in Black's cache, improving performance and
    decreasing the size of the cache (#​3877)

v23.9.0

Compare Source

Preview style
  • More concise formatting for dummy implementations (#​3796)
  • In stub files, add a blank line between a statement with a body (e.g an
    if sys.version_info > (3, x):) and a function definition on the same level (#​3862)
  • Fix a bug whereby spaces were removed from walrus operators within subscript(#​3823)
Configuration
  • Black now applies exclusion and ignore logic before resolving symlinks (#​3846)
Performance
  • Avoid importing IPython if notebook cells do not contain magics (#​3782)
  • Improve caching by comparing file hashes as fallback for mtime and size (#​3821)
Blackd
  • Fix an issue in blackd with single character input (#​3558)
Integrations
  • Black now has an
    official pre-commit mirror. Swapping
    https://github.com/psf/black to https://github.com/psf/black-pre-commit-mirror in
    your .pre-commit-config.yaml will make Black about 2x faster (#​3828)
  • The .black.env folder specified by ENV_PATH will now be removed on the completion
    of the GitHub Action (#​3759)

v23.7.0

Compare Source

Highlights
  • Runtime support for Python 3.7 has been removed. Formatting 3.7 code will still be
    supported until further notice (#​3765)
Stable style
  • Fix a bug where an illegal trailing comma was added to return type annotations using
    PEP 604 unions (#​3735)
  • Fix several bugs and crashes where comments in stub files were removed or mishandled
    under some circumstances (#​3745)
  • Fix a crash with multi-line magic comments like type: ignore within parentheses
    (#​3740)
  • Fix error in AST validation when Black removes trailing whitespace in a type comment
    (#​3773)
Preview style
  • Implicitly concatenated strings used as function args are no longer wrapped inside
    parentheses (#​3640)
  • Remove blank lines between a class definition and its docstring (#​3692)
Configuration
  • The --workers argument to Black can now be specified via the BLACK_NUM_WORKERS
    environment variable (#​3743)
  • .pytest_cache, .ruff_cache and .vscode are now excluded by default (#​3691)
  • Fix Black not honouring pyproject.toml settings when running --stdin-filename
    and the pyproject.toml found isn't in the current working directory (#​3719)
  • Black will now error if exclude and extend-exclude have invalid data types in
    pyproject.toml, instead of silently doing the wrong thing (#​3764)
Packaging
  • Upgrade mypyc from 0.991 to 1.3 (#​3697)
  • Remove patching of Click that mitigated errors on Python 3.6 with LANG=C (#​3768)
Parser
  • Add support for the new PEP 695 syntax in Python 3.12 (#​3703)
Performance
  • Speed up Black significantly when the cache is full (#​3751)
  • Avoid importing IPython in a case where we wouldn't need it (#​3748)
Output
  • Use aware UTC datetimes internally, avoids deprecation warning on Python 3.12 (#​3728)
  • Change verbose logging to exactly mirror Black's logic for source discovery (#​3749)
Blackd
  • The blackd argument parser now shows the default values for options in their help
    text (#​3712)
Integrations
Documentation
  • Add a CITATION.cff file to the root of the repository, containing metadata on how to
    cite this software (#​3723)
  • Update the classes and exceptions documentation in Developer reference to match
    the latest code base (#​3755)
nedbat/coveragepy (coverage)

v7.6.1

Compare Source

  • Fix: coverage used to fail when measuring code using :func:runpy.run_path <python:runpy.run_path> with a :class:Path <python:pathlib.Path> argument.
    This is now fixed, thanks to Ask Hjorth Larsen <pull 1819_>_.

  • Fix: backslashes preceding a multi-line backslashed string could confuse the
    HTML report. This is now fixed, thanks to LiuYinCarl <pull 1828_>_.

  • Now we publish wheels for Python 3.13, both regular and free-threaded.

.. _pull 1819:https://github.com/nedbat/coveragepy/pull/18199
.. _pull 1828https://github.com/nedbat/coveragepy/pull/182828

.. _changes_7-6-0:

v7.6.0

Compare Source

  • Exclusion patterns can now be multi-line, thanks to Daniel Diniz <pull 1807_>. This enables many interesting exclusion use-cases, including those
    requested in issues 118 <issue 118_>
    (entire files), 996 <issue 996_>_ (multiple lines only when appearing together), 1741 <issue 1741_>_ (remainder of a function), and 1803 <issue 1803_>_
    (arbitrary sequence of marked lines). See the :ref:multi_line_exclude
    section of the docs for more details and examples.

  • The JSON report now includes per-function and per-class coverage information.
    Thanks to Daniel Diniz <pull 1809_>_ for getting the work started. This
    closes issue 1793_ and issue 1532_.

  • Fixed an incorrect calculation of "(no class)" lines in the HTML classes
    report.

  • Python 3.13.0b3 is supported.

.. _issue 118:https://github.com/nedbat/coveragepy/issues/1188
.. _issue 996https://github.com/nedbat/coveragepy/issues/99696
.. _issue 153https://github.com/nedbat/coveragepy/issues/1532532
.. _issue 17https://github.com/nedbat/coveragepy/issues/17411741
.. _issue 1https://github.com/nedbat/coveragepy/issues/1793/1793
.. _issue https://github.com/nedbat/coveragepy/issues/1803s/1803
.. _pullhttps://github.com/nedbat/coveragepy/pull/1807ll/1807
.. _pulhttps://github.com/nedbat/coveragepy/pull/1809ull/1809

.. _changes_7-5-4:

v7.5.4

Compare Source

  • If you attempt to combine statement coverage data with branch coverage data,
    coverage.py used to fail with the message "Can't combine arc data with line
    data" or its reverse, "Can't combine line data with arc data." These
    messages used internal terminology, making it hard for people to understand
    the problem. They are now changed to mention "branch coverage data" and
    "statement coverage data."

  • Fixed a minor branch coverage problem with wildcard match/case cases using
    names or guard clauses.

  • Started testing on 3.13 free-threading (nogil) builds of Python. I'm not
    claiming full support yet. Closes issue 1799_.

.. _issue 1799:https://github.com/nedbat/coveragepy/issues/17999

.. _changes_7-5-3:

v7.5.3

Compare Source

  • Performance improvements for combining data files, especially when measuring
    line coverage. A few different quadratic behaviors were eliminated. In one
    extreme case of combining 700+ data files, the time dropped from more than
    three hours to seven minutes. Thanks for Kraken Tech for funding the fix.

  • Performance improvements for generating HTML reports, with a side benefit of
    reducing memory use, closing issue 1791_. Thanks to Daniel Diniz for
    helping to diagnose the problem.

.. _issue 1791:https://github.com/nedbat/coveragepy/issues/17911

.. _changes_7-5-2:

v7.5.2

Compare Source

  • Fix: nested matches of exclude patterns could exclude too much code, as
    reported in issue 1779_. This is now fixed.

  • Changed: previously, coverage.py would consider a module docstring to be an
    executable statement if it appeared after line 1 in the file, but not
    executable if it was the first line. Now module docstrings are never counted
    as executable statements. This can change coverage.py's count of the number
    of statements in a file, which can slightly change the coverage percentage
    reported.

  • In the HTML report, the filter term and "hide covered" checkbox settings are
    remembered between viewings, thanks to Daniel Diniz <pull 1776_>_.

  • Python 3.13.0b1 is supported.

  • Fix: parsing error handling is improved to ensure bizarre source files are
    handled gracefully, and to unblock oss-fuzz fuzzing, thanks to Liam DeVoe <pull 1788_>. Closes issue 1787.

.. _pull 1776:https://github.com/nedbat/coveragepy/pull/17766
.. _issue 1779https://github.com/nedbat/coveragepy/issues/177979
.. _issue 178https://github.com/nedbat/coveragepy/issues/1787787
.. _pull 17https://github.com/nedbat/coveragepy/pull/17881788

.. _changes_7-5-1:

v7.5.1

Compare Source

  • Fix: a pragma comment on the continuation lines of a multi-line statement
    now excludes the statement and its body, the same as if the pragma is
    on the first line. This closes issue 754. The fix was contributed by
    Daniel Diniz <pull 1773_>
    .

  • Fix: very complex source files like this one <resolvent_lookup_>_ could
    cause a maximum recursion error when creating an HTML report. This is now
    fixed, closing issue 1774_.

  • HTML report improvements:

    • Support files (JavaScript and CSS) referenced by the HTML report now have
      hashes added to their names to ensure updated files are used instead of
      stale cached copies.

    • Missing branch coverage explanations that said "the condition was never
      false" now read "the condition was always true" because it's easier to
      understand.

    • Column sort order is remembered better as you move between the index pages,
      fixing issue 1766. Thanks, Daniel Diniz <pull 1768_>.

.. _resolvent_lookup: https://github.com/sympy/sympy/blob/130950f3e6b3f97fcc17f4599ac08f70fdd2e9d4/sympy/polys/numberfields/resolvent_lookup.py
.. _issue 754https://github.com/nedbat/coveragepy/issues/75454
.. _issue 176https://github.com/nedbat/coveragepy/issues/1766766
.. _pull 17https://github.com/nedbat/coveragepy/pull/17681768
.. _pull 1https://github.com/nedbat/coveragepy/pull/1773/1773
.. _issue https://github.com/nedbat/coveragepy/issues/1774s/1774

.. _changes_7-5-0:

v7.5.0

Compare Source

  • Added initial support for function and class reporting in the HTML report.
    There are now three index pages which link to each other: files, functions,
    and classes. Other reports don't yet have this information, but it will be
    added in the future where it makes sense. Feedback gladly accepted!
    Finishes issue 780_.

  • Other HTML report improvements:

    • There is now a "hide covered" checkbox to filter out 100% files, finishing
      issue 1384_.

    • The index page is always sorted by one of its columns, with clearer
      indications of the sorting.

    • The "previous file" shortcut key didn't work on the index page, but now it
      does, fixing issue 1765_.

  • The debug output showing which configuration files were tried now shows
    absolute paths to help diagnose problems where settings aren't taking effect,
    and is renamed from "attempted_config_files" to the more logical
    "config_files_attempted."

  • Python 3.13.0a6 is supported.

.. _issue 780:https://github.com/nedbat/coveragepy/issues/7800
.. _issue 1384https://github.com/nedbat/coveragepy/issues/138484
.. _issue 176https://github.com/nedbat/coveragepy/issues/1765765

.. _changes_7-4-4:

v7.4.4

Compare Source

  • Fix: in some cases, even with [run] relative_files=True, a data file
    could be created with absolute path names. When combined with other relative
    data files, it was random whether the absolute file names would be made
    relative or not. If they weren't, then a file would be listed twice in
    reports, as detailed in issue 1752_. This is now fixed: absolute file
    names are always made relative when combining. Thanks to Bruno Rodrigues dos
    Santos for support.

  • Fix: the last case of a match/case statement had an incorrect message if the
    branch was missed. It said the pattern never matched, when actually the
    branch is missed if the last case always matched.

  • Fix: clicking a line number in the HTML report now positions more accurately.

  • Fix: the report:format setting was defined as a boolean, but should be a
    string. Thanks, Tanaydin Sirin <pull 1754_>_. It is also now documented
    on the :ref:configuration page <config_report_format>.

.. _issue 1752:https://github.com/nedbat/coveragepy/issues/17522
.. _pull 1754https://github.com/nedbat/coveragepy/pull/175454

.. _changes_7-4-3:

v7.4.3

Compare Source

  • Fix: in some cases, coverage could fail with a RuntimeError: "Set changed
    size during iteration." This is now fixed, closing issue 1733_.

.. _issue 1733:https://github.com/nedbat/coveragepy/issues/17333

.. _changes_7-4-2:

v7.4.2

Compare Source

  • Fix: setting COVERAGE_CORE=sysmon no longer errors on 3.11 and lower,
    thanks Hugo van Kemenade <pull 1747_>_. It now issues a warning that
    sys.monitoring is not available and falls back to the default core instead.

.. _pull 1747:https://github.com/nedbat/coveragepy/pull/17477

.. _changes_7-4-1:

v7.4.1

Compare Source

  • Python 3.13.0a3 is supported.

  • Fix: the JSON report now includes an explicit format version number, closing
    issue 1732_.

.. _issue 1732:https://github.com/nedbat/coveragepy/issues/17322

.. _changes_7-4-0:

v7.4.0

Compare Source

  • In Python 3.12 and above, you can try an experimental core based on the new
    :mod:sys.monitoring <python:sys.monitoring> module by defining a
    COVERAGE_CORE=sysmon environment variable. This should be faster for
    line coverage, but not for branch coverage, and plugins and dynamic contexts
    are not yet supported with it. I am very interested to hear how it works (or
    doesn't!) for you.

.. _changes_7-3-4:

v7.3.4

Compare Source

  • Fix: the change for multi-line signature exclusions in 7.3.3 broke other
    forms of nested clauses being excluded properly. This is now fixed, closing
    issue 1713_.

  • Fix: in the HTML report, selecting code for copying won't select the line
    numbers also. Thanks, Robert Harris <pull 1717_>_.

.. _issue 1713:https://github.com/nedbat/coveragepy/issues/17133
.. _pull 1717https://github.com/nedbat/coveragepy/pull/171717

.. _changes_7-3-3:

v7.3.3

Compare Source

  • 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 <pull 1705_>.

  • 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 <cmd_run_debug>:

    • 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/6844
.. _pull 1705https://github.com/nedbat/coveragepy/pull/170505
.. _issue 170https://github.com/nedbat/coveragepy/issues/1709709

.. _changes_7-3-2:

v7.3.2

Compare Source

  • The coverage lcov command ignored the [report] exclude_lines and
    [report] exclude_also settings (issue 1684). This is now fixed,
    thanks Jacqueline Lee <pull 1685_>
    .

  • 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/16055
.. _issue 1684https://github.com/nedbat/coveragepy/issues/168484
.. _pull 168https://github.com/nedbat/coveragepy/pull/1685685
.. _880https://github.com/python/cpython/issues/880548054

.. _changes_7-3-1:

v7.3.1

Compare Source

  • 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 <starbad_>, who provided patient detailed diagnosis <pull 1650_> and
    graciously agreed to a pragmatic resolution.

  • The API docs were missing from the last version. They are now restored <apidocs_>_.

.. _apidocs: https://coverage.readthedocs.io/en/latest/api_coverage.html
.. _starbadhttps://github.com/nedbat/coveragepy/issues/1407#issuecomment-163108520909
.. _pull 165https://github.com/nedbat/coveragepy/pull/1650650

.. _changes_7-3-0:

v7.3.0

Compare Source

  • Added a :meth:.Coverage.collect context manager to start and stop coverage
    data collection.

  • Dropped support for Python 3.7.

  • Fix: in unusual circumstances, SQLite cannot be set to asynchronous mode.
    Coverage.py would fail with the error Safety level may not be changed inside a transaction. This is now avoided, closing issue 1646_. Thanks
    to Michael Bell for the detailed bug report.

  • Docs: examples of configuration files now include separate examples for the
    different syntaxes: .coveragerc, pyproject.toml, setup.cfg, and tox.ini.

  • Fix: added nosemgrep comments to our JavaScript code so that
    semgrep-based SAST security checks won't raise false alarms about security
    problems that aren't problems.

  • Added a CITATION.cff file, thanks to Ken Schackart <pull 1641_>_.

.. _pull 1641:https://github.com/nedbat/coveragepy/pull/16411
.. _issue 1646https://github.com/nedbat/coveragepy/issues/164646

.. _changes_7-2-7:

pycqa/isort (isort)

v5.13.2

Compare Source

v5.13.1

Compare Source

v5.13.0

Compare Source


Configuration

📅 Schedule: Branch creation - "before 10pm on Sunday" in timezone America/Chicago, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from c7dc9c5 to 9d48304 Compare May 19, 2024 01:26
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 9d48304 to 410f183 Compare May 25, 2024 19:10
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from fe0806d to c6df159 Compare June 8, 2024 19:12
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 94df06a to ca4d5f8 Compare July 11, 2024 16:41
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from ca4d5f8 to 10ba102 Compare July 14, 2024 11:27
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 2ef32be to cb1c73d Compare July 29, 2024 04:57
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 3853c7a to b7b4a48 Compare August 18, 2024 19:42
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from b7b4a48 to 612cd12 Compare August 23, 2024 22:04
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 8e858ad to 2d153e1 Compare September 7, 2024 16:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants