You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
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.
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
![renovate-pagopa[bot]](https://avatars.githubusercontent.com/u/57742367?s=60&v=4){kind=small}
renovate-pagopa
bot
force-pushed
the
renovate/handlebars-to-4.7.7
branch
from
This PR contains the following updates:
~4.5.3->~4.7.0For further information on security, please refer to the Confluence page link
Release Notes
handlebars-lang/handlebars.js (handlebars)
v4.7.7Compare Source
eb860c0b6d3de7f05897077825f83789a30(POSSIBLY) BREAKING CHANGES:
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.
Commits
v4.7.6Compare Source
Chore/Housekeeping:
Compatibility notes:
Commits
v4.7.5Compare Source
Chore/Housekeeping:
Compatibility notes:
Commits
v4.7.4Compare Source
Chore/Housekeeping:
Compatibility notes:
Commits
v4.7.3Compare Source
Chore/Housekeeping:
d78cc73Bugfixes:
4de51fea32d05fCompatibility notes:
Commits
v4.7.2Compare Source
Bugfixes:
9d5aa36, #1639Chore/Build:
a4fd391Compatibility notes:
Commits
v4.7.1Compare Source
Bugfixes:
f152dfc3c1e252Compatibility notes:
Commits
v4.7.0Compare Source
Features:
7af1c12, #1635and no explicit configuration has taken place.
Compatibility notes:
Commits
v4.6.0Compare Source
Features:
d03b6ecBugfixes:
23d58e7Chores, docs:
d7f0dcf,187d611,d337f40c40d9f3,8901c28,e97685e,1f61f21164b7ff,1ebce2b14b621c,1ec1737,3a5b65e,dde108e,04b1984,587e7a3e913dc5,ac4655e,dc54952d1fb07bedcc84fBREAKING 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.
Commits
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.