🚨 [security] Update handlebars 4.7.2 → 4.7.8 (patch) #117
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.
🚨 Your current dependencies have known security vulnerabilities 🚨
This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ handlebars (4.7.2 → 4.7.8) · Repo
Security Advisories 🚨
🚨 Prototype Pollution in handlebars
🚨 Remote code execution in handlebars when compiling templates
Release Notes
4.7.8
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 62 commits:
v4.7.8
Fix browser tests in CI pipeline
Test on Node 18
Make library compatible with workers
Fix sync issue with npm lock-file
Fix compiling of each block params in strict mode
Fix bundler issue with webpack 5
Fix integration-tests issue with npm >= 7
use https instead of git for mustache submodule
Fix typo
Use eslint-env "shared-node-browser" for shared handlebars code
Replace shields.io with faster badgen.net
Don't create security alerts for dev-dependencies
Replace custom test-server with Grunt connect
Fix rollup warning when importing Handlebars as ESM
Add integration-tests to CI workflow
Replace Saucelabs with Playwright
Move `print-script.js`-file in `tests`-folder
Move `integration-testing`-folder in `tests`-folder
Remove redundant `task`-part in `task-tests`-folder
Move `bench`-folder in `tests`-folder
Update repository URL
Update contributing guidelines
Run CI tests on more versions
Don't rely on Node.js `global` object
Replace Travis CI with GitHub action (#1772)
Fix Mustache links
v4.7.7
Update release notes
disable IE in Saucelabs tests
fix weird error in integration tests
fix: check prototype property access in strict-mode (#1736)
fix: escape property names in compat mode (#1736)
refator: In spec tests, use expectTemplate over equals and shouldThrow (#1683)
chore: start testing on Node.js 12 and 13
v4.7.6
Update release notes
Update release-notes.md
Switch cmd parser to latest minimist
Revert "chore: set Node.js compatibility to v6+"
v4.7.5
Update release notes
chore: downgrade yargs to v14
chore: set Node.js compatibility to v6+
test: fix integration tests
docs: update release-docs in CONTRIBUTING.md
v4.7.4
Update release notes
Use tmp directory for files written during tests
tasks/test-bin.js: Delete duplicate test
Revert "Update release-notes.md"
Update release-notes.md
chore: add unit tests for cli options (#1666)
fix: migrate from optimist to yargs (#1666)
chore: ignore external @types in tests
docs: fix comparison link
v4.7.3
Update release notes
Fixes spelling and punctuation
Add Type Definition for Handlebars.VERSION, Fixes #1647
Include Type Definition for runtime.js in Package
chore: add missing "await" in aws-s3 publishing code
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands