chore(deps): update taiga-ui dev infra

[taiga-family-bot]

This PR contains the following updates:

Package	Type	Change
@taiga-ui/browserslist-config	devDependencies	0.182.0 -> 0.187.0
@taiga-ui/commitlint-config	devDependencies	0.182.0 -> 0.187.0
@taiga-ui/cspell-config	devDependencies	0.182.0 -> 0.187.0
@​taiga-ui/design-tokens	devDependencies	0.135.0 -> 0.136.0
@​taiga-ui/eslint-plugin-experience	devDependencies	0.182.0 -> 0.187.0
@taiga-ui/prettier-config	devDependencies	0.182.0 -> 0.187.0
@taiga-ui/stylelint-config	devDependencies	0.182.0 -> 0.187.0
@taiga-ui/tsconfig	devDependencies	0.182.0 -> 0.187.0

---

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

---

This PR has been generated by Renovate Bot.

[lumberjack-bot]

Tests completed successfully ✅

Good job 🔥

[github-actions]

⛔ Lint job has failed!

[github-actions]

Visit the preview URL for this PR (updated for commit 6ca990c):

https://taiga-previews--pr9056-renovate-taiga-ui-de-5ln70w3z.web.app

_{(expires Wed, 18 Sep 2024 16:38:13 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

_{Sign: 20bbff1ad19772ecf9c5134a84c0641b0d776f4a}

[bundlemon]

BundleMon

Files updated (2)

Status	Path	Size	Limits
✅	demo/browser/polyfills.(hash).js	11.18KB (-20B -0.17%)	+10%
✅	demo/browser/vendor.(hash).js	216.3KB (-168B -0.08%)	+10%

Unchanged files (3)

Status	Path	Size	Limits
✅	demo/browser/main.(hash).js	285.84KB	+10%
✅	demo/browser/runtime.(hash).js	42.25KB	+10%
✅	demo/browser/styles.(hash).css	13.51KB	+10%

Total files change -188B -0.03%

Groups updated (1)

Status	Path	Size	Limits
✅	demo/browser/*..js	7.01MB (-195B 0%)	-

Final result: ✅

View report in BundleMon website ➡️

---

Current branch size history | Target branch size history

[taiga-family-bot]

⚠️ 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: @taiga-ui/[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   7 more (@angular-eslint/utils, @stylistic/eslint-plugin, ...)
npm error
npm error Could not resolve dependency:
npm error dev @taiga-ui/eslint-plugin-experience@"0.187.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.6.0" from @taiga-ui/[email protected]
npm error   node_modules/@taiga-ui/eslint-plugin-experience
npm error     dev @taiga-ui/eslint-plugin-experience@"0.187.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-17T16_29_45_303Z-eresolve-report.txt
npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-09-17T16_29_45_303Z-debug-0.log

[github-actions]

⛔ Lint job has failed!

[github-actions]

⛔ Lint job has failed!

[github-actions]

⛔ Lint job has failed!

[github-actions]

⛔ Lint job has failed!

[taiga-family-bot]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.