Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
renovate wants to merge 1 commit into from
Closed

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

renovate wants to merge 1 commit into from

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Aug 13, 2025 •
edited
Loading

This PR contains the following updates:

Package Change Age Confidence
gh-pages 0.12.0 -> 5.0.0 age confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

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.

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.

v3.2.3

Compare Source

v3.2.2

Compare Source

v3.2.1

Compare Source

v3.2.0

Compare Source

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

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.

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:

v2.2.0

Compare Source

v2.1.1

Compare Source

v2.1.0

Compare Source

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)

v1.2.0

Compare Source

v1.1.0

Compare Source

v1.0.0

Compare Source

This release includes a couple breaking changes:

  • Node 4+ is required.
  • The logger option has been removed. Set NODE_DEBUG=gh-pages to see debug output.

If you are using Node 4+ and not using the logger option, upgrades should be painless. See below for a full list of changes:

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.

@renovate
Copy link
Contributor Author

renovate bot commented Aug 13, 2025 •
edited
Loading

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm warn cli npm v11.6.1 does not support Node.js v16.15.0. This version of npm supports the following node versions: `^20.17.0 || >=22.9.0`. You can find the latest version at https://nodejs.org/.
npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @angular/[email protected]
npm error Found: [email protected]
npm error node_modules/zone.js
npm error   zone.js@"0.10.3" from the root project
npm error
npm error Could not resolve dependency:
npm error peer zone.js@"^0.7.2" from @angular/[email protected]
npm error node_modules/@angular/core
npm error   @angular/core@"2.4.10" from the root project
npm error   peer @angular/core@"2.4.10" from @angular/[email protected]
npm error   node_modules/@angular/common
npm error     @angular/common@"2.4.10" from the root project
npm error     5 more (@angular/forms, @angular/platform-browser, ...)
npm error   8 more (@angular/compiler, @angular/compiler-cli, ...)
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/zone.js
npm error   peer zone.js@"^0.7.2" from @angular/[email protected]
npm error   node_modules/@angular/core
npm error     @angular/core@"2.4.10" from the root project
npm error     peer @angular/core@"2.4.10" from @angular/[email protected]
npm error     node_modules/@angular/common
npm error       @angular/common@"2.4.10" from the root project
npm error       5 more (@angular/forms, @angular/platform-browser, ...)
npm error     8 more (@angular/compiler, @angular/compiler-cli, ...)
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2025-09-27T00_13_20_754Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-09-27T00_13_20_754Z-debug-0.log

@renovate renovate bot requested a review from koenmetsu as a code owner August 13, 2025 23:54
@renovate renovate bot force-pushed the renovate/npm-gh-pages-vulnerability branch from 1090244 to 5b2e8d8 Compare August 19, 2025 07:25
@renovate renovate bot force-pushed the renovate/npm-gh-pages-vulnerability branch from 5b2e8d8 to 5fbd8cc Compare August 19, 2025 07:52
@renovate renovate bot changed the title chore(deps): update dependency gh-pages to v5 [security] chore(deps): update dependency gh-pages to v5 [security] - autoclosed Oct 16, 2025
@renovate renovate bot closed this Oct 16, 2025
@renovate renovate bot deleted the renovate/npm-gh-pages-vulnerability branch October 16, 2025 11:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@koenmetsu koenmetsu Awaiting requested review from koenmetsu koenmetsu is a code owner

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant