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

semantic-release@6.3.6 breaks build 🚨 #105

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

Conversation

greenkeeperio-bot
Copy link
Contributor

🚨🔥⚠️ Action required: Switch to the new Greenkeeper now! 🚨🔥⚠️
This version of Greenkeper will be shutdown on May 31st.
With Integrations first-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.


Hello lovely humans,

semantic-release just published its new version 6.3.6.

State Failing tests 🚨
Dependency semantic-release
New version 6.3.6
Type devDependency

This version is covered by your current version range and after updating it in your project the build went from success to failure.

As semantic-release is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.

Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?

There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.

Good luck with your project ✨

You rock!

🌴


GitHub Release

<a name"6.3.6">

6.3.6 (2017-01-13)

Bug Fixes

  • package:
    • update github to version 8.0.0 (afd6ab75)
    • update nopt to version 4.0.0 (b10c8910)

The new version differs by 19 commits .

  • af90de9 Merge pull request #355 from semantic-release/dep-updates
  • aa012b3 Merge branch 'greenkeeper/tap-9.0.0' into dep-updates
  • 5724b19 Merge branch 'greenkeeper/github-8.0.0' into dep-updates
  • 97a8e73 Merge branch 'caribou' into greenkeeper/nopt-4.0.0
  • 51e12a3 docs(package): fix 'home' link
  • afd6ab7 fix(package): update github to version 8.0.0
  • f80e056 chore(package): update tap to version 9.0.0
  • b10c891 fix(package): update nopt to version 4.0.0
  • 3295f95 fix(package): update github to version 7.0.0
  • 6a172e1 docs(README.md): discourage use of pre-patch, pre-minor and pre-release
  • 68f9753 chore(package): update dependencies
  • 462c51d style: standard
  • cdf705c chore: update dependencies
  • 9a51b02 chore: update github client
  • 14618c8 chore(package): parse-github-repo-url

There are 19 commits in total. See the full diff.

@codecov-io
Copy link

codecov-io commented May 6, 2017

Codecov Report

Merging #105 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #105   +/-   ##
=======================================
  Coverage   93.81%   93.81%           
=======================================
  Files           9        9           
  Lines          97       97           
=======================================
  Hits           91       91           
  Misses          6        6

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5e3589b...9dabcd1. Read the comment docs.

@accraze accraze force-pushed the greenkeeper-semantic-release-6.3.6 branch from ad30d01 to 9dabcd1 Compare May 28, 2017 00:44
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

3 participants