search

HiFaraz / character

Authentication, SSO, user management, and overall identity solution for Node.js
MIT License
8 stars 0 forks source link

An in-range update of babel-preset-env is breaking the build 🚨 #16

Closed greenkeeper[bot] closed 7 years ago

greenkeeper[bot] commented 7 years ago

Version 1.6.0 of babel-preset-env just got published.

Branch Build failing 🚨
Dependency babel-preset-env
Current Version 1.5.2
Type devDependency

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

As babel-preset-env is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this :muscle:

Status Details - ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/HiFaraz/identity-desk/builds/250027241?utm_source=github_status&utm_medium=notification)
Release Notes v1.6.0

v1.6.0 (2017-07-04)

🚀 New Feature

We updated our mappings to support native trailing function commas and string paddings in Node.js 8+.

🐛 Bug Fix

We added support for using browserslist's chromeandroid in targets.

📝 Documentation

Thanks to @graingert and @pfiaux for pointing out some needed updates to the uglify-js-related docs.

Commits

The new version differs by 10 commits.

  • 8d09fa5 1.6.0
  • 6e06755 Update changelog
  • 9e3f5e8 Update yarn.lock
  • 0da8e7b Tweak uglify option docs (#368)
  • f5ee86f Merge pull request #367 from babel/chromeandroid
  • 9eb6b3b add test
  • 3c841bf Handle chromeandroid browserslist value.
  • fd11bb3 Bump compat-table for node8 support (#363)
  • d1b05fa add probot-stale [skip ci] (#353)
  • 240456f Update changelog for v1.5.2 [skip ci]

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

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