Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Aug 12, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
gh-pages ^4.0.0 -> ^6.0.0 age adoption passing confidence

Release Notes

tschaub/gh-pages (gh-pages)

v6.2.0

Compare Source

Assorted dependency updates and a documentation change.

v6.1.1

Compare Source

This release fixes an issue with the --cname option.

v6.1.0

Compare Source

This release adds support for --nojekyll and --cname options.

v6.0.0

Compare Source

This release drops support for Node 14. Otherwise, there are no special upgrade considerations.

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.


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, 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 12, 2023

⚠ 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 ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: react-typed@1.2.0
npm ERR! Found: react@18.2.0
npm ERR! node_modules/react
npm ERR!   react@"^18.2.0" from the root project
npm ERR!   peer react@">=16.8" from @react-hook/debounce@3.0.0
npm ERR!   node_modules/@react-hook/debounce
npm ERR!     @react-hook/debounce@"^3.0.0" from @react-hook/window-size@3.1.1
npm ERR!     node_modules/@react-hook/window-size
npm ERR!       @react-hook/window-size@"^3.1.1" from the root project
npm ERR!   15 more (@react-hook/event, @react-hook/latest, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.3.0" from react-typed@1.2.0
npm ERR! node_modules/react-typed
npm ERR!   react-typed@"^1.2.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: react@16.14.0
npm ERR! node_modules/react
npm ERR!   peer react@"^16.3.0" from react-typed@1.2.0
npm ERR!   node_modules/react-typed
npm ERR!     react-typed@"^1.2.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/d0d98d/147fc4/cache/others/npm/_logs/2023-11-17T21_11_31_193Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/d0d98d/147fc4/cache/others/npm/_logs/2023-11-17T21_11_31_193Z-debug-0.log

@renovate renovate bot force-pushed the renovate/gh-pages-6.x branch from 02eb85f to 1966ec4 Compare November 17, 2023 21:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant