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

Bump coveralls from 2.2.0 to 3.2.0 #8

Closed
wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Jul 24, 2021

Bumps coveralls from 2.2.0 to 3.2.0.

Release notes

Sourced from coveralls's releases.

3.2.0 (2021-07-20)

Features

3.1.0

3.1.0 (2021-05-24)

Features

3.0.1

3.0.1 (2021-03-02)

Bug Fixes

3.0.0

3.0.0 (2021-01-12)

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):

  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

3.1.0 (2021-05-24)

Features

3.0.1 (2021-03-02)

Bug Fixes

3.0.0 (2021-01-12)

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):

  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 compatibility score

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)

Bumps [coveralls](https://github.com/TheKevJames/coveralls-python) from 2.2.0 to 3.2.0.
- [Release notes](https://github.com/TheKevJames/coveralls-python/releases)
- [Changelog](https://github.com/TheKevJames/coveralls-python/blob/master/CHANGELOG.md)
- [Commits](TheKevJames/coveralls-python@2.2.0...3.2.0)

---
updated-dependencies:
- dependency-name: coveralls
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github
Copy link
Author

dependabot bot commented on behalf of github Jul 24, 2021

Dependabot tried to add @alwx as a reviewer to this PR, but received the following error from GitHub:

POST https://api.github.com/repos/kearnsw/rasa/pulls/8/requested_reviewers: 422 - Reviews may only be requested from collaborators. One or more of the users or teams you specified is not a collaborator of the kearnsw/rasa repository. // See: https://docs.github.com/rest/reference/pulls#request-reviewers-for-a-pull-request

@dependabot @github
Copy link
Author

dependabot bot commented on behalf of github Jul 24, 2021

The following labels could not be found: type:dependencies.

@dependabot @github
Copy link
Author

dependabot bot commented on behalf of github Jun 1, 2022

Superseded by #28.

@dependabot dependabot bot closed this Jun 1, 2022
@dependabot dependabot bot deleted the dependabot-pip-coveralls-3.2.0 branch June 1, 2022 13:15
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.

0 participants