-
Notifications
You must be signed in to change notification settings - Fork 11
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-browserify is breaking the build 🚨 #67
Comments
After pinning to 1.1.13 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results. |
Version 1.2.0 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 |
Version 1.2.1 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 |
Version 1.2.2 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 9 commits.
See the full diff |
Version 1.1.14 of ember-browserify just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As ember-browserify 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 💪
Status Details
Commits
The new version differs by 7 commits.
1f689b8
release v1.1.14 🎉
ee8f7fa
Merge pull request #119 from Kerrick/upgrade-acorn
0dd24b8
Upgrade acorn to v5.x
e249253
node 6 (lts)
f016379
Merge commit 'refs/pull/117/head' of github.com:ef4/ember-browserify
f010c2f
drop old node version from travis
27b7504
Changing error message on invalid syntax
See the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
The text was updated successfully, but these errors were encountered: