🚨 [security] Update ejs 3.1.7 → 3.1.10 (patch) #95
Conversation
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
![depfu[bot]](https://avatars.githubusercontent.com/in/715?s=60&v=4){kind=small}
depfu
bot
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
✳️ ejs (3.1.7 → 3.1.10) · Repo · Changelog
Security Advisories 🚨
🚨 ejs lacks certain pollution protection
Release Notes
3.1.10
3.1.9
3.1.8
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 33 commits:
Version 3.1.10Mocha TDDBasic pollution protectionMerge pull request #756 from Jeffrey-mu/mainInclude advanced usage examplesAdded headerMerge branch 'main' of github.com:mde/ejs into mainAdded security banner to READMEUpdate SECURITY.mdUpdate SECURITY.mdUpdate SECURITY.mdVersion 3.1.9Updated dev depsMerge pull request #707 from mde/dependabot/npm_and_yarn/minimatch-3.1.2Removed old changelog, please rely on git logMerge pull request #719 from jportner/frozen-prototype-fixFall back to assignment, update testChange approach to shadowing "toString" property for escapeXMLBump minimatch from 3.0.4 to 3.1.2Merge pull request #706 from mde/dependabot/npm_and_yarn/flat-and-mocha-5.0.2Bump flat and mochaMerge pull request #704 from mshima/patch-1Update README.mdroot can be arrays.Merge pull request #685 from mde/dependabot/npm_and_yarn/shell-quote-1.7.3Merge pull request #687 from i8-pi/cli-relative-pathMake relative paths in include work for cliBump shell-quote from 1.7.2 to 1.7.3Version bump in Express exampleVersion 3.1.8Merge branch 'main' of github.com:mde/ejs into mainMinor mitigationMerge pull request #664 from netcode/patch-1Commits
See the full diff on Github. The new version differs by 29 commits:
Version 3.2.5Update built fileswork around compiler quirkpath to config filerequireConfigFile: falseEnsure error objects are propagated without modification (#1920)Update .eslintrc.json to use es2021Run lint on node 20Run coverage on node 20Update Node version matrix in CIBump eslint from 8.35.0 to 8.52.0 (#1922)Bump @babel/core from 7.21.0 to 7.23.2 (#1923)Bump rollup from 2.79.1 to 4.2.0 (#1921)Bump @babel/eslint-parser from 7.19.1 to 7.22.15 (#1917)Bump chai from 4.3.7 to 4.3.10 (#1915)Bump karma from 6.4.1 to 6.4.2 (#1910)Bump yargs from 17.7.1 to 17.7.2 (#1909)Bump semver from 7.3.8 to 7.5.4 (#1906)Bump fs-extra from 10.1.0 to 11.1.1 (#1905)chore: updated babel/core to @babel/core (#1900)Bump eslint from 8.20.0 to 8.21.0 (#1857)Bump @babel/eslint-parser from 7.18.2 to 7.18.9 (#1858)Bump rollup from 2.75.7 to 2.77.2 (#1855)Bump jsdoc from 3.6.10 to 3.6.11 (#1856)Bump eslint from 8.17.0 to 8.20.0 (#1854)Bump karma from 6.3.20 to 6.4.0 (#1852)Bump rollup from 2.75.5 to 2.75.7 (#1853)fix: typo in jsdoc description for whilst (#1850)update docs for v3.2.4Commits
See the full diff on Github. The new version differs by 20 commits:
Version 10.8.7Removed stray logging statementsVersion 10.8.6Merge pull request #424 from martinholters/mh/fix_file_taskAdded lint taskRestore lint defaultAdd test for file task with multiple prereqsUpdate file_task.jsMerge pull request #421 from falsefalse/patch-1Bring back -q descriptionMerge pull request #420 from falsefalse/patch-1Fix jake -T for directory tasksMerge pull request #418 from jakejs/dependabot/npm_and_yarn/flat-and-mocha-5.0.2Bump flat and mochaMerge pull request #417 from llucasls/fix-directory-taskfix: add name to anonymous functiontest: check output of "jake -T" commandMerge pull request #414 from connerpierce/mainUpdated dependencies to include new filelist versionMerge pull request #413 from JackHowa/CHORE-remove-unused-imports👉 No CI detected
You don't seem to have any Continuous Integration service set up!
Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.
This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:
* [Circle CI](https://circleci.com), [Semaphore ](https://semaphoreci.com) and [Github Actions](https://docs.github.com/actions) are all excellent options. * If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github. * If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with `depfu/`.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