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

An in-range update of ember-source is breaking the build 🚨 #284

Open
greenkeeper bot opened this issue Feb 14, 2018 · 1 comment
Open

An in-range update of ember-source is breaking the build 🚨 #284

greenkeeper bot opened this issue Feb 14, 2018 · 1 comment

Comments

@greenkeeper
Copy link

greenkeeper bot commented Feb 14, 2018

Version 2.18.1 of ember-source was just published.

Branch Build failing 🚨
Dependency ember-source
Current Version 2.18.0
Type devDependency

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

ember-source 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 failed Details

Commits

The new version differs by 12 commits.

  • 78717c5 Release v2.18.1.
  • 905dd01 Add v2.18.1 to CHANGELOG.md.
  • 8639d6a [BUGFIX lts] Enable some recovery of errors thrown during render.
  • 8d6600b [BUGFIX lts] Avoid excessively calling Glimmer AST transforms.
  • 6e0b9fd Add v2.17.1 to CHANGELOG.md
  • dcfb297 Add v2.16.2 to CHANGELOG.md.
  • 1f05c15 Ensure build-metadata.json is included in packed tarball.
  • c2b7d49 Publish metadata file to S3.
  • 2dc45b2 Merge pull request #16068 from rwjblue/update-backburner-release
  • 0e049fb [BUGFIX release] Update to backburner@1.3.5.
  • dee84b0 Fix incorrect .travis.yml config for release branch.
  • ca01684 Begin publishing npm tarballs to S3.

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
Author

greenkeeper bot commented Feb 14, 2018

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

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

No branches or pull requests

0 participants