Skip to content

Update dependency @redhat-cloud-services/frontend-components-config to v4.7.3#470

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/red-hat-cloud-services-packages
Open

Update dependency @redhat-cloud-services/frontend-components-config to v4.7.3#470
renovate[bot] wants to merge 1 commit intomainfrom
renovate/red-hat-cloud-services-packages

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Apr 21, 2022

This PR contains the following updates:

Package Change Age Confidence
@redhat-cloud-services/frontend-components-config (source) 4.3.54.7.3 age confidence

Release Notes

RedHatInsights/frontend-components (@​redhat-cloud-services/frontend-components-config)

v4.7.3

Compare Source

v4.7.2

Compare Source

v4.7.1

Compare Source

v4.7.0

Compare Source

v4.6.40

Compare Source

v4.6.39

Compare Source

v4.6.38

Compare Source

v4.6.37

Compare Source

v4.6.36

Compare Source

v4.6.35

Compare Source

v4.6.34

Compare Source

v4.6.33

Compare Source

v4.6.32

Compare Source

v4.6.31

Compare Source

v4.6.30

Compare Source

v4.6.29

Compare Source

v4.6.28

Compare Source

v4.6.27

Compare Source

v4.6.26

Compare Source

v4.6.25

Compare Source

v4.6.24

Compare Source

v4.6.23

Compare Source

v4.6.22

Compare Source

v4.6.21

Compare Source

v4.6.20

Compare Source

v4.6.19

Compare Source

v4.6.18

Compare Source

v4.6.17

Compare Source

v4.6.16

Compare Source

v4.6.15

Compare Source

v4.6.14

Compare Source

v4.6.13

Compare Source

v4.6.12

Compare Source

v4.6.11

Compare Source

v4.6.10

Compare Source

v4.6.9

Compare Source

v4.6.8

Compare Source

v4.6.7

Compare Source

v4.6.6

Compare Source

v4.6.5

Compare Source

v4.6.4

Compare Source

v4.6.3

Compare Source

v4.6.2

Compare Source

v4.6.1

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
Copy link
Copy Markdown
Contributor Author

renovate Bot commented Apr 21, 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: .build/package-lock.json
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @webpack-cli/configtest@1.1.0
npm WARN Found: webpack@5.64.4
npm WARN node_modules/@webpack-cli/configtest/node_modules/webpack
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer webpack@"4.x.x || 5.x.x" from @webpack-cli/configtest@1.1.0
npm WARN node_modules/@webpack-cli/configtest
npm WARN   @webpack-cli/configtest@"^1.1.0" from webpack-cli@4.9.1
npm WARN   node_modules/webpack-cli
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: ajv-keywords@3.5.2
npm WARN Found: ajv@6.12.6
npm WARN node_modules/ajv-keywords/node_modules/ajv
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer ajv@"^6.9.1" from ajv-keywords@3.5.2
npm WARN node_modules/ajv-keywords
npm WARN   ajv-keywords@"^3.5.2" from schema-utils@3.1.1
npm WARN   node_modules/schema-utils
npm WARN 
npm WARN Conflicting peer dependency: ajv@6.12.6
npm WARN node_modules/ajv
npm WARN   peer ajv@"^6.9.1" from ajv-keywords@3.5.2
npm WARN   node_modules/ajv-keywords
npm WARN     ajv-keywords@"^3.5.2" from schema-utils@3.1.1
npm WARN     node_modules/schema-utils
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: optimize-css-assets-webpack-plugin@6.0.1
npm ERR! Found: webpack@5.51.1
npm ERR! node_modules/webpack
npm ERR!   dev webpack@"5.51.1" from the root project
npm ERR!   peer webpack@">=5.0.0" from assets-webpack-plugin@7.1.1
npm ERR!   node_modules/assets-webpack-plugin
npm ERR!     dev assets-webpack-plugin@"7.1.1" from the root project
npm ERR!   24 more (copy-webpack-plugin, css-loader, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer webpack@"^4.0.0" from optimize-css-assets-webpack-plugin@6.0.1
npm ERR! node_modules/optimize-css-assets-webpack-plugin
npm ERR!   dev optimize-css-assets-webpack-plugin@"6.0.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: webpack@4.47.0
npm ERR! node_modules/webpack
npm ERR!   peer webpack@"^4.0.0" from optimize-css-assets-webpack-plugin@6.0.1
npm ERR!   node_modules/optimize-css-assets-webpack-plugin
npm ERR!     dev optimize-css-assets-webpack-plugin@"6.0.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! 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-01-15T15_39_36_499Z-debug-0.log

@renovate renovate Bot force-pushed the renovate/red-hat-cloud-services-packages branch from 6765ca3 to dd1885c Compare April 21, 2022 19:57
@renovate renovate Bot changed the title Update dependency @redhat-cloud-services/frontend-components-config to v4.6.9 Update dependency @redhat-cloud-services/frontend-components-config to v4.6.10 Apr 21, 2022
@renovate renovate Bot changed the title Update dependency @redhat-cloud-services/frontend-components-config to v4.6.10 fix(deps): update dependency @redhat-cloud-services/frontend-components-config to v4.6.10 Apr 21, 2022
@renovate renovate Bot force-pushed the renovate/red-hat-cloud-services-packages branch from dd1885c to 5df2f8d Compare April 22, 2022 12:39
@renovate renovate Bot changed the title fix(deps): update dependency @redhat-cloud-services/frontend-components-config to v4.6.10 fix(deps): update dependency @redhat-cloud-services/frontend-components-config to v4.6.11 Apr 22, 2022
@renovate renovate Bot force-pushed the renovate/red-hat-cloud-services-packages branch 10 times, most recently from b8276ae to 827cc03 Compare April 29, 2022 13:20
@renovate renovate Bot force-pushed the renovate/red-hat-cloud-services-packages branch 11 times, most recently from b5de2ac to 3861d95 Compare May 6, 2022 14:59
@renovate renovate Bot changed the title fix(deps): update dependency @redhat-cloud-services/frontend-components-config to v4.6.11 fix(deps): update dependency @redhat-cloud-services/frontend-components-config to v4.6.12 May 6, 2022
@renovate renovate Bot force-pushed the renovate/red-hat-cloud-services-packages branch from 3861d95 to 8c5e47f Compare May 10, 2022 15:05
@renovate renovate Bot changed the title fix(deps): update dependency @redhat-cloud-services/frontend-components-config to v4.6.12 fix(deps): update dependency @redhat-cloud-services/frontend-components-config to v4.6.13 May 10, 2022
@renovate renovate Bot force-pushed the renovate/red-hat-cloud-services-packages branch 3 times, most recently from b198804 to 9fa5338 Compare June 3, 2022 17:44
@renovate renovate Bot force-pushed the renovate/red-hat-cloud-services-packages branch 4 times, most recently from d5f95d9 to 7e59989 Compare June 14, 2022 15:35
@renovate renovate Bot changed the title fix(deps): update dependency @redhat-cloud-services/frontend-components-config to v4.6.13 fix(deps): update dependency @redhat-cloud-services/frontend-components-config to v4.6.14 Jun 14, 2022
@renovate renovate Bot force-pushed the renovate/red-hat-cloud-services-packages branch 5 times, most recently from 8cc7150 to 7735216 Compare June 23, 2022 13:12
@renovate renovate Bot force-pushed the renovate/red-hat-cloud-services-packages branch 4 times, most recently from 8faf6ec to 0d25461 Compare June 28, 2022 14:53
@renovate renovate Bot changed the title fix(deps): update dependency @redhat-cloud-services/frontend-components-config to v4.6.14 fix(deps): update dependency @redhat-cloud-services/frontend-components-config to v4.6.15 Jun 28, 2022
@renovate renovate Bot force-pushed the renovate/red-hat-cloud-services-packages branch 5 times, most recently from 341b831 to 432c556 Compare July 5, 2022 16:17
@renovate renovate Bot force-pushed the renovate/red-hat-cloud-services-packages branch 5 times, most recently from 97eaa67 to 5fe65b3 Compare July 12, 2022 18:04
@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented Jul 22, 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: .build/package-lock.json
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @webpack-cli/configtest@1.1.0
npm WARN Found: webpack@5.64.4
npm WARN node_modules/@webpack-cli/configtest/node_modules/webpack
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer webpack@"4.x.x || 5.x.x" from @webpack-cli/configtest@1.1.0
npm WARN node_modules/@webpack-cli/configtest
npm WARN   @webpack-cli/configtest@"^1.1.0" from webpack-cli@4.9.1
npm WARN   node_modules/webpack-cli
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: ajv-keywords@3.5.2
npm WARN Found: ajv@6.12.6
npm WARN node_modules/ajv-keywords/node_modules/ajv
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer ajv@"^6.9.1" from ajv-keywords@3.5.2
npm WARN node_modules/ajv-keywords
npm WARN   ajv-keywords@"^3.5.2" from schema-utils@3.1.1
npm WARN   node_modules/schema-utils
npm WARN 
npm WARN Conflicting peer dependency: ajv@6.14.0
npm WARN node_modules/ajv
npm WARN   peer ajv@"^6.9.1" from ajv-keywords@3.5.2
npm WARN   node_modules/ajv-keywords
npm WARN     ajv-keywords@"^3.5.2" from schema-utils@3.1.1
npm WARN     node_modules/schema-utils
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: optimize-css-assets-webpack-plugin@6.0.1
npm ERR! Found: webpack@5.51.1
npm ERR! node_modules/webpack
npm ERR!   dev webpack@"5.51.1" from the root project
npm ERR!   peer webpack@">=5.0.0" from assets-webpack-plugin@7.1.1
npm ERR!   node_modules/assets-webpack-plugin
npm ERR!     dev assets-webpack-plugin@"7.1.1" from the root project
npm ERR!   24 more (copy-webpack-plugin, css-loader, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer webpack@"^4.0.0" from optimize-css-assets-webpack-plugin@6.0.1
npm ERR! node_modules/optimize-css-assets-webpack-plugin
npm ERR!   dev optimize-css-assets-webpack-plugin@"6.0.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: webpack@4.47.0
npm ERR! node_modules/webpack
npm ERR!   peer webpack@"^4.0.0" from optimize-css-assets-webpack-plugin@6.0.1
npm ERR!   node_modules/optimize-css-assets-webpack-plugin
npm ERR!     dev optimize-css-assets-webpack-plugin@"6.0.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! 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-08T20_04_16_451Z-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.

0 participants