Skip to content

fix(deps): update dependency hapi-swaggered-ui to v3#991

Open
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/hapi-swaggered-ui-3.x
Open

fix(deps): update dependency hapi-swaggered-ui to v3#991
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/hapi-swaggered-ui-3.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented May 13, 2020

This PR contains the following updates:

Package Type Update Change OpenSSF
hapi-swaggered-ui dependencies major 2.6.23.1.0 OpenSSF Scorecard

Release Notes

z0mt3c/hapi-swaggered-ui (hapi-swaggered-ui)

v3.1.0

Compare Source

v3.0.2

Compare Source

v3.0.1

Compare Source

v3.0.0

Compare Source


Configuration

📅 Schedule: (UTC)

  • 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 renovate bot force-pushed the renovate/hapi-swaggered-ui-3.x branch from f04cf8e to 8b9f7ad Compare May 18, 2020 02:49
@coveralls
Copy link
Copy Markdown

coveralls commented May 18, 2020

Pull Request Test Coverage Report for Build 4546

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 100.0%

Totals Coverage Status
Change from base Build 4542: 0.0%
Covered Lines: 126
Relevant Lines: 126

💛 - Coveralls

@renovate renovate bot force-pushed the renovate/hapi-swaggered-ui-3.x branch from 8b9f7ad to bf1249f Compare June 23, 2020 08:22
@renovate renovate bot changed the title fix(deps): update dependency hapi-swaggered-ui to v3 Update dependency hapi-swaggered-ui to v3 Aug 14, 2020
@renovate renovate bot changed the title Update dependency hapi-swaggered-ui to v3 fix(deps): update dependency hapi-swaggered-ui to v3 Aug 14, 2020
@renovate renovate bot force-pushed the renovate/hapi-swaggered-ui-3.x branch 14 times, most recently from dca16f1 to c552334 Compare February 15, 2021 05:00
@renovate renovate bot force-pushed the renovate/hapi-swaggered-ui-3.x branch 7 times, most recently from 126a460 to ba55987 Compare February 22, 2021 06:39
@renovate renovate bot force-pushed the renovate/hapi-swaggered-ui-3.x branch 4 times, most recently from ed43017 to 68451dd Compare February 23, 2021 10:54
@renovate renovate bot force-pushed the renovate/hapi-swaggered-ui-3.x branch 14 times, most recently from c1db15b to fd2ddc6 Compare March 9, 2021 13:57
@renovate renovate bot force-pushed the renovate/hapi-swaggered-ui-3.x branch 13 times, most recently from 51a7c98 to 9e5edff Compare March 16, 2021 03:35
@renovate
Copy link
Copy Markdown
Contributor Author

renovate bot commented Oct 29, 2021

⚠ 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 unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: travi-api@undefined
npm ERR! Found: hapi@16.7.0
npm ERR! node_modules/hapi
npm ERR!   hapi@"16.7.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer hapi@">= 17.x.x" from hapi-swaggered-ui@3.1.0
npm ERR! node_modules/hapi-swaggered-ui
npm ERR!   hapi-swaggered-ui@"3.1.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/worker/40992a/4e51ae/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/worker/40992a/4e51ae/cache/others/npm/_logs/2023-08-28T05_11_40_500Z-debug-0.log

@renovate
Copy link
Copy Markdown
Contributor Author

renovate bot commented Jun 30, 2025

⚠️ 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 unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: travi-api@undefined
npm ERR! Found: hapi@16.7.0
npm ERR! node_modules/hapi
npm ERR!   hapi@"16.7.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer hapi@">= 17.x.x" from hapi-swaggered-ui@3.1.0
npm ERR! node_modules/hapi-swaggered-ui
npm ERR!   hapi-swaggered-ui@"3.1.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 /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2026-04-08T21_07_27_665Z-debug-0.log

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