chore(deps): update dependency gh-pages to v5 [security]

[renovate]

Coming soon: The Renovate bot (GitHub App) will be renamed to Mend. PRs from Renovate will soon appear from 'Mend'. Learn more here.

This PR contains the following updates:

Package	Change	Age	Confidence
gh-pages	^1.2.0 -> ^5.0.0

GitHub Vulnerability Alerts

CVE-2022-37611

Prototype pollution vulnerability in tschaub gh-pages via the partial variable in util.js.

---

Release Notes

tschaub/gh-pages (gh-pages)

v5.0.0

Compare Source

Potentially breaking change: the publish method now always returns a promise. Previously, it did not return a promise in some error cases. This should not impact most users.

Updates to the development dependencies required a minimum Node version of 14 for the tests. The library should still work on Node 12, but tests are no longer run in CI for version 12. A future major version of the library may drop support for version 12 altogether.

• #​438 - Remove quotation marks (@​Vicropht)
• #​459 - Bump async from 2.6.4 to 3.2.4 (@​tschaub)
• #​454 - Bump email-addresses from 3.0.1 to 5.0.0 (@​tschaub)
• #​455 - Bump actions/setup-node from 1 to 3 (@​tschaub)
• #​453 - Bump actions/checkout from 2 to 3 (@​tschaub)
• #​445 - Update README to clarify project site configuration requirements with tools like CRA, webpack, Vite, etc. (@​Nezteb)
• #​452 - Assorted updates (@​tschaub)

v4.0.0

Compare Source

This release doesn't include any breaking changes, but due to updated development dependencies, tests are no longer run on Node 10.

• #​432 - Updated dev dependencies and formatting (@​tschaub)
• #​430 - Bump ansi-regex from 3.0.0 to 3.0.1 (@​tschaub)
• #​431 - Bump path-parse from 1.0.6 to 1.0.7 (@​tschaub)
• #​427 - Bump async from 2.6.1 to 2.6.4 (@​tschaub)
• #​423 - Bump minimist from 1.2.5 to 1.2.6 (@​tschaub)

v3.2.3

Compare Source

• #​398 - Update glob-parent (@​tschaub)
• #​395 - Switch from filenamify-url to filenamify (@​tw0517tw)

v3.2.2

Compare Source

• #​396 - Revert "security(deps): bump filenamify-url to 2.1.1" (@​tschaub)

v3.2.1

Compare Source

• #​393 - security(deps): bump filenamify-url to 2.1.1 (@​AviVahl)

v3.2.0

Compare Source

This release updates a few development dependencies and adds a bit of documentation.

• #​391 - Update dev dependencies (@​tschaub)
• #​375 - Add note about domain problem (@​demee)
• #​390 - Fix little typo in the README (@​cizordj)
• #​388 - Bump hosted-git-info from 2.8.8 to 2.8.9 (@​tschaub)
• #​387 - Bump y18n from 4.0.0 to 4.0.3 (@​tschaub)
• #​378 - Add GitHub Actions tips to readme.md (@​mickelsonmichael)
• #​386 - Bump lodash from 4.17.14 to 4.17.21 (@​tschaub)

v3.1.0

Compare Source

The cache directory used by gh-pages is now node_modules/.cache/gh-pages. If you want to use a different location, set the CACHE_DIR environment variable.

• #​362 - Move the cache directory (@​tschaub)
• #​361 - Update dev dependencies (@​tschaub)

v3.0.0

Compare Source

Breaking changes:

None really. But tests are no longer run on Node < 10. Development dependencies were updated to address security warnings, and this meant tests could no longer be run on Node 6 or 8. If you still use these Node versions, you may still be able to use this library, but be warned that tests are no longer run on these versions.

All changes:

• #​357 - Dev dependency updates (@​tschaub)
• #​333 - Update readme with command line options (@​Victoire44)
• #​356 - Test as a GitHub action (@​tschaub)
• #​355 - feat(beforeAdd): allow custom script before git add (@​Xiphe)
• #​336 - Fix remove not working properly (@​sunghwan2789)
• #​328 - Update .travis.yml (@​XhmikosR)
• #​327 - Fix typo (@​d-tsuji)

v2.2.0

Compare Source

• #​318 - Allow an absolute path as dist directory (@​okuryu)
• #​319 - Added 'remove' documentation to the readme (@​Sag-Dev)
• #​323 - Update dependencies (@​tschaub)
• #​277 - Add --no-history flag not to preserve deploy history (@​dplusic)

v2.1.1

Compare Source

• #​312 - Add default for '--git' option (@​tschaub)

v2.1.0

Compare Source

• #​307 - Dev dependency updates (@​tschaub)
• #​303 - Support '--git' CLI option (@​JRJurman)

v2.0.1

Compare Source

• #​268 - Continue even if no git configured user.

v2.0.0

Compare Source

Breaking changes:

• Requires Node 6 and above. If you require support for Node 4, stick with v1.2.0.

• The git user for commits is determined by running git config user.name and git config user.email in the current working directory when gh-pages is run. Ideally, this is what you want. In v1, the git user was determined based on the gh-pages install directory. If the package was installed globally, the git user might not have been what you expected when running in a directory with a locally configured git user.

• #​264 - Better user handling (thanks @​holloway for getting this going and @​nuklearfiziks and @​paulirish for pushing it over the edge)

• #​263 - Infra: newer syntax and upgrade deps to latest stable versions (@​AviVahl)

---

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 is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	shell-quote@​1.7.2
	merge-deep@​3.0.2
	url-parse@​1.4.7
	eventsource@​1.0.7
	form-data@​3.0.1 ⏵ 2.3.3	+1
	@​babel/​traverse@​7.23.2 ⏵ 7.20.1	+1	-75
	react-error-overlay@​6.0.11
	side-channel@​1.0.4
	util.promisify@​1.0.0
	mamacro@​0.0.3
	tty-browserify@​0.0.0
	jsonify@​0.0.0
	isarray@​2.0.5 ⏵ 1.0.0	+1		+21
	string.prototype.trimleft@​2.1.1
	string.prototype.trimright@​2.1.1
	safe-regex-test@​1.0.0
	abab@​2.0.6 ⏵ 2.0.3	+1
	object.fromentries@​2.0.6
	array-flatten@​2.1.2
	path-parse@​1.0.6
	harmony-reflect@​1.6.1
	object.getownpropertydescriptors@​2.1.0
	deep-equal@​2.2.0 ⏵ 1.1.1	+1		-7
	unbox-primitive@​1.0.2
	internal-slot@​1.0.5 ⏵ 1.0.3	+1		-2
	object.entries@​1.1.6
	object.values@​1.1.1
	array-includes@​3.1.6 ⏵ 3.1.1	+1		-1
	string.prototype.matchall@​4.0.8
	is-string@​1.0.7 ⏵ 1.0.5	+1		+1
	regexp.prototype.flags@​1.4.3
	object.assign@​4.1.0
	string.prototype.trimstart@​1.0.6
See 654 more rows in the dashboard

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		@babel/[email protected] has a Critical CVE. CVE: GHSA-67hx-6x53-jw92 Babel vulnerable to arbitrary code execution when compiling specifically crafted malicious code (CRITICAL) Affected versions: < 7.23.2; >= 8.0.0-alpha.0 < 8.0.0-alpha.4 Patched version: 7.23.2 From: package-lock.json → npm/@babel/[email protected] ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@babel/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		[email protected] has a Critical CVE. CVE: GHSA-6h5x-7c5m-7cr7 Exposure of Sensitive Information in eventsource (CRITICAL) Affected versions: < 1.1.1; >= 2.0.0 < 2.0.2 Patched version: 1.1.1 From: demo/yarn.lock → npm/[email protected] ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		[email protected] has a Critical CVE. CVE: GHSA-76p3-8jx3-jpfq Prototype pollution in webpack loader-utils (CRITICAL) Affected versions: >= 2.0.0 < 2.0.3; < 1.4.1 Patched version: 1.4.1 From: demo/yarn.lock → npm/[email protected] → npm/[email protected] ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		[email protected] has a Critical CVE. CVE: GHSA-r6rj-9ch6-g264 Prototype pollution in Merge-deep (CRITICAL) Affected versions: < 3.0.3 Patched version: 3.0.3 From: demo/yarn.lock → npm/[email protected] ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		[email protected] has a Critical CVE. CVE: GHSA-g4rg-993r-mgx7 Improper Neutralization of Special Elements used in a Command in Shell-quote (CRITICAL) Affected versions: < 1.7.3 Patched version: 1.7.3 From: package-lock.json → npm/[email protected] ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		[email protected] has a Critical CVE. CVE: GHSA-hgjh-723h-mx2j Authorization Bypass Through User-Controlled Key in url-parse (CRITICAL) Affected versions: < 1.5.8 Patched version: 1.5.8 From: package-lock.json → npm/[email protected] ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		[email protected] is Protestware or potentially unwanted behavior. Note: This package prints a protestware console message on install regarding Ukraine for users with Russian language locale From: demo/yarn.lock → npm/[email protected] ℹ Read more on: This package | This alert | What is protestware? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Consider that consuming this package may come along with functionality unrelated to its primary purpose. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report