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

fix(deps): update dependency @redhat-cloud-services/frontend-components-config to v6 #671

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 1, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@redhat-cloud-services/frontend-components-config (source) 4.3.5 -> 6.3.4 age adoption passing confidence

Release Notes

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

v6.3.4

Compare Source

Changelog

This file was generated using @​jscutlery/semver.

6.3.4 (2024-11-22)

Dependency Updates
  • @redhat-cloud-services/frontend-components-config-utilities updated to version 4.0.4
  • @redhat-cloud-services/tsc-transform-imports updated to version 1.0.21

6.3.3 (2024-11-22)

Dependency Updates
  • @redhat-cloud-services/frontend-components-config-utilities updated to version 4.0.3
  • @redhat-cloud-services/tsc-transform-imports updated to version 1.0.20

6.3.3 (2024-11-19)

Dependency Updates
  • @redhat-cloud-services/frontend-components-config-utilities updated to version 4.0.3
  • @redhat-cloud-services/tsc-transform-imports updated to version 1.0.20

v6.3.3

Compare Source

v6.3.2: Initial config release

Compare Source

v6.3.1

Compare Source

v6.3.0

Compare Source

v6.2.10

Compare Source

v6.2.9

Compare Source

v6.2.8

Compare Source

v6.2.7

Compare Source

v6.2.6

Compare Source

v6.2.5

Compare Source

v6.2.4

Compare Source

v6.2.3

Compare Source

v6.2.2

Compare Source

v6.2.1

Compare Source

v6.2.0

Compare Source

v6.1.3

Compare Source

v6.1.2

Compare Source

v6.1.1

Compare Source

v6.1.0

Compare Source

v6.0.18

Compare Source

v6.0.17

Compare Source

v6.0.16

Compare Source

v6.0.15

Compare Source

v6.0.14

Compare Source

v6.0.13

Compare Source

v6.0.12

Compare Source

v6.0.11

Compare Source

v6.0.10

Compare Source

v6.0.9

Compare Source

v6.0.8

Compare Source

v6.0.7

Compare Source

v6.0.6

Compare Source

v6.0.5

Compare Source

v6.0.4

Compare Source

v6.0.3

Compare Source

v6.0.2

Compare Source

v6.0.1

Compare Source

v6.0.0

Compare Source

v5.1.1

Compare Source

v5.1.0

Compare Source

v5.0.5

Compare Source

v5.0.4

Compare Source

v5.0.3

Compare Source

v5.0.2

Compare Source

v5.0.1

Compare Source

v5.0.0

Compare Source

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: 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
Contributor Author

renovate bot commented Jun 1, 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: .build/package-lock.json
npm WARN ERESOLVE overriding peer dependency
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @webpack-cli/[email protected]
npm WARN Found: [email protected]
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/[email protected]
npm WARN node_modules/@webpack-cli/configtest
npm WARN   @webpack-cli/configtest@"^1.1.0" from [email protected]
npm WARN   node_modules/webpack-cli
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: [email protected]
npm WARN Found: [email protected]
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 [email protected]
npm WARN node_modules/ajv-keywords
npm WARN   ajv-keywords@"^3.5.2" from [email protected]
npm WARN   node_modules/schema-utils
npm WARN 
npm WARN Conflicting peer dependency: [email protected]
npm WARN node_modules/ajv
npm WARN   peer ajv@"^6.9.1" from [email protected]
npm WARN   node_modules/ajv-keywords
npm WARN     ajv-keywords@"^3.5.2" from [email protected]
npm WARN     node_modules/schema-utils
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!   peer webpack@"^5.75.0" from @openshift/[email protected]
npm ERR!   node_modules/@redhat-cloud-services/frontend-components-config-utilities/node_modules/@openshift/dynamic-plugin-sdk-webpack
npm ERR!     @openshift/dynamic-plugin-sdk-webpack@"^4.0.1" from @redhat-cloud-services/[email protected]
npm ERR!     node_modules/@redhat-cloud-services/frontend-components-config-utilities
npm ERR!       @redhat-cloud-services/frontend-components-config-utilities@"^3.0.5" from @redhat-cloud-services/[email protected]
npm ERR!       node_modules/@redhat-cloud-services/frontend-components-config
npm ERR!         @redhat-cloud-services/frontend-components-config@"6.0.13" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer webpack@"^4.0.0" from [email protected]
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: [email protected]
npm ERR! node_modules/webpack
npm ERR!   peer webpack@"^4.0.0" from [email protected]
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-05-02T15_54_12_692Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-red-hat-cloud-services-packages branch from ab80ab4 to de11a7d Compare June 19, 2023 17:35
@renovate renovate bot force-pushed the renovate/major-red-hat-cloud-services-packages branch 2 times, most recently from 7e56e9b to edcf7c0 Compare July 3, 2023 11:15
@renovate renovate bot force-pushed the renovate/major-red-hat-cloud-services-packages branch 2 times, most recently from 24d452d to fd18cc3 Compare July 26, 2023 09:44
@renovate renovate bot force-pushed the renovate/major-red-hat-cloud-services-packages branch from fd18cc3 to 28e7414 Compare August 24, 2023 11:52
@renovate renovate bot changed the title fix(deps): update dependency @redhat-cloud-services/frontend-components-config to v5 fix(deps): update dependency @redhat-cloud-services/frontend-components-config to v6 Aug 24, 2023
@renovate renovate bot force-pushed the renovate/major-red-hat-cloud-services-packages branch 3 times, most recently from d708083 to b8598f3 Compare August 30, 2023 10:45
@renovate renovate bot force-pushed the renovate/major-red-hat-cloud-services-packages branch from b8598f3 to 1af3f3e Compare September 13, 2023 17:32
@renovate renovate bot force-pushed the renovate/major-red-hat-cloud-services-packages branch from 1af3f3e to 82ad35a Compare November 28, 2023 10:09
@renovate renovate bot force-pushed the renovate/major-red-hat-cloud-services-packages branch 3 times, most recently from cc73320 to c89c919 Compare January 11, 2024 15:01
@renovate renovate bot force-pushed the renovate/major-red-hat-cloud-services-packages branch 2 times, most recently from 2ab615e to f80f4f3 Compare January 22, 2024 15:17
@renovate renovate bot force-pushed the renovate/major-red-hat-cloud-services-packages branch from f80f4f3 to ba2c3f3 Compare February 21, 2024 09:18
@renovate renovate bot force-pushed the renovate/major-red-hat-cloud-services-packages branch from ba2c3f3 to d6ea516 Compare March 13, 2024 16:46
@renovate renovate bot force-pushed the renovate/major-red-hat-cloud-services-packages branch from d6ea516 to 3bc474a Compare April 3, 2024 13:07
@renovate renovate bot force-pushed the renovate/major-red-hat-cloud-services-packages branch from 3bc474a to cd252c5 Compare May 2, 2024 15:54
@renovate renovate bot force-pushed the renovate/major-red-hat-cloud-services-packages branch from cd252c5 to ea704fa Compare May 15, 2024 19:50
Copy link
Contributor Author

renovate bot commented May 15, 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 ERESOLVE overriding peer dependency
npm WARN While resolving: @webpack-cli/[email protected]
npm WARN Found: [email protected]
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/[email protected]
npm WARN node_modules/@webpack-cli/configtest
npm WARN   @webpack-cli/configtest@"^1.1.0" from [email protected]
npm WARN   node_modules/webpack-cli
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: [email protected]
npm WARN Found: [email protected]
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 [email protected]
npm WARN node_modules/ajv-keywords
npm WARN   ajv-keywords@"^3.5.2" from [email protected]
npm WARN   node_modules/schema-utils
npm WARN 
npm WARN Conflicting peer dependency: [email protected]
npm WARN node_modules/ajv
npm WARN   peer ajv@"^6.9.1" from [email protected]
npm WARN   node_modules/ajv-keywords
npm WARN     ajv-keywords@"^3.5.2" from [email protected]
npm WARN     node_modules/schema-utils
npm WARN ERESOLVE overriding peer dependency
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!   peer webpack@"^5.75.0" from @openshift/[email protected]
npm ERR!   node_modules/@redhat-cloud-services/frontend-components-config-utilities/node_modules/@openshift/dynamic-plugin-sdk-webpack
npm ERR!     @openshift/dynamic-plugin-sdk-webpack@"^4.0.1" from @redhat-cloud-services/[email protected]
npm ERR!     node_modules/@redhat-cloud-services/frontend-components-config-utilities
npm ERR!       @redhat-cloud-services/frontend-components-config-utilities@"^3.2.3" from @redhat-cloud-services/[email protected]
npm ERR!       node_modules/@redhat-cloud-services/frontend-components-config
npm ERR!         @redhat-cloud-services/frontend-components-config@"6.3.4" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer webpack@"^4.0.0" from [email protected]
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: [email protected]
npm ERR! node_modules/webpack
npm ERR!   peer webpack@"^4.0.0" from [email protected]
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-11-23T01_04_53_489Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-red-hat-cloud-services-packages branch 2 times, most recently from 36e193e to 65d187d Compare June 14, 2024 12:45
@renovate renovate bot force-pushed the renovate/major-red-hat-cloud-services-packages branch 2 times, most recently from a99c0c5 to 9bf13c6 Compare June 27, 2024 11:03
@renovate renovate bot force-pushed the renovate/major-red-hat-cloud-services-packages branch 2 times, most recently from 406ff99 to 82c9785 Compare July 2, 2024 11:11
@renovate renovate bot force-pushed the renovate/major-red-hat-cloud-services-packages branch from 82c9785 to 339cd08 Compare July 8, 2024 08:49
@renovate renovate bot force-pushed the renovate/major-red-hat-cloud-services-packages branch 2 times, most recently from 9eaf25b to 57f1e67 Compare July 23, 2024 10:41
@renovate renovate bot force-pushed the renovate/major-red-hat-cloud-services-packages branch 3 times, most recently from 95147a0 to d77fcfb Compare August 7, 2024 16:46
@renovate renovate bot force-pushed the renovate/major-red-hat-cloud-services-packages branch 4 times, most recently from bbee853 to a915dbc Compare August 20, 2024 17:00
@renovate renovate bot force-pushed the renovate/major-red-hat-cloud-services-packages branch from a915dbc to 1aa7a96 Compare August 28, 2024 08:48
@renovate renovate bot force-pushed the renovate/major-red-hat-cloud-services-packages branch from 1aa7a96 to 2ac0aab Compare September 18, 2024 10:27
@renovate renovate bot force-pushed the renovate/major-red-hat-cloud-services-packages branch 2 times, most recently from 9784571 to d062308 Compare October 2, 2024 09:21
@renovate renovate bot force-pushed the renovate/major-red-hat-cloud-services-packages branch from d062308 to 62dd709 Compare October 9, 2024 12:41
@renovate renovate bot force-pushed the renovate/major-red-hat-cloud-services-packages branch 2 times, most recently from d653d12 to 0891a56 Compare October 25, 2024 12:55
@renovate renovate bot force-pushed the renovate/major-red-hat-cloud-services-packages branch from 0891a56 to 64ae8a4 Compare November 23, 2024 01:05
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