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

Update coveralls to 3.3.0 #96

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

Conversation

pyup-bot
Copy link
Collaborator

@pyup-bot pyup-bot commented Nov 4, 2021

This PR updates coveralls from 2.0.0 to 3.3.0.

Changelog

3.3.0

Features

* **cli:**  add --srcdir option (306) ([4120c540](4120c540))
* **deps:**  add support for coverage v6.x (330) ([372443dc](372443dc), closes [326](326))

Note this implicitly improves support for Python 3.10, as coverage v6.x includes some fixes for v3.10 of Python.

Bug Fixes

* **env:**  fixup handling of default env service values (314) ([1a0fd9b3](1a0fd9b3), closes [303](303))

This solves some edge cases around duplicated / unmerged coverage results in parallel runs.

<a name="3.2.0"></a>

3.2.0

Features

* **api:**  support officially documented generic CI env vars (300) ([ca1c6a47](ca1c6a47))

<a name="3.1.0"></a>

3.1.0

Features

* **cli**:  add `--basedir` and `--submit` options (287) ([165a5cd1](165a5cd1))
* **github:**  push coverage info from tags (284) ([0a49bd28](0a49bd28))

<a name="3.0.1"></a>

3.0.1

Bug Fixes

* **github:**  send null job_id to fix 422 during resubmission (269) ([54be7545](54be7545))

<a name="3.0.0"></a>

3.0.0

Features (BREAKING)

* **config:**  reorder configuration precedence (249) ([f4faa92d](f4faa92d))

We have *reversed* the order in which configurations are parsed. This means we
are now following the following precedence (latest configured value is used):

1. CI Config
2. COVERALLS_* env vars
3. .coveralls.yml file
4. CLI flags

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

* **github:**  send null job_id to fix 422 ([05b66aa0](05b66aa0))
* **api:**  fixup retries for services without job IDs ([6ebdc5e2](6ebdc5e2))

<a name="2.2.0"></a>

2.2.0

Features

* **api:**  add workaround allowing job resubmission (241) ([0de0c019](0de0c019))

Bug Fixes

* **integrations:**  fixup environment detection for Semaphore CI (236) ([ad4f8fa8](ad4f8fa8))

<a name="2.1.2"></a>

2.1.2

Features

* **circleci:**  support parallel builds (233) ([5e05654c](5e05654c))
          Note: this is partially a fix for the `--finish` command
          introduced in v2.1.0, which did not seem to work for some CircleCI
          users.


<a name="2.1.1"></a>

2.1.1

Bug Fixes

*  fix unhashable CoverallsException (230) ([aa55335d](aa55335d))
This fixes a regression introduced in v2.1.0 which affected (at least) any
Python 3.5 installations.


<a name="2.1.0"></a>

2.1.0

Features

* **cli**:  add new `--finish` flag for finalizing parallel builds (277) ([f597109b](f597109b))

Bug Fixes

* **github:**  fix Github Actions support (227) ([f597109b](f597109b))

<a name="2.0.0"></a>
Links

@pyup-bot pyup-bot mentioned this pull request Nov 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant