search

crisboarna / react-skillbars

Skill bars with full color customizations and responsive layout.
https://crisboarna.github.io/react-skillbars
MIT License
23 stars 13 forks source link

An in-range update of semantic-release is breaking the build 🚨 #193

Closed greenkeeper[bot] closed 2 years ago

greenkeeper[bot] commented 4 years ago

🚨 Reminder! Less than one month left to migrate your repositories over to Snyk before Greenkeeper says goodbye on June 3rd! 💜 🚚💨 💚

Find out how to migrate to Snyk at greenkeeper.io

The devDependency semantic-release was updated from 17.0.7 to 17.0.8.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details - ❌ **continuous-integration/travis-ci/push:** The Travis CI build could not complete due to an error ([Details](https://travis-ci.org/github/crisboarna/react-skillbars/builds/690711324?utm_source=github_status&utm_medium=notification)).
Release Notes for v17.0.8

17.0.8 (2020-05-24)

Bug Fixes

  • prevent false positive secret replacement for Golang projects (#1562) (eed1d3c)
Commits

The new version differs by 5 commits.

  • eed1d3c fix: prevent false positive secret replacement for Golang projects (#1562)
  • 5f3a8bb docs: Recommend using npx instead of installing globally (#1563)
  • 0ef52e7 docs: adjust minor typos (#1554)
  • a62bc7c docs(GitHub Actions): Add alternative trigger options (#1471)
  • 22321cf docs: update recipe for gitlab-ci with Node.js >=10.18

See the full diff

FAQ and help There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

greenkeeper[bot] commented 4 years ago

After pinning to 17.0.7 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.