chore(deps-dev): bump coveralls from 2.2.0 to 3.0.1

[dependabot-preview[bot]]

Bumps coveralls from 2.2.0 to 3.0.1.

Release notes

Sourced from coveralls's releases.

3.0.0

3.0.0 (2021-01-12)

Features (BREAKING)

• config: reorder configuration precedence (#249) (https://github.com/TheKevJames/coveralls-python/blob/HEAD/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 (https://github.com/TheKevJames/coveralls-python/blob/HEAD/05b66aa0)
• api: fixup retries for services without job IDs (https://github.com/TheKevJames/coveralls-python/blob/HEAD/6ebdc5e2)

Changelog

Sourced from coveralls's changelog.

3.0.1 (2021-03-02)

Bug Fixes

• github: send null job_id to fix 422 during resubmission (#269) (https://github.com/TheKevJames/coveralls-python/blob/master/54be7545)

3.0.0 (2021-01-12)

Features (BREAKING)

• config: reorder configuration precedence (#249) (https://github.com/TheKevJames/coveralls-python/blob/master/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 (https://github.com/TheKevJames/coveralls-python/blob/master/05b66aa0)
• api: fixup retries for services without job IDs (https://github.com/TheKevJames/coveralls-python/blob/master/6ebdc5e2)

Commits

• fbd4090 chore(release): fixup version spec
• daa4d80 chore(release): bump version
• 54be754 fix(github): send null job_id to fix 422 during resubmission (#269)
• f42e10a chore(deps): update precommit hook pre-commit/pygrep-hooks to v1.8.0 (#268)
• ea3a8a4 chore(deps): update precommit hook pre-commit/pygrep-hooks to v1.7.1 (#266)
• fe6b14a chore(deps): update precommit hook asottile/pyupgrade to v2.10.0 (#267)
• 4e88dd8 chore(deps): update precommit hook asottile/reorder_python_imports to v2.4.0 ...
• 1e14c53 chore(deps): update precommit hook asottile/pyupgrade to v2.9.0 (#264)
• c6d1096 chore(deps): update linter orb to v1.1.60 (#263)
• 405e90f docs: add more github service name info
• Additional commits viewable in compare view

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.

If all status checks pass Dependabot will automatically merge this pull request.

---

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) - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in the `.dependabot/config.yml` file in this repo: - Update frequency - Automerge options (never/patch/minor, and dev/runtime dependencies) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)

[dependabot-preview[bot]]

One of your CI runs failed on this pull request, so Dependabot won't merge it.

• Unit tests (3.7, windows-latest)
• Unit tests (3.7, ubuntu-latest)
• Unit tests (3.7, macos-latest)
• Unit tests (3.6, windows-latest)
• Unit tests (3.6, macos-latest)
• Unit tests (2.7, macos-latest)

Dependabot will still automatically merge this pull request if you amend it and your tests pass.

[dependabot-preview[bot]]

OK, I won't notify you again about this release, but will get in touch when a new version is available.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.