chore(deps): update dependency handlebars.js to v4.7.7
This MR contains the following updates:
Package | Update | Change |
---|---|---|
handlebars.js (source) | minor |
4.1.1 -> 4.7.7
|
Release Notes
wycats/handlebars.js
v4.7.7
- fix weird error in integration tests -
eb860c0
- fix: check prototype property access in strict-mode (#1736) -
b6d3de7
- fix: escape property names in compat mode (#1736) -
f058970
- refactor: In spec tests, use expectTemplate over equals and shouldThrow (#1683) -
77825f8
- chore: start testing on Node.js 12 and 13 -
3789a30
(POSSIBLY) BREAKING CHANGES:
- the changes from version 4.6.0 now also apply in when using the compile-option "strict: true". Access to prototype properties is forbidden completely by default, specific properties or methods can be allowed via runtime-options. See #1633 for details. If you are using Handlebars as documented, you should not be accessing prototype properties from your template anyway, so the changes should not be a problem for you. Only the use of undocumented features can break your build.
That is why we only bump the patch version despite mentioning breaking changes.
v4.7.6
Chore/Housekeeping:
- #1672 - Switch cmd parser to latest minimist (@dougwilson
Compatibility notes:
- Restored Node.js compatibility
v4.7.5
Chore/Housekeeping:
- ~Node.js version support has been changed to v6+~ Reverted in 4.7.6
Compatibility notes:
- ~Node.js < v6 is no longer supported~ Reverted in 4.7.6
v4.7.4
Chore/Housekeeping:
- #1666 - Replaced minimist with yargs for handlebars CLI (@aorinevo, @AviVahl & @fabb)
Compatibility notes:
- No incompatibilities are to be expected
v4.7.3
Chore/Housekeeping:
- #1644 - Download links to aws broken on handlebarsjs.com - access denied (@Tea56)
- Fix spelling and punctuation in changelog -
d78cc73
Bugfixes:
- Add Type Definition for Handlebars.VERSION, Fixes #1647 -
4de51fe
- Include Type Definition for runtime.js in Package -
a32d05f
Compatibility notes:
- No incompatibilities are to be expected
v4.7.2
Bugfixes:
Chore/Build:
- chore: execute saucelabs-task only if access-key exists -
a4fd391
Compatibility notes:
- No breaking changes are to be expected
v4.7.1
Bugfixes:
- fix: fix log output in case of illegal property access -
f152dfc
- fix: log error for illegal property access only once per property -
3c1e252
Compatibility notes:
- no incompatibilities are to be expected.
v4.7.0
Features:
- feat: default options for controlling proto access -
7af1c12
, #1635- This makes it possible to disable the prototype access restrictions added in 4.6.0
- an error is logged in the console, if access to prototype properties is attempted and denied and no explicit configuration has taken place.
Compatibility notes:
- no compatibilities are expected
v4.6.0
Features:
Bugfixes:
Chores, docs:
- various refactorings and improvements to tests -
d7f0dcf
,187d611
,d337f40
- modernize the build-setup
- use prettier to format and eslint to verify -
c40d9f3
,8901c28
,e97685e
,1f61f21
- use nyc instead of istanbul to collect coverage -
164b7ff
,1ebce2b
- update build code to use modern javascript and make it cleaner -
14b621c
,1ec1737
,3a5b65e
,dde108e
,04b1984
,587e7a3
- restructur build commands -
e913dc5
,
- use prettier to format and eslint to verify -
- eslint rule changes -
ac4655e
,dc54952
- Update (C) year in the LICENSE file -
d1fb07b
- chore: try to fix saucelabs credentials (#1627) -
- Update readme.md with updated links (#1620) -
edcc84f
BREAKING CHANGES:
-
access to prototype properties is forbidden completely by default, specific properties or methods can be allowed via runtime-options. See #1633 for details. If you are using Handlebars as documented, you should not be accessing prototype properties from your template anyway, so the changes should not be a problem for you. Only the use of undocumented features can break your build.
That is why we only bump the minor version despite mentioning breaking changes.
v4.5.3
Bugfixes:
- fix: add "no-prototype-builtins" eslint-rule and fix all occurences -
f7f05d7
- fix: add more properties required to be enumerable -
1988878
Chores / Build:
- fix: use !== 0 instead of != 0 -
c02b05f
- add chai and dirty-chai and sinon, for cleaner test-assertions and spies,
deprecate old assertion-methods -
93e284e
,886ba86
,0817dad
,93516a0
Security:
- The properties
__proto__
,__defineGetter__
,__defineSetter__
and__lookupGetter__
have been added to the list of "properties that must be enumerable". If a property by that name is found and not enumerable on its parent, it will silently evaluate toundefined
. This is done in both the compiled template and the "lookup"-helper. This will prevent new Remote-Code-Execution exploits that have been published recently.
Compatibility notes:
- Due to the security-fixes. The semantics of the templates using
__proto__
,__defineGetter__
,__defineSetter__
and__lookupGetter__
in the respect that those expression now returnundefined
rather than their actual value from the proto. - The semantics have not changed in cases where the properties are enumerable, as in:
{
__proto__: 'some string';
}
- The change may be breaking in that respect, but we still only increase the patch-version, because the incompatible use-cases are not intended, undocumented and far less important than fixing Remote-Code-Execution exploits on existing systems.
v4.5.2
v4.5.1
Bugfixs
Compatibility notes:
- No compatibility issues are to be expected
v4.5.0
Features / Improvements
- Add method Handlebars.parseWithoutProcessing (#1584) -
62ed3c2
- add guard to if & unless helpers (#1549)
- show source location for the strict lookup exceptions -
feb60f8
Bugfixes:
- Use objects for hash value tracking -
7fcf9d2
Chore:
- Resolve deprecation warning message from eslint while running eslint (#1586) -
7052e88
- chore: add eslint-plugin-compat and eslint-plugin-es5 -
088e618
Compatibility notes:
- No compatibility issues are to be expected
v4.4.5
Bugfixes:
v4.4.4
Bugfixes:
Chore:
- chore: link to s3 bucket with https, add "npm ci" to build instructions -
0b593bf
Compatibility notes:
- no compatibility issues are expected
v4.4.3
Bugfixes
Typings:
- add missing type fields to AST typings and add tests for them -
0440af2
v4.4.2
- chore: fix grunt-saucelabs dependency -
b7eada0
v4.4.1
- #1562 - Error message for syntax error missing location in 4.2.1+
v4.4.0
v4.3.5
v4.3.4
- fix: harden "propertyIsEnumerable"-check -
ff4d827
Compatibility notes:
- No incompatibilities are known.
v4.3.3
- fix test case for browsers that do not support defineGetter -
8742bde
v4.3.2
Compatibility notes:
- There are no breaking changes
v4.3.1
Fixes:
- do not break on precompiled templates from Handlebars >=4.0.0 <4.3.0 -
1266838
, #1561 - Ensure allowCallsToHelperMissing runtime option is optional in typings -
93444c5
,64ecb9e
, #1560
v4.3.0
Fixes:
- Security: Disallow calling "helperMissing" and "blockHelperMissing" directly -
2078c72
- Disallow calling "helperMissing" and "blockHelperMissing" directly -
2078c72
Features:
- Add new runtime option
allowCallsToHelperMissing
to allow callingblockHelperMissing
andhelperMissing
.
Breaking changes:
Compatibility notes:
-
Compiler revision increased -
06b7224
- This means that template compiled with versions prior to 4.3.0 will not work with runtimes >= 4.3.0 The increase was done because the "helperMissing" and "blockHelperMissing" are now moved from the helpers to the internal "container.hooks" object, so old templates will not be able to call them anymore. We suggest that you always recompile your templates with the latest compiler in your build pipelines.
-
Disallow calling "helperMissing" and "blockHelperMissing" directly -
2078c72
- Calling "helperMissing" and "blockHelperMissing" directly from a template (like in
{{blockHelperMissing}}
was never intended and was part of the exploits that have been revealed early in 2019 (see https://github.com/wycats/handlebars.js/issues/1495). It is also part of a new exploit that is not captured by the earlier fix. In order to harden Handlebars against such exploits, calling thos helpers is now not possible anymore. Overriding those helpers is still possible. - If you really need this behavior, you can set the runtime option
allowCallsToHelperMissing
totrue
and the calls will again be possible
- Calling "helperMissing" and "blockHelperMissing" directly from a template (like in
Both bullet points imly that Handlebars is not 100% percent compatible to 4.2.0, despite the minor version bump.
We consider it more important to resolve a major security issue than to maintain 100% compatibility.
v4.2.2
v4.2.1
Bugfixes:
- The "browser" property in the package.json has been updated to use the common-js builds instead of the minified UMD -
c55a7be
, #1553
Compatibility notes:
- No compatibility issues should arise
v4.2.0
Chore/Test:
- Use custom
grunt-saucelab
with current sauce-connect proxy -f119497
- Add framework for various integration tests -
f9cce4d
- Add integration test for webpack -
a57b682
Bugfixes:
-
#1544 - Typescript types:
knownHelpers
doesnt allow for custom helpers (@NickCis) - #1534 - Add typings for "Handlebars.VM.resolvePartial (@AndrewLeedham)
Features:
Compatibility notes:
- The new "browser"-property should not break anything, but you can never be sure. The integration test for webpack shows that it works, but if it doesn't please open an issue.
v4.1.2
#1540 - added browser to package.json, resolves #1102 (@ouijan)
Compatibility notes:
- We are not sure if imports via webpack are still working, which is why this release is a pre-release
Configuration
-
If you want to rebase/retry this MR, check this box.
This MR has been generated by Renovate Bot.