Repository navigation
chore(deps-dev): bump serialize-javascript from 7.0.7 to 7.1.4 - #7
Conversation
Bumps [serialize-javascript](https://github.com/yahoo/serialize-javascript) from 7.0.7 to 7.1.4. - [Release notes](https://github.com/yahoo/serialize-javascript/releases) - [Commits](yahoo/serialize-javascript@v7.0.7...v7.1.4) --- updated-dependencies: - dependency-name: serialize-javascript dependency-version: 7.1.4 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.OpenSSF Scorecard
Scanned Files
|
veillette
left a comment
There was a problem hiding this comment.
Lockfile-only bump of the transitive dev dependency serialize-javascript from 7.0.7 to 7.1.4. It comes in through @rollup/plugin-terser. package.json is unchanged.
7.1.4 includes the fix for GHSA-m5mm-p8h7-m29v (low): cross-site scripting from an unescaped </script at the end of a serialized function body, which affects versions before 7.1.3. The release also serializes methods correctly when their bodies contain a nested function or arrow.
The diff is the version, resolved URL, and integrity hash in package-lock.json. On the earliest of these pull requests, compliance and dependency review passed. Build and CodeQL were still queued.
Bumps serialize-javascript from 7.0.7 to 7.1.4.
Release notes
Sourced from serialize-javascript's releases.
... (truncated)
Commits
05c5cebrelease: v7.1.4 (#238)fdb853dFix methods containing nested functions and arrows (#231)f7dfeaedocs: add SECURITY.md pointing to private vulnerability reporting (#237)4d36b82release: v7.1.3 (#236)45e5397fix: ignore functions without mutating input objects (#233)e978a1bfix: serialize Dates with expanded ISO years (#232)2864b3cfix: escape</scriptat the end of a serialized function body (#235)6a73fa1release: v7.1.22bdbaafMerge commit from fork8c8caa7release: v7.1.1Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.