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 taiga-ui dev infra to v0.148.0 #1313

Closed
wants to merge 1 commit into from

Conversation

taiga-family-bot
Copy link
Contributor

@taiga-family-bot taiga-family-bot commented Aug 30, 2024

This PR contains the following updates:

Package Type Change
@taiga-ui/browserslist-config devDependencies 0.128.0 -> 0.148.0
@taiga-ui/commitlint-config devDependencies 0.128.0 -> 0.148.0
@​taiga-ui/eslint-plugin-experience devDependencies 0.128.0 -> 0.148.0
@taiga-ui/prettier-config devDependencies 0.128.0 -> 0.148.0
@taiga-ui/stylelint-config devDependencies 0.128.0 -> 0.148.0
@taiga-ui/tsconfig devDependencies 0.128.0 -> 0.148.0

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@taiga-family-bot
Copy link
Contributor Author

taiga-family-bot commented Aug 30, 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 error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: @typescript-eslint/[email protected]
npm error node_modules/@typescript-eslint/utils
npm error   peer @typescript-eslint/utils@"^7.11.0 || ^8.0.0" from @angular-eslint/[email protected]
npm error   node_modules/@angular-eslint/eslint-plugin
npm error   peer @typescript-eslint/utils@"^7.11.0 || ^8.0.0" from @angular-eslint/[email protected]
npm error   node_modules/@angular-eslint/eslint-plugin-template
npm error   4 more (@angular-eslint/utils, ...)
npm error
npm error Could not resolve dependency:
npm error dev @taiga-ui/eslint-plugin-experience@"0.148.0" from the root project
npm error
npm error Conflicting peer dependency: @typescript-eslint/[email protected]
npm error node_modules/@typescript-eslint/utils
npm error   peer @typescript-eslint/utils@"^8.3.0" from @taiga-ui/[email protected]
npm error   node_modules/@taiga-ui/eslint-plugin-experience
npm error     dev @taiga-ui/eslint-plugin-experience@"0.148.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /home/runner/.npm/_logs/2024-09-02T12_35_47_865Z-eresolve-report.txt
npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-09-02T12_35_47_865Z-debug-0.log

Copy link

lumberjack-bot bot commented Aug 30, 2024

Pull request was closed ✔️

All saved screenshots (for current PR) were deleted 🗑️

@taiga-family-bot taiga-family-bot self-assigned this Aug 30, 2024
Copy link
Contributor

⛔ Lint job has failed!

@taiga-family-bot taiga-family-bot force-pushed the renovate/taiga-ui-dev-infra branch from cd43d49 to d56042b Compare August 30, 2024 17:19
@taiga-family-bot taiga-family-bot changed the title chore(deps): update taiga-ui dev infra to v0.147.10 chore(deps): update taiga-ui dev infra to v0.147.11 Aug 30, 2024
Copy link
Contributor

⛔ Lint job has failed!

@taiga-family-bot taiga-family-bot changed the title chore(deps): update taiga-ui dev infra to v0.147.11 chore(deps): update taiga-ui dev infra to v0.147.12 Aug 31, 2024
@taiga-family-bot taiga-family-bot force-pushed the renovate/taiga-ui-dev-infra branch from d56042b to eb64bec Compare August 31, 2024 23:19
Copy link
Contributor

⛔ Lint job has failed!

@taiga-family-bot taiga-family-bot force-pushed the renovate/taiga-ui-dev-infra branch from eb64bec to 3190221 Compare September 1, 2024 20:21
@taiga-family-bot taiga-family-bot changed the title chore(deps): update taiga-ui dev infra to v0.147.12 chore(deps): update taiga-ui dev infra to v0.147.13 Sep 1, 2024
Copy link
Contributor

github-actions bot commented Sep 1, 2024

⛔ Lint job has failed!

@taiga-family-bot taiga-family-bot force-pushed the renovate/taiga-ui-dev-infra branch from 3190221 to 521f4a5 Compare September 2, 2024 04:24
@taiga-family-bot taiga-family-bot changed the title chore(deps): update taiga-ui dev infra to v0.147.13 chore(deps): update taiga-ui dev infra to v0.147.14 Sep 2, 2024
Copy link
Contributor

github-actions bot commented Sep 2, 2024

⛔ Lint job has failed!

@taiga-family-bot taiga-family-bot changed the title chore(deps): update taiga-ui dev infra to v0.147.14 chore(deps): update taiga-ui dev infra to v0.147.15 Sep 2, 2024
@taiga-family-bot taiga-family-bot force-pushed the renovate/taiga-ui-dev-infra branch from 521f4a5 to b389751 Compare September 2, 2024 09:22
Copy link
Contributor

github-actions bot commented Sep 2, 2024

⛔ Lint job has failed!

@taiga-family-bot taiga-family-bot force-pushed the renovate/taiga-ui-dev-infra branch from b389751 to c8928f9 Compare September 2, 2024 12:37
@taiga-family-bot taiga-family-bot changed the title chore(deps): update taiga-ui dev infra to v0.147.15 chore(deps): update taiga-ui dev infra to v0.148.0 Sep 2, 2024
Copy link
Contributor

github-actions bot commented Sep 2, 2024

⛔ Lint job has failed!

@splincode splincode closed this Sep 2, 2024
@splincode splincode deleted the renovate/taiga-ui-dev-infra branch September 2, 2024 14:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants