🚨🔥⚠️ Action required: Switch to the new Greenkeeper now! 🚨🔥⚠️
This version of Greenkeper will be shutdown on May 31st.
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.
This version is covered by your current version range and after updating it in your project the build went from success to failure.
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:
Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
We were originally waiting on 2.x for a breaking change, but since node v7.10
and other targets are causing some pain, we decided to land a backwards
compatible version.
🏠 Internal
Backport: use preset-env and remove flow-strip-types (#324) (@yavorsky)
Hello lovely humans,
babel-preset-env just published its new version 1.5.0.
This version is covered by your current version range and after updating it in your project the build went from success to failure.
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:
Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
GitHub Release
v1.5.0 (2017-05-19)
We were originally waiting on 2.x for a breaking change, but since node v7.10
and other targets are causing some pain, we decided to land a backwards
compatible version.
The new version differs by 147 commits .
d9372611.5.0590bfb5Update changelog for v1.5 [skip ci]ddea7c8Merge pull request #321 from babel/backport-string-versions6bc5326Backport: use preset-env and remove flow-strip-types (#324)c7d0e17Merge branch 'master' into backport-string-versionsfd35519Merge pull request #329 from babel/bump-electron8fb2222Use ensureDirSync in smoke test58055c8Support target versions as strings (#231)78ed702Bump electron-to-chromiumabdbeecTweak version mappings to match compat-table updates (#323)0e917deBump browserslist. (#319)20ddb72Bump compat-table (#307)966922dAdd debug-fixtures and test/tmp to .eslintignore (#305)db5daffRemove hidden files from debug fixtures targets. (#287)125e9281.4.0There are 147 commits in total. See the full diff.