Skip to content

build(deps-dev): bump gh-pages from 1.2.0 to 5.0.0#27

Open
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/gh-pages-5.0.0
Open

build(deps-dev): bump gh-pages from 1.2.0 to 5.0.0#27
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/gh-pages-5.0.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jun 14, 2026

Copy link
Copy Markdown

Bumps gh-pages from 1.2.0 to 5.0.0.

Release notes

Sourced from gh-pages's releases.

v5.0.0

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.

What's Changed

New Contributors

Full Changelog: tschaub/gh-pages@v4.0.0...v5.0.0

v4.0.0

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

What's Changed

Full Changelog: tschaub/gh-pages@v3.2.3...v4.0.0

v3.2.3

v3.0.0

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:

... (truncated)

Changelog

Sourced from gh-pages's changelog.

v5.0.0

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

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

v3.2.2

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

v3.2.1

v3.2.0

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

... (truncated)

Commits
  • f729b97 5.0.0
  • 51534c7 Log changes
  • ace063b Merge pull request #438 from Vicropht/patch-1
  • 58e54be Merge pull request #459 from tschaub/dependabot/npm_and_yarn/async-3.2.4
  • 2189df3 Bump async from 2.6.4 to 3.2.4
  • 051846e Merge pull request #454 from tschaub/dependabot/npm_and_yarn/email-addresses-...
  • 5c91c67 Merge pull request #455 from tschaub/dependabot/github_actions/actions/setup-...
  • fe0ad83 Merge pull request #453 from tschaub/dependabot/github_actions/actions/checko...
  • b89287d Merge pull request #445 from Nezteb/patch-1
  • e890bd1 Bump email-addresses from 3.0.1 to 5.0.0
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot 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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will 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 version will 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 dependency will 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.

Bumps [gh-pages](https://github.com/tschaub/gh-pages) from 1.2.0 to 5.0.0.
- [Release notes](https://github.com/tschaub/gh-pages/releases)
- [Changelog](https://github.com/tschaub/gh-pages/blob/main/changelog.md)
- [Commits](tschaub/gh-pages@v1.2.0...v5.0.0)

---
updated-dependencies:
- dependency-name: gh-pages
  dependency-version: 5.0.0
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Jun 14, 2026
@dependabot dependabot Bot requested a review from lolgab as a code owner June 14, 2026 00:31
@codacy-production

codacy-production Bot commented Jun 14, 2026

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 duplication

Metric Results
Duplication 0

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

Run reviewer

TIP This summary will be updated as you push new changes.

@codacy-production codacy-production Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This major version upgrade transitions gh-pages to a pure ESM package and increases the minimum Node.js requirement to 16. While Codacy results indicate the PR is up to standards, the project's environment appears to rely on legacy dependencies (e.g., npm-run-all ^4.1.3), suggesting it may not yet support ESM or modern Node.js versions. There is a high risk that existing deployment scripts or CI pipelines will fail upon merging this change because the programmatic API and environment requirements have fundamentally changed since v1.x.

About this PR

  • The transition to gh-pages v5.0.0 is a major breaking change that shifts the package to ESM-only. Ensure that the project's build and deployment infrastructure is prepared for this transition, as it likely requires updates to how scripts are invoked or how the environment is configured.

Test suggestions

  • Verify that the project's documentation deployment script (likely using gh-pages CLI) still functions correctly under the new version.
  • Verify that the CI/CD pipeline runs on a compatible Node.js version (Node 16+) as required by the new gh-pages version for its own internal stability and testing.
Prompt proposal for missing tests
Consider implementing these tests if applicable:
1. Verify that the project's documentation deployment script (likely using gh-pages CLI) still functions correctly under the new version.
2. Verify that the CI/CD pipeline runs on a compatible Node.js version (Node 16+) as required by the new gh-pages version for its own internal stability and testing.

TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback

Comment thread package.json
"cz-conventional-changelog": "^2.1.0",
"dictionary-en-us": "^2.0.0",
"gh-pages": "^1.2.0",
"gh-pages": "^5.0.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 MEDIUM RISK

This major version upgrade transitions gh-pages to a pure ESM package and increases the minimum Node.js requirement to 16. Given the legacy nature of other dependencies in this file (such as npm-run-all and codacy-coverage from 2018), this change will likely break CommonJS-based scripts or CI pipelines running on older Node.js versions. Check if the project uses CommonJS require('gh-pages') or runs on Node.js < 16. If so, either upgrade the environment to ESM/Node 16+ or revert gh-pages to a version compatible with the current setup (e.g., v2.x or v3.x).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants