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:
==2.0.0
->==4.0.1
Release Notes
TheKevJames/coveralls-python (coveralls)
v4.0.1
Compare Source
Internal
coverage
v7.5+ (#442) (f41dca5).git
is missing (#443) (b566fc3)v4.0.0
Compare Source
BREAKING CHANGES
When
config.ignore_errors
is Falsey, failures to parse Python files orlook up file sources will now interrupt and early exit collection, which
matches default
coverage
behaviour. Previously, we had manually mutedthese errors and/or only errored after collecting multiple failures.
See the coverage.py docs for setting this option.
Features
pyproject.toml
packages by default (viacoverage[toml]
) (962e2242)python-coveralls
entrypoint (3d8d56e4)Bug Fixes
CoverallsException
(be446287)Internal
coverage
v7.0 - v7.4 (8fb36645)coverage
v4.x (752f52a0)docker
imagescoverage
public interface (#421)v3.3.1
Compare Source
Bug Fixes
Internal
coverage
versions (#337)coverage
versions v6.0.0 through v6.1.1 exhibited some incompatibilies withcoveralls
; we've updated our version compatibility ranges to exclude thoseversions.
v3.3.0
Compare Source
Features
Note this implicitly improves support for Python 3.10, as coverage v6.x includes some fixes for v3.10 of Python.
Bug Fixes
This solves some edge cases around duplicated / unmerged coverage results in parallel runs.
v3.2.0
Compare Source
Features
v3.1.0
Compare Source
Features
--basedir
and--submit
options (#287) (165a5cd1)v3.0.1
Compare Source
Bug Fixes
v3.0.0
Compare Source
Features (BREAKING)
We have reversed the order in which configurations are parsed. This means we
are now following the following precedence (latest configured value is used):
If you have the same fields set in multiple of the above locations, please
double-check them before upgrading to v3.
The motivation for this change is allowing users to selectively fix values
which may be automatically set to the wrong value. For example, Github Actions
users may find that Github Actions expects you to use a different "service name"
in various different cases. Now you can run, for example:
coveralls --service=github
In places where you need to override the default (which is
github-actions
).Bug Fixes
v2.2.0
Compare Source
Features
Bug Fixes
v2.1.2
Compare Source
Features
Note: this is partially a fix for the
--finish
commandintroduced in v2.1.0, which did not seem to work for some CircleCI
users.
v2.1.1
Compare Source
Bug Fixes
This fixes a regression introduced in v2.1.0 which affected (at least) any
Python 3.5 installations.
v2.1.0
Compare Source
Features
--finish
flag for finalizing parallel builds (#277) (f597109b)Bug Fixes
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 was generated by Mend Renovate. View the repository job log.