Update dependency coverage to v7.10.6 #121
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "renovate/coverage-7.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
==7.4.0->==7.10.6Release Notes
nedbat/coveragepy (coverage)
v7.10.6Compare Source
Fix:
sourcedirectories were not properly communicated to subprocessesthat ran in different directories, as reported in
issue 1499_. This is nowfixed.
Performance:
Alex Gaynor continues fine-tuning <pull 2038_>_ the speed ofcombination, especially with many contexts.
.. _issue 1499: #1499
.. _pull 2038: #2038
.. _changes_7-10-5:
v7.10.5Compare Source
coverage combine: it's now about twice asfast! Huge thanks to Alex Gaynor for pull requests
2032 <pull 2032_>,2033 <pull 2033_>, and2034 <pull 2034_>_... _pull 2032: #2032
.. _pull 2033: #2033
.. _pull 2034: #2034
.. _changes_7-10-4:
v7.10.4Compare Source
Added
patch = forkfor times when the built-in forking support isinsufficient.
Fix:
patch = execvalso inherits the entire coverage configuration now... _changes_7-10-3:
v7.10.3Compare Source
Fixes for
patch = subprocess:If subprocesses spawned yet more subprocesses simultaneously, some coverage
could be missed. This is now fixed, closing
issue 2024_.If subprocesses were created in other directories, their data files were
stranded there and not combined into the totals, as described in
issue 2025_. This is now fixed.On Windows (or maybe only some Windows?) the patch would fail with a
ModuleNotFounderror trying to import coverage. This is now fixed,closing
issue 2022_.Originally only options set in the coverage configuration file would apply
to subprocesses. Options set on the
coverage runcommand line (such as--branch) wouldn't be communicated to the subprocesses. This couldlead to combining failures, as described in
issue 2021_. Now the entireconfiguration is used in subprocesses, regardless of its origin.
Added
debug=patchto help diagnose problems.Fix: really close all SQLite databases, even in-memory ones. Closes
issue 2017_... _issue 2017: #2017
.. _issue 2021: #2021
.. _issue 2022: #2022
.. _issue 2024: #2024
.. _issue 2025: #2025
.. _changes_7-10-2:
v7.10.2Compare Source
actually executed. This is now fixed, closing
issue 1999_. Python 3.9still shows the problem.
.. _issue 1999: #1999
.. _changes_7-10-1:
v7.10.1Compare Source
Fix: the exclusion for
if TYPE_CHECKING:was wrong: it marked the branchas partial, but it should have been a line exclusion so the entire clause
would be excluded. Improves
issue 831_.Fix: changed where .pth files are written for
patch = subprocess, closingissue 2006_... _issue 2006: #2006
.. _changes_7-10-0:
v7.10.0Compare Source
A new configuration option: ":ref:
config_run_patch" specifies named patchesto work around some limitations in coverage measurement. These patches are
available:
patch = _exitlets coverage save its data even when :func:os._exit() <python:os._exit>is used to abruptly end the process. This closeslong-standing
issue 310_ as well as its duplicates:issue 312,issue 1673,issue 1845, andissue 1941.patch = subprocessmeasures coverage in Python subprocesses createdwith :mod:
subprocess, :func:os.system, or one of the :func:execv <python:os.execl>or :func:spawnv <python:os.spawnl>family offunctions. Closes old
issue 367, its duplicateissue 378and oldissue 689_.patch = execvadjusts the :func:execv <python:os.execl>family offunctions to save coverage data before ending the current program and
starting the next. Not available on Windows. Closes
issue 43_ after 15years!
The HTML report now dimly colors subsequent lines in multi-line statements.
They used to have no color. This gives a better indication of the amount of
code missing in the report. Closes
issue 1308_.Two new exclusion patterns are part of the defaults:
...is automaticallyexcluded as a line and
if TYPE_CHECKING:is excluded as a branch. Closesissue 831_.A new command-line option:
--save-signal=USR1specifies a signal thatcoverage.py will listen for. When the signal is sent, the coverage data will
be saved. This makes it possible to save data from within long-running
processes. Thanks,
Arkady Gilinsky <pull 1998_>_.A new configuration option: ":ref:
config_report_partial_also" is a list ofregexes to add as pragmas for partial branches. This parallels the
":ref:
config_report_exclude_also" setting for adding line exclusionpatterns.
A few file path configuration settings didn't allow for tilde expansion:
:ref:
config_json_output, :ref:config_lcov_outputand:ref:
config_run_debug_file. This is now fixed.Wheels are included for 3.14 now that 3.14 rc1 is available.
We no longer ship a PyPy-specific wheel. PyPy will install the pure-Python
wheel. Closes
issue 2001_.In the very unusual situation of not having a current frame, coverage no
longer crashes when using the sysmon core, fixing
issue 2005_... _issue 43: #43
.. _issue 310: #310
.. _issue 312: #312
.. _issue 367: #367
.. _issue 378: #378
.. _issue 689: #689
.. _issue 831: #831
.. _issue 1308: #1308
.. _issue 1673: #1673
.. _issue 1845: #1845
.. _issue 1941: #1941
.. _pull 1998: #1998
.. _issue 2001: #2001
.. _issue 2005: #2005
.. _changes_7-9-2:
v7.9.2Compare Source
Fix: complex conditionals within a line might cause a KeyError when using
sys.monitoring, as reported in
issue 1991_. This is now fixed.Fix: we can now measure coverage for code in Python archive (.par) files.
Thanks,
Itamer Oren <pull 1984_>_... _pull 1984: #1984
.. _issue 1991: #1991
.. _changes_7-9-1:
v7.9.1Compare Source
The "no-ctracer" warning is not issued for Python pre-release versions.
Coverage doesn't ship compiled wheels for those versions, so this was far too
noisy.
On Python 3.14+, the "sysmon" core is now the default if it's supported for
your configuration. Plugins and dynamic contexts are still not supported
with it.
.. _changes_7-9-0:
v7.9.0Compare Source
Added a
[run] coreconfiguration setting to specify the measurement core,which was previously only available through the COVERAGE_CORE environment
variable. Finishes
issue 1746_.Fixed incorrect rendering of f-strings with doubled braces, closing
issue 1980_.If the C tracer core can't be imported, a warning ("no-ctracer") is issued
with the reason.
The C tracer core extension module now conforms to
PEP 489, closingissue 1977. Thanks,Adam Turner <pull 1978_>_.Fixed a "ValueError: min() arg is an empty sequence" error caused by strange
empty modules, found by
oss-fuzz_... _issue 1746: #1746
.. _issue 1977: #1977
.. _pull 1978: #1978
.. _issue 1980: #1980
.. _PEP 489: https://peps.python.org/pep-0489
.. _oss-fuzz: https://google.github.io/oss-fuzz/
.. _changes_7-8-2:
v7.8.2Compare Source
Thanks,
Finn Womack <pull 1972_>_... _issue 1971: #1971
.. _pull 1972: #1972
.. _changes_7-8-1:
v7.8.1Compare Source
A number of EncodingWarnings were fixed that could appear if you've enabled
PYTHONWARNDEFAULTENCODING, fixing
issue 1966. Thanks,Henry Schreiner <pull 1967_>.Fixed a race condition when using sys.monitoring with free-threading Python,
closing
issue 1970_... _issue 1966: #1966
.. _pull 1967: #1967
.. _issue 1970: #1970
.. _changes_7-8-0:
v7.8.0Compare Source
Added a new
source_dirssetting for symmetry with the existingsource_pkgssetting. It's preferable to the existingsourcesetting,because you'll get a clear error when directories don't exist. Fixes
issue 1942. Thanks,Jeremy Fleischman <pull 1943_>.Fix: the PYTHONSAFEPATH environment variable new in Python 3.11 is properly
supported, closing
issue 1696. Thanks,Philipp A. <pull 1700_>. Thisworks properly except for a detail when using the
coveragecommand onWindows. There you can use
python -m coverageinstead if you need exactemulation.
.. _issue 1696: #1696
.. _pull 1700: #1700
.. _issue 1942: #1942
.. _pull 1943: #1943
.. _changes_7-7-1:
v7.7.1Compare Source
test!
.. _changes_7-7-0:
v7.7.0Compare Source
The Coverage object has a new method, :meth:
.Coverage.branch_statsforgetting simple branch information for a module. Closes
issue 1888_.The :class:
Coverage constructor<.Coverage>now has apluginsparameterfor passing in plugin objects directly, thanks to
Alex Gaynor <pull 1919_>_.Many constant tests in if statements are now recognized as being optimized
away. For example, previously
if 13:would have been considered a branchwith one path not taken. Now it is understood as always true and no coverage
is missing.
The experimental sys.monitoring support now works for branch coverage if you
are using Python 3.14.0 alpha 6 or newer. This should reduce the overhead
coverage.py imposes on your test suite. Set the environment variable
COVERAGE_CORE=sysmonto try it out.Confirmed support for PyPy 3.11. Thanks Michał Górny.
.. _issue 1888: #1888
.. _pull 1919: #1919
.. _changes_7-6-12:
v7.6.12Compare Source
issue 1927_). These are nowbuilding reliably.
.. _issue 1927: https://github.com/nedbat/coveragepy/issues/1927
.. _changes_7-6-11:
v7.6.11Compare Source
Fix: a memory leak in CTracer has been fixed. The details are in
issue 1924_ andpytest-dev 676_. This should reduce the memory footprint foreveryone even if it hadn't caused a problem before.
We now ship a py3-none-any.whl wheel file. Thanks,
Russell Keith-Magee <pull 1914_>_... _pull 1914: https://github.com/nedbat/coveragepy/pull/1914
.. _issue 1924: https://github.com/nedbat/coveragepy/issues/1924
.. _pytest-dev 676: https://github.com/pytest-dev/pytest-cov/issues/676
.. _changes_7-6-10:
v7.6.10Compare Source
Fix: some descriptions of missing branches in HTML and LCOV reports were
incorrect when multi-line statements were involved (
issue 1874_ andissue 1875_). These are now fixed.Fix: Python 3.14
defers evaluation of annotations <pep649_>_ by moving theminto separate code objects. That code is rarely executed, so coverage.py
would mark them as missing, as reported in
issue 1908_. Now they areignored by coverage automatically.
Fixed an obscure and mysterious problem on PyPy 3.10 seemingly involving
mocks, imports, and trace functions:
issue 1902_. To be honest, I don'tunderstand the problem or the solution, but
git bisecthelped find it,and now it's fixed.
Docs: re-wrote the :ref:
subprocesspage to put multiprocessing first and tohighlight the correct use of :class:
multiprocessing.Pool <python:multiprocessing.pool.Pool>... _issue 1874: https://github.com/nedbat/coveragepy/issues/1874
.. _issue 1875: https://github.com/nedbat/coveragepy/issues/1875
.. _issue 1902: https://github.com/nedbat/coveragepy/issues/1902
.. _issue 1908: https://github.com/nedbat/coveragepy/issues/1908
.. _pep649: https://docs.python.org/3.14/whatsnew/3.14.html#whatsnew314-pep649
.. _changes_7-6-9:
v7.6.9Compare Source
Tomas Uribe fixed <pull 1901_>_ a performance problem in the XMLreport. Large code bases should produce XML reports much faster now.
.. _pull 1901: https://github.com/nedbat/coveragepy/pull/1901
.. _changes_7-6-8:
v7.6.8Compare Source
Fix: the LCOV report code assumed that a branch line that took no branches
meant that the entire line was unexecuted. This isn't true in a few cases:
the line might always raise an exception, or might have been optimized away.
Fixes
issue 1896_.Fix: similarly, the HTML report will now explain that a line that jumps to
none of its expected destinations must have always raised an exception.
Previously, it would say something nonsensical like, "line 4 didn't jump to
line 5 because line 4 was never true, and it didn't jump to line 7 because
line 4 was always true." This was also shown in
issue 1896_... _issue 1896: https://github.com/nedbat/coveragepy/issues/1896
.. _changes_7-6-7:
v7.6.7Compare Source
so it's been restored to a conditional. Sorry for the churn.
.. _changes_7-6-6:
v7.6.6Compare Source
reported in
issue 1891_. The assert has been removed... _issue 1891: https://github.com/nedbat/coveragepy/issues/1891
.. _changes_7-6-5:
v7.6.5Compare Source
Fix: fine-tuned the exact Python version (3.12.6) when exiting from
withstatements changed how they traced. This affected whether people saw the
fix for
issue 1880_.Fix: isolate our code more from mocking in the os module that in rare cases
can cause
bizarre behavior <pytest-cov-666_>_.Refactor: some code unreachable code paths in parser.py were changed to
asserts. If you encounter any of these, please let me know!
.. _pytest-cov-666: https://github.com/pytest-dev/pytest-cov/issues/666
.. _changes_7-6-4:
v7.6.4Compare Source
withstatements could cause contained branches to beincorrectly marked as missing (
issue 1880_). This is now fixed... _issue 1880: https://github.com/nedbat/coveragepy/issues/1880
.. _changes_7-6-3:
v7.6.3Compare Source
Fix: nested context managers could incorrectly be analyzed to flag a missing
branch on the last context manager, as described in
issue 1876_. This isnow fixed.
Fix: the missing branch message about not exiting a module had an extra
"didn't," as described in
issue 1873_. This is now fixed... _issue 1873: https://github.com/nedbat/coveragepy/issues/1873
.. _issue 1876: https://github.com/nedbat/coveragepy/issues/1876
.. _changes_7-6-2:
v7.6.2Compare Source
Dropped support for Python 3.8 and PyPy 3.8.
Fix: a final wildcard match/case clause assigning to a name (
case _ as value) was incorrectly marked as a missing branch. This is now fixed,closing
issue 1860_.Fewer things are considered branches now. Lambdas, comprehensions, and
generator expressions are no longer marked as missing branches if they don't
complete execution. Closes
issue 1852_.Fix: the HTML report didn't properly show multi-line f-strings that end with
a backslash continuation. This is now fixed, closing
issue 1836, thanksto
LiuYinCarl and Marco Ricci <pull 1838_>.Fix: the LCOV report now has correct line numbers (fixing
issue 1846) andbetter branch descriptions for BRDA records (fixing
issue 1850). Thereare other changes to lcov also, including a new configuration option
:ref:
line_checksums <config_lcov_line_checksums>to control whether linechecksums are included in the lcov report. The default is false. To keep
checksums set it to true. All this work is thanks to Zack Weinberg
(
pull 1849_ andpull 1851_).Fixed the docs for multi-line regex exclusions, closing
issue 1863_.Fixed a potential crash in the C tracer, closing
issue 1835, thanks toJan Kühle <pull 1843_>... _issue 1835: https://github.com/nedbat/coveragepy/issues/1835
.. _issue 1836: https://github.com/nedbat/coveragepy/issues/1836
.. _pull 1838: https://github.com/nedbat/coveragepy/pull/1838
.. _pull 1843: https://github.com/nedbat/coveragepy/pull/1843
.. _issue 1846: https://github.com/nedbat/coveragepy/issues/1846
.. _pull 1849: https://github.com/nedbat/coveragepy/pull/1849
.. _issue 1850: https://github.com/nedbat/coveragepy/issues/1850
.. _pull 1851: https://github.com/nedbat/coveragepy/pull/1851
.. _issue 1852: https://github.com/nedbat/coveragepy/issues/1852
.. _issue 1860: https://github.com/nedbat/coveragepy/issues/1860
.. _issue 1863: https://github.com/nedbat/coveragepy/issues/1863
.. _changes_7-6-1:
v7.6.1Compare Source
issue 1927_). These are nowbuilding reliably.
.. _issue 1927: https://github.com/nedbat/coveragepy/issues/1927
.. _changes_7-6-11:
v7.6.0Compare Source
Exclusion patterns can now be multi-line, thanks to
Daniel Diniz <pull 1807_>. This enables many interesting exclusion use-cases, including thoserequested in issues
118 <issue 118_>(entire files),996 <issue 996_>_ (multiple lines only when appearing together),1741 <issue 1741_>_ (remainder of a function), and1803 <issue 1803_>_(arbitrary sequence of marked lines). See the :ref:
multi_line_excludesection 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. Thiscloses
issue 1793_ andissue 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/118
.. _issue 996: https://github.com/nedbat/coveragepy/issues/996
.. _issue 1532: https://github.com/nedbat/coveragepy/issues/1532
.. _issue 1741: https://github.com/nedbat/coveragepy/issues/1741
.. _issue 1793: https://github.com/nedbat/coveragepy/issues/1793
.. _issue 1803: https://github.com/nedbat/coveragepy/issues/1803
.. _pull 1807: https://github.com/nedbat/coveragepy/pull/1807
.. _pull 1809: https://github.com/nedbat/coveragepy/pull/1809
.. _changes_7-5-4:
v7.5.4Compare 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/1799
.. _changes_7-5-3:
v7.5.3Compare 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 forhelping to diagnose the problem.
.. _issue 1791: https://github.com/nedbat/coveragepy/issues/1791
.. _changes_7-5-2:
v7.5.2Compare 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_>. Closesissue 1787... _pull 1776: https://github.com/nedbat/coveragepy/pull/1776
.. _issue 1779: https://github.com/nedbat/coveragepy/issues/1779
.. _issue 1787: https://github.com/nedbat/coveragepy/issues/1787
.. _pull 1788: https://github.com/nedbat/coveragepy/pull/1788
.. _changes_7-5-1:
v7.5.1Compare 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 byDaniel Diniz <pull 1773_>.Fix: very complex source files like
this one <resolvent_lookup_>_ couldcause 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:
130950f3e6/sympy/polys/numberfields/resolvent_lookup.py.. _issue 754: https://github.com/nedbat/coveragepy/issues/754
.. _issue 1766: https://github.com/nedbat/coveragepy/issues/1766
.. _pull 1768: https://github.com/nedbat/coveragepy/pull/1768
.. _pull 1773: https://github.com/nedbat/coveragepy/pull/1773
.. _issue 1774: https://github.com/nedbat/coveragepy/issues/1774
.. _changes_7-5-0:
v7.5.0Compare 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/780
.. _issue 1384: https://github.com/nedbat/coveragepy/issues/1384
.. _issue 1765: https://github.com/nedbat/coveragepy/issues/1765
.. _changes_7-4-4:
v7.4.4Compare Source
Fix: in some cases, even with
[run] relative_files=True, a data filecould 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 filenames 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:formatsetting was defined as a boolean, but should be astring. Thanks,
Tanaydin Sirin <pull 1754_>_. It is also now documentedon the :ref:
configuration page <config_report_format>... _issue 1752: https://github.com/nedbat/coveragepy/issues/1752
.. _pull 1754: https://github.com/nedbat/coveragepy/pull/1754
.. _changes_7-4-3:
v7.4.3Compare Source
size during iteration." This is now fixed, closing
issue 1733_... _issue 1733: https://github.com/nedbat/coveragepy/issues/1733
.. _changes_7-4-2:
v7.4.2Compare Source
COVERAGE_CORE=sysmonno longer errors on 3.11 and lower,thanks
Hugo van Kemenade <pull 1747_>_. It now issues a warning thatsys.monitoring is not available and falls back to the default core instead.
.. _pull 1747: https://github.com/nedbat/coveragepy/pull/1747
.. _changes_7-4-1:
v7.4.1Compare 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/1732
.. _changes_7-4-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 Renovate Bot.
ad89eddbf8to666c7757f6Update dependency coverage to v7.5.0to Update dependency coverage to v7.5.1666c7757f6tof2ad28db4fUpdate dependency coverage to v7.5.1to Update dependency coverage to v7.5.2f2ad28db4fto86f1da4beeUpdate dependency coverage to v7.5.2to Update dependency coverage to v7.5.3Update dependency coverage to v7.5.3to Update dependency coverage to v7.5.486f1da4beetob6aa72f655b6aa72f655tob4627a4ad1Update dependency coverage to v7.5.4to Update dependency coverage to v7.6.0Update dependency coverage to v7.6.0to Update dependency coverage to v7.6.1b4627a4ad1to65d8567cd9Update dependency coverage to v7.6.1to Update dependency coverage to v7.6.265d8567cd9todcef37f55aUpdate dependency coverage to v7.6.2to Update dependency coverage to v7.6.3dcef37f55ato91870913009187091300toa7e6ce99f4Update dependency coverage to v7.6.3to Update dependency coverage to v7.6.4a7e6ce99f4to7dfaff1f0dUpdate dependency coverage to v7.6.4to Update dependency coverage to v7.6.57dfaff1f0dto65f1912778Update dependency coverage to v7.6.5to Update dependency coverage to v7.6.6Update dependency coverage to v7.6.6to Update dependency coverage to v7.6.765f1912778tod6bbbff080Update dependency coverage to v7.6.7to Update dependency coverage to v7.6.8d6bbbff080to808f6ebab5Update dependency coverage to v7.6.8to Update dependency coverage to v7.6.9808f6ebab5toa7a897b65fUpdate dependency coverage to v7.6.9to Update dependency coverage to v7.6.10a7a897b65fto1200f2fb011200f2fb01tof8331f0ba6Update dependency coverage to v7.6.10to Update dependency coverage to v7.6.11f8331f0ba6to3dd6be7909Update dependency coverage to v7.6.11to Update dependency coverage to v7.6.123dd6be7909to9e612eb21bUpdate dependency coverage to v7.6.12to Update dependency coverage to v7.7.0Update dependency coverage to v7.7.0to Update dependency coverage to v7.7.19e612eb21btob3fa9d3636Update dependency coverage to v7.7.1to Update dependency coverage to v7.8.0b3fa9d3636toe214f49b95e214f49b95tobcf5fda39aUpdate dependency coverage to v7.8.0to Update dependency coverage to v7.8.1bcf5fda39atocc1173e120Update dependency coverage to v7.8.1to Update dependency coverage to v7.8.2cc1173e120to303ca4bb87Update dependency coverage to v7.8.2to Update dependency coverage to v7.9.0Update dependency coverage to v7.9.0to Update dependency coverage to v7.9.1303ca4bb87tod231eaba9dd231eaba9dto7a30607cecUpdate dependency coverage to v7.9.1to Update dependency coverage to v7.9.2Update dependency coverage to v7.9.2to Update dependency coverage to v7.10.07a30607cecto4dc6ce1e30Update dependency coverage to v7.10.0to Update dependency coverage to v7.10.14dc6ce1e30to87ff06492387ff064923to08a19164d3Update dependency coverage to v7.10.1to Update dependency coverage to v7.10.208a19164d3to26f90574b0Update dependency coverage to v7.10.2to Update dependency coverage to v7.10.326f90574b0to2b0459dee2Update dependency coverage to v7.10.3to Update dependency coverage to v7.10.42b0459dee2to1d1bb2a416Update dependency coverage to v7.10.4to Update dependency coverage to v7.10.5Update dependency coverage to v7.10.5to Update dependency coverage to v7.10.61d1bb2a416to1b380468eeView command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.