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: update dependency release-it to v17.10.0 #590

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

Conversation

taiga-family-bot
Copy link
Collaborator

@taiga-family-bot taiga-family-bot commented Oct 8, 2024

This PR contains the following updates:

Package Type Change
release-it devDependencies 17.6.0 -> 17.10.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
Collaborator Author

taiga-family-bot commented Oct 8, 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: @taiga-ui/[email protected]
npm error Found: [email protected]
npm error node_modules/release-it
npm error   dev release-it@"17.10.0" from the root project
npm error   peer release-it@"^14.0.0 || ^15.2.0 || ^16.0.0 || ^17.0.0" from @release-it-plugins/[email protected]
npm error   node_modules/@release-it-plugins/workspaces
npm error     dev @release-it-plugins/workspaces@"4.2.0" from the root project
npm error   1 more (@release-it/conventional-changelog)
npm error
npm error Could not resolve dependency:
npm error peer release-it@"17.6.0" from @taiga-ui/[email protected]
npm error node_modules/@taiga-ui/release-it-config
npm error   dev @taiga-ui/release-it-config@"0.222.4" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/release-it
npm error   peer release-it@"17.6.0" from @taiga-ui/[email protected]
npm error   node_modules/@taiga-ui/release-it-config
npm error     dev @taiga-ui/release-it-config@"0.222.4" 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-10-16T07_29_47_526Z-eresolve-report.txt
npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-10-16T07_29_47_526Z-debug-0.log

@taiga-family-bot taiga-family-bot changed the title chore(deps): update dependency release-it to v17.7.0 chore: update dependency release-it to v17.7.0 Oct 9, 2024
@taiga-family-bot taiga-family-bot force-pushed the renovate/dev-dependencies/release-it-17.x branch from b52f518 to ca02435 Compare October 9, 2024 18:33
@taiga-family-bot taiga-family-bot changed the title chore: update dependency release-it to v17.7.0 chore: update dependency release-it to v17.8.2 Oct 9, 2024
@taiga-family-bot taiga-family-bot changed the title chore: update dependency release-it to v17.8.2 chore: update dependency release-it to v17.9.0 Oct 15, 2024
@taiga-family-bot taiga-family-bot force-pushed the renovate/dev-dependencies/release-it-17.x branch from ca02435 to e33cace Compare October 15, 2024 18:46
@taiga-family-bot taiga-family-bot changed the title chore: update dependency release-it to v17.9.0 chore: update dependency release-it to v17.10.0 Oct 16, 2024
@taiga-family-bot taiga-family-bot force-pushed the renovate/dev-dependencies/release-it-17.x branch from e33cace to 4dd1020 Compare October 16, 2024 07:29
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