-
Notifications
You must be signed in to change notification settings - Fork 0
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 handlebars is breaking the build 🚨 #86
Comments
Version 4.0.8 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 4.0.9 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 10 commits.
See the full diff |
Version 4.0.10 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 4.0.11 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 7 commits.
See the full diff |
Your tests are still failing with this version. Compare changes CommitsThe new version differs by 33 commits.
There are 33 commits in total. See the full diff |
Your tests are still failing with this version. Compare changes CommitsThe new version differs by 20 commits.
There are 20 commits in total. See the full diff |
Your tests are still failing with this version. Compare changes CommitsThe new version differs by 10 commits.
See the full diff |
Version 4.0.7 of handlebars just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As handlebars 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
- ❌ **continuous-integration/travis-ci/push** The Travis CI build is in progress [Details](https://travis-ci.org/alsatian-test/alsatian-website/builds/227224628?utm_source=github_status&utm_medium=notification),- ❌ **continuous-integration/appveyor/branch** AppVeyor build failed [Details](https://ci.appveyor.com/project/jamesrichford/alsatian-website/build/1.0.0-199)Commits
The new version differs by 10 commits0.
606fa55
v4.0.7
8e09f0e
Update release-notes for 4.0.7
c8f4b57
Fix context-stack when calling block-helpers on null values
b617375
Parser: Change suffix to use ES6 default module export
63a8e0c
Add more tests for partial-blocks and inline partials
5a164d0
Fix for #1252: Using @partial-block twice in a template not possible
01b0f65
Avoid duplicate "sourceMappingURL=" lines.
406f2ee
require('sys') is deprecated, using 'util' instead
a023cb4
Make "column"-property of Errors enumerable
c7dc353
Testcase to verify that compile-errors have a column-property
false
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: