Skip to content
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.

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

chore(deps): update dependency @hapi/hapi to v21 #1078

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Nov 20, 2022

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@hapi/hapi (source) 20.2.1 -> 21.3.12 age adoption passing confidence

Release Notes

hapijs/hapi (@​hapi/hapi)

v21.3.12

Compare Source

v21.3.11

Compare Source

v21.3.10

Compare Source

v21.3.9

Compare Source

v21.3.8

Compare Source

v21.3.7

Compare Source

v21.3.6

Compare Source

v21.3.5

Compare Source

v21.3.4

Compare Source

v21.3.3

Compare Source

v21.3.2

Compare Source

v21.3.1

Compare Source

v21.3.0: 20.3.0

Compare Source

⚠️ This release contains security fixes, for more information see https://github.com/hapijs/hapi/issues/4425.

v21.2.2

Compare Source

v21.2.1

Compare Source

v21.2.0

Compare Source

v21.1.0

Compare Source

v21.0.0

Compare Source

Release notes: https://github.com/hapijs/hapi/issues/4386

hapi v21.0.0 is a medium-sized release focused on modernization and miscellaneous API improvements. All modules in the hapi.js ecosystem have been updated to officially support Node.js v18, be compatible with ESM projects, and drop support for Node.js v12. Plugins in the hapi.js ecosystem now support hapi v20+.

v20.3.0

Compare Source

v20.2.2

Compare Source


Configuration

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

🚦 Automerge: Enabled.

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
Author

renovate bot commented Nov 20, 2022

⚠ 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: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/stylelint
npm ERR!   dev stylelint@"13.13.1" from the root project
npm ERR!   peer stylelint@"11.x - 14.x" from [email protected]
npm ERR!   node_modules/stylelint-config-css-modules
npm ERR!     dev stylelint-config-css-modules@"2.3.0" from the root project
npm ERR!   2 more (stylelint-config-recommended, stylelint-config-standard)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer stylelint@">=14" from [email protected]
npm ERR! node_modules/stylelint-config-recess-order
npm ERR!   dev stylelint-config-recess-order@"3.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/stylelint
npm ERR!   peer stylelint@">=14" from [email protected]
npm ERR!   node_modules/stylelint-config-recess-order
npm ERR!     dev stylelint-config-recess-order@"3.0.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! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-04-09T15_11_17_289Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-hapijs-monorepo branch from 9196840 to ee3742c Compare March 19, 2023 00:00
@renovate renovate bot force-pushed the renovate/major-hapijs-monorepo branch from ee3742c to 2d630cd Compare March 27, 2023 21:34
@renovate renovate bot force-pushed the renovate/major-hapijs-monorepo branch from 2d630cd to de7c188 Compare May 28, 2023 10:47
@renovate renovate bot force-pushed the renovate/major-hapijs-monorepo branch from de7c188 to 5c1c0b0 Compare January 29, 2024 16:43
@renovate renovate bot force-pushed the renovate/major-hapijs-monorepo branch 3 times, most recently from cd47115 to 354766a Compare March 19, 2024 22:32
@renovate renovate bot force-pushed the renovate/major-hapijs-monorepo branch 2 times, most recently from 1846736 to 2cc470a Compare April 9, 2024 15:11
@renovate renovate bot force-pushed the renovate/major-hapijs-monorepo branch from 2cc470a to 2bb7bf0 Compare June 12, 2024 10:08
Copy link
Author

renovate bot commented Jun 12, 2024

⚠️ 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: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/stylelint
npm ERR!   dev stylelint@"13.13.1" from the root project
npm ERR!   peer stylelint@"11.x - 14.x" from [email protected]
npm ERR!   node_modules/stylelint-config-css-modules
npm ERR!     dev stylelint-config-css-modules@"2.3.0" from the root project
npm ERR!   2 more (stylelint-config-recommended, stylelint-config-standard)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer stylelint@">=14" from [email protected]
npm ERR! node_modules/stylelint-config-recess-order
npm ERR!   dev stylelint-config-recess-order@"3.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/stylelint
npm ERR!   peer stylelint@">=14" from [email protected]
npm ERR!   node_modules/stylelint-config-recess-order
npm ERR!     dev stylelint-config-recess-order@"3.0.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! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-10-25T00_26_27_628Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-hapijs-monorepo branch from 2bb7bf0 to 51389b4 Compare October 24, 2024 10:37
@renovate renovate bot force-pushed the renovate/major-hapijs-monorepo branch from 51389b4 to 475200a Compare October 25, 2024 00:26
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.

0 participants