d-band / fef

Front-End Framework using react redux saga ( fork from dva )
2 stars 0 forks source link

An in-range update of redux-saga is breaking the build 🚨 #44

Open greenkeeper[bot] opened 7 years ago

greenkeeper[bot] commented 7 years ago

Version 0.15.1 of redux-saga just got published.

Branch Build failing 🚨
Dependency redux-saga
Current Version 0.15.0
Type dependency

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

redux-saga is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them. I recommend you give this issue a very high priority. I’m sure you can resolve this :muscle:

Status Details - ❌ **continuous-integration/travis-ci/push** The Travis CI build could not complete due to an error [Details](https://travis-ci.org/d-band/fef/builds/227905049?utm_source=github_status&utm_medium=notification)

Commits

The new version differs by 7 commits0.

  • df9d184 0.15.1
  • 1da517d Do not use Symbol internally, because 2 conflicting redux-saga versions wont match - i.e. effects created by old one wont be recognized by newer runtime (fixes #950)
  • 73bbf40 Wrap join/cancel effects with all
  • e14ae6f Some misc grammar fixes
  • b44b03a Update ForkModel.md
  • e8b49cb Activated loose mode for es2015 preset
  • 0d16912 Revamped docs

false

See the full diff

Not sure how things should work exactly? There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

greenkeeper[bot] commented 7 years ago

Version 0.15.2 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Release Notes v0.15.2
  • fixed problem with yielding falsy values - normally all non-interpretable yields are just injected back to your saga (const two = yield 2), however yielding falsy values prevented yielding saga to continue
Commits

The new version differs by 8 commits0.

  • 19fb2cc 0.15.2
  • 276e38b updated dist files
  • 3500c7b Inject yielded falsy values back just like any other non-interpretable values (fixes #961)
  • afcf5d4 Fixed deprecation warning which suggested default imports instead of named ones (fixes #959)
  • 40a638e Added release npm scripts
  • 85bcaa7 Remove old korean readme file
  • 733784b Change korean translation link
  • 535e079 Change way to get object keys to flexible

false

See the full diff

greenkeeper[bot] commented 7 years ago

Version 0.15.3 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Release Notes v0.15.3
  • fixed middleware's context not being passed to the root sagas (thanks @VictorQueiroz)
Commits

The new version differs by 8 commits0.

  • f86de7c 0.15.3
  • a9e44de Tweaked matchers.default
  • ab89fa4 edited docs comments
  • 600b848 Fixed bug in Retrying XHR calls recipe
  • 591d158 reworded context notes a little bit
  • 81d3582 add description to setContext() and getContext() effects on docs
  • 99940a2 fix misspelled effect name on docs
  • b09f9fa fix: always deliver “context” object to runSaga() function

false

See the full diff