Bump coveralls from 2.2.0 to 3.2.0

[dependabot-preview[bot]]

Bumps coveralls from 2.2.0 to 3.2.0.

Release notes

Sourced from coveralls's releases.

3.2.0 (2021-07-20)

Features

• api: support officially documented generic CI env vars (#300) (https://github.com/TheKevJames/coveralls-python/blob/HEAD/ca1c6a47) -- thanks @​abravalheri!

3.1.0

3.1.0 (2021-05-24)

Features

• cli: add --basedir and --submit options (#287) (https://github.com/TheKevJames/coveralls-python/blob/HEAD/165a5cd1)
• github: push coverage info from tags (#284) (https://github.com/TheKevJames/coveralls-python/blob/HEAD/0a49bd28)

3.0.1

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/HEAD/54be7545)

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

... (truncated)

Changelog

Sourced from coveralls's changelog.

3.2.0 (2021-07-20)

Features

• api: support officially documented generic CI env vars (#300) (https://github.com/TheKevJames/coveralls-python/blob/master/ca1c6a47)

3.1.0 (2021-05-24)

Features

• cli: add --basedir and --submit options (#287) (https://github.com/TheKevJames/coveralls-python/blob/master/165a5cd1)
• github: push coverage info from tags (#284) (https://github.com/TheKevJames/coveralls-python/blob/master/0a49bd28)

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

... (truncated)

Commits

• 9ff9d4a chore(release): bump version
• ca1c6a4 feat(api): support officially documented generic CI env vars (#299) (#300)
• 56def53 chore(deps): update linter orb to v1.4.1 (#313)
• ee33d16 chore(deps): sidegrade orb to talkiq/linter
• 9f3fb47 tests(git): add test to cover not a git repository case (#311)
• ecc6a6e chore(deps): update precommit hook asottile/pyupgrade to v2.21.2 (#310)
• e652820 chore(deps): update precommit hook asottile/pyupgrade to v2.21.1 (#309)
• ab29ce1 chore(deps): update precommit hook asottile/pyupgrade to v2.21.0 (#308)
• b568038 chore(deps): update precommit hook asottile/pyupgrade to v2.20.0 (#307)
• bf5a03f chore(deps): update precommit hook asottile/pyupgrade to v2.19.4 (#305)
• 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.

---

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 use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@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 your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)