search

asset-pipe / integration

Integration verification module
Other
0 stars 0 forks source link

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

Closed greenkeeper[bot] closed 6 years ago

greenkeeper[bot] commented 6 years ago

Version 1.0.1 of @asset-pipe/js-reader was just published.

Branch Build failing 🚨
Dependency @asset-pipe/js-reader
Current Version 1.0.0
Type dependency

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

@asset-pipe/js-reader 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 failed [Details](https://travis-ci.org/asset-pipe/integration/builds/329836397?utm_source=github_status&utm_medium=notification)
Release Notes v1.0.1

1.0.1 (2018-01-17)

Bug Fixes

  • package: update browser-pack to version 6.0.3 (f8340c4)
Commits

The new version differs by 11 commits.

  • f8340c4 fix(package): update browser-pack to version 6.0.3
  • f44c7a6 chore: add semantic-release to repo
  • d2bbf41 chore: update repo tooling
  • cdd368c chore: add package lock file
  • 5d28fd2 chore(package): update prettier to version 1.10.2
  • ed6b3d2 chore(package): update all deps
  • 6c1cfb8 chore(package): update jest
  • 080235f chore(package): update prettier to version 1.9.2
  • ae6c3c8 chore(package): update prettier to version 1.9.1
  • 324529f chore(package): update prettier to version 1.9.0
  • 88a50a7 style: add lint rule for missing deps

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 6 years ago

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

greenkeeper[bot] commented 6 years ago

Version 2.0.0 just got published.

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

Release Notes v2.0.0

2.0.0 (2018-01-23)

Code Refactoring

  • rework bundle implementation (8c1d6a0)

Features

BREAKING CHANGES

  • Bundle output now differs in several ways from before
Commits

The new version differs by 16 commits.

  • 1a257ce refactor: remove dependency on get-stream
  • fc2ff2e refactor: fixes based on PR feedback
  • 250ee09 feat: add sourcemap support
  • 8a5e25d test: update snapshots
  • 0cab90f docs: update readme and code commenting
  • 7555614 test: remove test
  • e865afd chore: ignore mock files when linting
  • 43d0ea7 test: fix paths in snapshots, add test coverage
  • 57e7c5c test: improve test coverage
  • d610573 refactor: ensure api remains consistent
  • b27ad34 refactor: replace old reader impl with new
  • 8887ea1 test: add additional test coverage to reader2.js
  • 23500e3 refactor: unpack feeds then run browserify
  • 8c1d6a0 refactor: rework bundle implementation
  • 4ffb117 test: add failing test for deduping issue

There are 16 commits in total.

See the full diff