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.

Sign up for GitHub

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

Jump to bottom

chore(deps): update dependency release-it to v17 #2507

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

chore(deps): update dependency release-it to v17 #2507

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 30, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
release-it 15.11.0 -> 17.8.2 age adoption passing confidence

Release Notes

release-it/release-it (release-it)

v17.8.2

Compare Source

v17.8.1

Compare Source

v17.8.0

Compare Source

v17.7.0

Compare Source

v17.6.0

Compare Source

  • Update dependencies (517ac8c)
  • Replace eslint-plugin-import with eslint-plugin-import-x (5828326)
  • feat: add secure flag to gitlab config (#​1129) (7a3ce98)

v17.5.0

Compare Source

  • Add flag --preReleaseBase=1 to use prelease base 1 (resolves #​1128) (6570068)

v17.4.2

Compare Source

v17.4.1

Compare Source

v17.4.0

Compare Source

v17.3.0

Compare Source

v17.2.1

Compare Source

  • Update some dependencies (bb23771)
  • Exit without error message when requireCommits is true but requireCommitsFail is false and no commits are available (#​1101) (cce35f3)

v17.2.0

Compare Source

v17.1.1

Compare Source

v17.1.0

Compare Source

v17.0.5

Compare Source

  • Fix dependencies for Windows (d5a4c55)

v17.0.4

Compare Source

v17.0.3

Compare Source

  • Fix dependencies for Windows (c7d5ff0)

v17.0.2

Compare Source

v17.0.1

Compare Source

v17.0.0

Compare Source

v16.3.0

Compare Source

v16.2.1

Compare Source

  • Format Markdown (ebe4fbd)
  • Add production mode config for Knip (c1c0f99)
  • Update dependencies (a3d32ae)
  • Fix initial --snapshot latestVersion (f283230)

v16.2.0

Compare Source

v16.1.5

Compare Source

  • Only show url message on Windows (68b91c4)
  • fix: unable to open the browser automatically on Windows system (#​1019) (5069c30)

v16.1.4

Compare Source

  • Replace mock-fs with memfs + fs-monkey (723db6c)
  • Update dependencies (a3da2bf)

v16.1.3

Compare Source

v16.1.2

Compare Source

  • Revert some updates for Node.js 16 compat (a106c83)

v16.1.1

Compare Source

v16.1.0

Compare Source

  • Edit and move new section about getLatestTagFromAllRefs up in docs (a166ab4)
  • Extend test for getLatestTagFromAllRefs to assert default behavior too (930e80a)
  • test: add a test scenario for git.getLatestTagFromAllRefs (fef97c6)
  • feat: add git.getLatestTagFromAllRefs config item to use all refs to determine latest version, not just reachable commits. (8611ef0)
  • docs: update legacy Node comment on readme page (#​1021) (5beacf2)

v16.0.0

Compare Source

  • Add v16 to changelog (2e09260)
  • Add knip to deps/scripts (00220ce)
  • Update dependencies + add lockfile (breaking support for Node.js v14/npm v6) (97c233e)

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

renovate bot commented Jan 30, 2024 •
edited
Loading

⚠ 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 ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @nestjs/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR!   dev reflect-metadata@"0.2.1" from the root project
npm ERR!   peer reflect-metadata@"^0.1.12 || ^0.2.0" from @nestjs/[email protected]
npm ERR!   node_modules/@nestjs/common
npm ERR!     dev @nestjs/common@"10.3.2" from the root project
npm ERR!     peer @nestjs/common@"^8.0.0 || ^9.0.0 || ^10.0.0" from @mikro-orm/[email protected]
npm ERR!     node_modules/@mikro-orm/nestjs
npm ERR!       dev @mikro-orm/nestjs@"5.2.3" from the root project
npm ERR!     11 more (@nestjs/axios, @nestjs/core, @nestjs/mapped-types, ...)
npm ERR!   7 more (@nestjs/core, @nestjs/mapped-types, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer reflect-metadata@"^0.1.13" from @nestjs/[email protected]
npm ERR! node_modules/@nestjs/sequelize
npm ERR!   dev @nestjs/sequelize@"10.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR!   peer reflect-metadata@"^0.1.13" from @nestjs/[email protected]
npm ERR!   node_modules/@nestjs/sequelize
npm ERR!     dev @nestjs/sequelize@"10.0.0" 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-04-26T08_41_25_195Z-debug-0.log

@renovate renovate bot force-pushed the renovate/release-it-17.x branch 7 times, most recently from 54df95c to 3f50e1d Compare February 1, 2024 09:21
@renovate renovate bot force-pushed the renovate/release-it-17.x branch 9 times, most recently from ae90166 to 31e06ed Compare February 7, 2024 21:41
@renovate renovate bot force-pushed the renovate/release-it-17.x branch 4 times, most recently from 298b9a6 to cc4aeb9 Compare February 19, 2024 00:40
@renovate renovate bot force-pushed the renovate/release-it-17.x branch from cc4aeb9 to 03f5a0d Compare April 12, 2024 11:53
@renovate renovate bot force-pushed the renovate/release-it-17.x branch from 03f5a0d to 015167c Compare April 26, 2024 08:41
@renovate renovate bot force-pushed the renovate/release-it-17.x branch from 015167c to 9bf5048 Compare May 21, 2024 01:04
@renovate Renovate
Copy link
Contributor Author

renovate bot commented May 21, 2024 •
edited
Loading

⚠️ 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 ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @nestjs/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR!   dev reflect-metadata@"0.2.1" from the root project
npm ERR!   peer reflect-metadata@"^0.1.12 || ^0.2.0" from @nestjs/[email protected]
npm ERR!   node_modules/@nestjs/common
npm ERR!     dev @nestjs/common@"10.3.2" from the root project
npm ERR!     peer @nestjs/common@"^8.0.0 || ^9.0.0 || ^10.0.0" from @mikro-orm/[email protected]
npm ERR!     node_modules/@mikro-orm/nestjs
npm ERR!       dev @mikro-orm/nestjs@"5.2.3" from the root project
npm ERR!     11 more (@nestjs/axios, @nestjs/core, @nestjs/mapped-types, ...)
npm ERR!   7 more (@nestjs/core, @nestjs/mapped-types, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer reflect-metadata@"^0.1.13" from @nestjs/[email protected]
npm ERR! node_modules/@nestjs/sequelize
npm ERR!   dev @nestjs/sequelize@"10.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR!   peer reflect-metadata@"^0.1.13" from @nestjs/[email protected]
npm ERR!   node_modules/@nestjs/sequelize
npm ERR!     dev @nestjs/sequelize@"10.0.0" 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-10-09T19_53_28_116Z-debug-0.log

@renovate renovate bot force-pushed the renovate/release-it-17.x branch from 9bf5048 to d4116a9 Compare June 21, 2024 11:36
@renovate renovate bot force-pushed the renovate/release-it-17.x branch 2 times, most recently from 7577434 to 766e44b Compare July 8, 2024 19:17
@renovate renovate bot force-pushed the renovate/release-it-17.x branch 2 times, most recently from 136ebf4 to d7d8cb0 Compare July 16, 2024 14:57
@renovate renovate bot force-pushed the renovate/release-it-17.x branch from d7d8cb0 to 2e762b6 Compare July 16, 2024 15:02
@renovate renovate bot force-pushed the renovate/release-it-17.x branch from 2e762b6 to 162c675 Compare October 4, 2024 12:37
@renovate renovate bot force-pushed the renovate/release-it-17.x branch from 162c675 to 3e0b0b3 Compare October 9, 2024 19:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants