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

Update dependency connect-history-api-fallback to v2 - autoclosed #1078

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 4, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
connect-history-api-fallback ^1.6.0 -> ^2.0.0 age adoption passing confidence

Release Notes

bripkens/connect-history-api-fallback (connect-history-api-fallback)

v2.0.0

Compare Source

  • Potentially breaking: Treat HTTP HEAD requests like HTTP GET requests. This one is potentially breaking and we therefore released a new major version to be on the safe side. Most projects should not encounter issues when upgrading to this version. Contributed by @​awwit.

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 has been generated by Mend Renovate. View repository job log here.

@renovate
Copy link
Contributor Author

renovate bot commented Aug 4, 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: pils-frontend/package-lock.json
/usr/local/bin/docker: line 4: .: filename argument required
.: usage: . filename [arguments]
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/webpack
npm ERR!   dev webpack@"3.12.0" from the root project
npm ERR!   peer webpack@">=2" from [email protected]
npm ERR!   node_modules/babel-loader
npm ERR!     dev babel-loader@"8.0.6" from the root project
npm ERR!   7 more (extract-text-webpack-plugin, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer webpack@"^4.0.0 || ^5.0.0" from [email protected]
npm ERR! node_modules/copy-webpack-plugin
npm ERR!   dev copy-webpack-plugin@"5.1.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/webpack
npm ERR!   peer webpack@"^4.0.0 || ^5.0.0" from [email protected]
npm ERR!   node_modules/copy-webpack-plugin
npm ERR!     dev copy-webpack-plugin@"5.1.1" 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/1b4392/3a0723/cache/others/npm/_logs/2023-08-07T19_53_09_441Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/1b4392/3a0723/cache/others/npm/_logs/2023-08-07T19_53_09_441Z-debug-0.log

@renovate renovate bot force-pushed the renovate/connect-history-api-fallback-2.x branch from 14e3107 to 8292df6 Compare August 4, 2023 16:51
@oscrx oscrx force-pushed the main branch 2 times, most recently from 9381ad9 to 08e8e7a Compare August 4, 2023 23:37
@renovate renovate bot force-pushed the renovate/connect-history-api-fallback-2.x branch from 8292df6 to a55ac26 Compare August 4, 2023 23:40
@oscrx oscrx force-pushed the main branch 3 times, most recently from cec1dcc to d30d027 Compare August 5, 2023 00:18
@renovate renovate bot force-pushed the renovate/connect-history-api-fallback-2.x branch 2 times, most recently from 98f1c36 to 3c17a5f Compare August 5, 2023 01:13
@renovate renovate bot force-pushed the renovate/connect-history-api-fallback-2.x branch from 3c17a5f to c13cd68 Compare August 5, 2023 01:42
@renovate renovate bot force-pushed the renovate/connect-history-api-fallback-2.x branch 6 times, most recently from b13be39 to e64a541 Compare August 5, 2023 12:23
@codecov
Copy link

codecov bot commented Aug 5, 2023

Codecov Report

Patch coverage has no change and project coverage change: -0.51% ⚠️

Comparison is base (85cc939) 22.34% compared to head (6c14f2b) 21.83%.
Report is 2 commits behind head on main.

❗ Current head 6c14f2b differs from pull request most recent head 5452147. Consider uploading reports for the commit 5452147 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1078      +/-   ##
==========================================
- Coverage   22.34%   21.83%   -0.51%     
==========================================
  Files          14       14              
  Lines         179      174       -5     
  Branches       21       24       +3     
==========================================
- Hits           40       38       -2     
+ Misses        121      115       -6     
- Partials       18       21       +3     

see 3 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@renovate renovate bot force-pushed the renovate/connect-history-api-fallback-2.x branch 2 times, most recently from d13c56f to 4d0f953 Compare August 6, 2023 23:38
@oscrx oscrx force-pushed the main branch 3 times, most recently from 4e06394 to 369bee3 Compare August 6, 2023 23:53
@renovate renovate bot force-pushed the renovate/connect-history-api-fallback-2.x branch 4 times, most recently from 255944b to a883abe Compare August 7, 2023 02:27
@renovate renovate bot force-pushed the renovate/connect-history-api-fallback-2.x branch from a883abe to 2cc2233 Compare August 7, 2023 03:27
@oscrx oscrx added the preview Deploy this branch to kubernetes label Aug 7, 2023
@renovate renovate bot force-pushed the renovate/connect-history-api-fallback-2.x branch from 2cc2233 to dee5885 Compare August 7, 2023 03:57
@oscrx oscrx removed the preview Deploy this branch to kubernetes label Aug 7, 2023
@renovate renovate bot force-pushed the renovate/connect-history-api-fallback-2.x branch 9 times, most recently from 0568953 to 93cf08f Compare August 7, 2023 19:32
@renovate renovate bot force-pushed the renovate/connect-history-api-fallback-2.x branch from 93cf08f to 5452147 Compare August 7, 2023 19:53
@sonarcloud
Copy link

sonarcloud bot commented Aug 7, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@renovate renovate bot changed the title Update dependency connect-history-api-fallback to v2 Update dependency connect-history-api-fallback to v2 - autoclosed Aug 8, 2023
@renovate renovate bot closed this Aug 8, 2023
@renovate renovate bot deleted the renovate/connect-history-api-fallback-2.x branch August 8, 2023 21:22
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