🚨 [security] Update pug 3.0.0 → 3.0.4 (patch)#172
Open
depfu[bot] wants to merge 1 commit intomasterfrom
Open
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
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?
✳️ pug (3.0.0 → 3.0.4) · Repo · Changelog
Security Advisories 🚨
🚨 Pug allows JavaScript code execution if an application accepts untrusted input
🚨 Remote code execution via the `pretty` option.
Release Notes
Too many releases to show here. View the full release notes.
Commits
See the full diff on Github. The new version differs by 15 commits:
v7.29.0fix(parser): correctly parse type assertions in `extends` clause (#17765)[7.x backport] feat: Allow specifying startLine in code frame (#17739)Move changelog up to v7.28.5 to separate file (#17754)[7.x backport] Add attributes import declaration builder (#17750)fix(traverse): provide a hub when traversing a File or Program and no parentPath is given (#17708)[7.x backport] fix: Rename switch discriminant references when body creates shadowing variable (#17737)[7.x backport] fix(parser): improve super type argument parsing (#17723)[7.x backport] feat(standalone): export async transform (#17663)Update polyfill packages (#17727)[7.x backport] feat: read standalone targets from data-targets (#17725)[babel 7] Delete Babel 8 fixtures (#17729)chore(Babel 7): ignore browserslist old data (#17724)[Babel 7] Improve generator performance (#17642)Add v7.28.6 to CHANGELOG.md [skip ci]Release Notes
Too many releases to show here. View the full release notes.
Commits
See the full diff on Github. The new version differs by 15 commits:
v7.29.0fix(parser): correctly parse type assertions in `extends` clause (#17765)[7.x backport] feat: Allow specifying startLine in code frame (#17739)Move changelog up to v7.28.5 to separate file (#17754)[7.x backport] Add attributes import declaration builder (#17750)fix(traverse): provide a hub when traversing a File or Program and no parentPath is given (#17708)[7.x backport] fix: Rename switch discriminant references when body creates shadowing variable (#17737)[7.x backport] fix(parser): improve super type argument parsing (#17723)[7.x backport] feat(standalone): export async transform (#17663)Update polyfill packages (#17727)[7.x backport] feat: read standalone targets from data-targets (#17725)[babel 7] Delete Babel 8 fixtures (#17729)chore(Babel 7): ignore browserslist old data (#17724)[Babel 7] Improve generator performance (#17642)Add v7.28.6 to CHANGELOG.md [skip ci]Release Notes
1.1.0 (from changelog)
1.0.3 (from changelog)
1.0.2 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 44 commits:
v1.1.0[New] add types[Dev Deps] add missing peer dep[Dev Deps] update `auto-changelog`, `core-js`, `tape`[actions] update workflows[Tests] replace `aud` with `npm audit`[actions] further shard; update action deps[Dev Deps] update `@ljharb/eslint-config`, `aud`, `tape`[Dev Deps] update `npmignore`[meta] use `npmignore` to autogenerate an npmignore file[Dev Deps] update `eslint`, `@ljharb/eslint-config`, `aud`, `tape`[actions] update rebase action to use reusable workflowv1.0.3[Dev Deps] update `eslint`, `@ljharb/eslint-config`, `aud`, `auto-changelog`, `tape`[meta] add `bugs` and `homepage` fields; reorder package.json[actions] reuse common workflows[Dev Deps] update `eslint`, `@ljharb/eslint-config`, `safe-publish-latest`, `tape`[actions] update codecov uploader[Dev Deps] update `eslint`, `tape`[Tests] test on all 16 minors[readme] add actions and codecov badges[Dev Deps] update `eslint`, `auto-changelog`[Dev Deps] update `eslint`, `@ljharb/eslint-config`, `aud`, `tape`[actions] use `node/install` instead of `node/run`; use `codecov` action[meta] use `prepublishOnly` script for npm 7+v1.0.2[Fix] use a universal way to get the original Symbol[readme] remove unused testling URLs[Dev Deps] update `eslint`, `@ljharb/eslint-config`, `aud`, `tape`[meta] do not publish github action workflow files[Dev Deps] update `eslint`, `@ljharb/eslint-config`, `aud`, `auto-changelog`, `core-js`, `get-own-property-symbols`[readme] fix repo URLs, remove defunct badges[Tests] migrate tests to Github Actions[Tests] fix linting errors[Tests] run `nyc` on all tests[actions] add "Allow Edits" workflow[actions] switch Automatic Rebase workflow to `pull_request_target` event[Dev Deps] update `eslint`, `@ljharb/eslint-config`, `aud`, `tape`[Dev Deps] update `auto-changelog`; add `aud`[Tests] only audit prod deps[Dev Deps] update `auto-changelog`, `tape`[Dev Deps] update `@ljharb/eslint-config`[Dev Deps] update `eslint`, `@ljharb/eslint-config`, `tape`[Dev Deps] update `eslint`, `@ljharb/eslint-config`, `core-js`Release Notes
1.2.1 (from changelog)
1.2.0 (from changelog)
1.1.4 (from changelog)
1.1.3 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 47 commits:
v1.2.1[Refactor] use `call-bound` directly[Deps] update `call-bind`, `gopd`[Dev Deps] update `@arethetypeswrong/cli`, `@ljharb/tsconfig`v1.2.0[New] add types[Deps] update `gopd`[Dev Deps] update `core-js`[Refactor] reorganize code[Refactor] use `hasown`[actions] split out node 10-20, and 20+[Dev Deps] add missing peer dep[Tests] allow tests to pass if zero traps are triggered[Deps] update `call-bind`, `has-tostringtag`[Dev Deps] update `@ljharb/eslint-config`, `auto-changelog`, `core-js`, `npmignore`, `tape`[Tests] replace `aud` with `npm audit`[meta] use `npmignore` to autogenerate an npmignore file[Tests] use `for-each` instead of `foreach`[Dev Deps] update `eslint`, `@ljharb/eslint-config`, `aud`, `auto-changelog`, `core-js`, `foreach`, `tape`[actions] update rebase action to use reusable workflow[Dev Deps] update `eslint`, `@ljharb/eslint-config`, `aud`, `core-js`, `tape`[meta] better `eccheck` command[actions] reuse common workflows[Dev Deps] update `eslint`, `@ljharb/eslint-config`, `safe-publish-latest`, `tape`[actions] update codecov uploaderv1.1.4[Dev Deps] update `auto-changelog`, `core-js`, `eslint`, `tape`[Refactor] use `has-tostringtag` to behave correctly in the presence of symbol shamsv1.1.3[Fix] do not use `Object.prototype.toString` when `Symbol.toStringTag` is shammed[Deps] update `has-symbols`[Dev Deps] update `eslint`, `@ljharb/eslint-config`, `aud`, `tape`[readme] add actions and codecov badges[actions] use `node/install` instead of `node/run`; use `codecov` action[meta] use `prepublishOnly` script for npm 7+v1.1.2[Robustness] use `call-bind`[meta] do not publish github action workflow files[readme] fix repo URLs; remove travis badge[Dev Deps] update `eslint`, `@ljharb/eslint-config`, `tape`[meta] gitignore coverage output[actions] update workflows[Dev Deps] update `eslint`, `@ljharb/eslint-config`, `aud`, `auto-changelog`[Tests] migrate tests to Github Actions[Tests] run `nyc` on all tests[actions] add "Allow Edits" workflow[actions] switch Automatic Rebase workflow to `pull_request_target` eventSecurity Advisories 🚨
🚨 Pug allows JavaScript code execution if an application accepts untrusted input
🚨 Remote code execution via the `pretty` option.
🆕 @babel/helper-string-parser (added, 7.27.1)
🆕 call-bind-apply-helpers (added, 1.0.2)
🆕 call-bound (added, 1.0.4)
🆕 dunder-proto (added, 1.0.1)
🆕 es-define-property (added, 1.0.1)
🆕 es-errors (added, 1.3.0)
🆕 es-object-atoms (added, 1.1.1)
🆕 function-bind (added, 1.1.2)
🆕 get-intrinsic (added, 1.3.0)
🆕 get-proto (added, 1.0.1)
🆕 gopd (added, 1.2.0)
🆕 has-tostringtag (added, 1.0.2)
🆕 hasown (added, 2.0.2)
🆕 math-intrinsics (added, 1.1.0)
🗑️ lodash (removed)
🗑️ to-fast-properties (removed)
👉 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