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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update coveralls to the latest version 馃殌 #18

Merged
merged 1 commit into from
Mar 10, 2017

Conversation

greenkeeper[bot]
Copy link
Contributor

@greenkeeper greenkeeper bot commented Mar 5, 2017

Version 2.12.0 of coveralls just got published.

Dependency coveralls
Current Version 2.11.16
Type devDependency

The version 2.12.0 is not covered by your current version range.

Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

I recommend you look into these changes and try to get onto the latest version of coveralls.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.


Release Notes Branch coverage support

Adds branch coverage data to Coveralls API post.

Commits

The new version differs by 2 commits .

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 馃尨

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling fee5cf3 on greenkeeper/coveralls-2.12.0 into 36ccbd1 on master.

@zrrrzzt zrrrzzt merged commit 6b1e03c into master Mar 10, 2017
@zrrrzzt zrrrzzt deleted the greenkeeper/coveralls-2.12.0 branch March 10, 2017 19:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants