Skip to content
This repository has been archived by the owner on Jun 24, 2024. It is now read-only.

An in-range update of @asset-pipe/js-writer is breaking the build 🚨 #57

Open
greenkeeper bot opened this issue Dec 20, 2018 · 2 comments
Open

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Dec 20, 2018

The dependency @asset-pipe/js-writer was updated from 2.0.2 to 2.0.3.

🚨 View failing branch.

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

@asset-pipe/js-writer is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Release Notes for v2.0.3

2.0.3 (2018-12-20)

Bug Fixes

Commits

The new version differs by 4 commits.

  • 9fd72a9 fix: update deps to latest
  • 78b96ff chore(package): update eslint to version 5.0.1 (#96)
  • 8a400c8 chore(package): update semantic-release to version 15.1.4
  • ea95dc5 chore(package): update lint-staged to version 7.0.0

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Dec 20, 2018

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

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Aug 8, 2019

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Release Notes for v2.0.4

2.0.4 (2019-08-08)

Bug Fixes

  • match extensions config with js-reader (#104) (11c2335)
Commits

The new version differs by 2 commits.

  • 11c2335 fix: match extensions config with js-reader (#104)
  • 2f91d78 chore: test on node 10 and 11

See the full diff

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

0 participants