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 dependency @vue/eslint-config-typescript to v14 #435

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 8, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@vue/eslint-config-typescript ^13.0.0 -> ^14.0.0 age adoption passing confidence

Release Notes

vuejs/eslint-config-typescript (@​vue/eslint-config-typescript)

v14.1.4

Compare Source

v14.1.3

Compare Source

What's Changed

New Contributors

Full Changelog: vuejs/eslint-config-typescript@v14.1.2...v14.1.3

v14.1.2

Compare Source

Bug Fixes

  • Print more friendly error messages if the user provides a non-existent configuration name to extends.

Full Changelog: vuejs/eslint-config-typescript@v14.1.1...v14.1.2

v14.1.1

Compare Source

Bug Fixes

  • Fixed #​91

    TypeError: Config "typescript-eslint/disable-type-checked": Key "files": Expected value to be a non-empty array"

Full Changelog: vuejs/eslint-config-typescript@v14.1.0...v14.1.1

v14.1.0

Compare Source

New Features

Bug Fixes

New Contributors

Full Changelog: vuejs/eslint-config-typescript@v14.0.1...v14.1.0

v14.0.1

Compare Source

Bugfixes

  • Fixed an occasional bug that when using with npm or yarn v1, an invalid ecmaVersion error would be thrown if the wrong version of estree is hoisted to the node_modules root. Fixes #​87. [aae95d6]

New Contributors

Full Changelog: vuejs/eslint-config-typescript@v14.0.0...v14.0.1

v14.0.0

Compare Source

What's Changed

Full Changelog: vuejs/eslint-config-typescript@v13.0.0...v14.0.0


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 bot added the dependencies label Oct 8, 2024
Copy link
Contributor Author

renovate 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: frontend-service/package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/eslint
npm error   peer eslint@"^6.0.0 || ^7.0.0 || >=8.0.0" from @eslint-community/[email protected]
npm error   node_modules/@eslint-community/eslint-utils
npm error     @eslint-community/eslint-utils@"^4.4.0" from @typescript-eslint/[email protected]
npm error     node_modules/@typescript-eslint/utils
npm error       @typescript-eslint/utils@"7.8.0" from @typescript-eslint/[email protected]
npm error       node_modules/@typescript-eslint/eslint-plugin
npm error       1 more (@typescript-eslint/type-utils)
npm error     @eslint-community/eslint-utils@"^4.2.0" from [email protected]
npm error     1 more (eslint-plugin-vue)
npm error   peer eslint@"^8.56.0" from @typescript-eslint/[email protected]
npm error   node_modules/@typescript-eslint/eslint-plugin
npm error   8 more (@typescript-eslint/parser, ...)
npm error
npm error Could not resolve dependency:
npm error dev @vue/eslint-config-typescript@"^14.0.0" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/eslint
npm error   peer eslint@"^9.10.0" from @vue/[email protected]
npm error   node_modules/@vue/eslint-config-typescript
npm error     dev @vue/eslint-config-typescript@"^14.0.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 /tmp/renovate/cache/others/npm/_logs/2024-12-16T03_39_36_399Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-12-16T03_39_36_399Z-debug-0.log

@renovate renovate bot force-pushed the renovate/vue-eslint-config-typescript-14.x branch 15 times, most recently from 51ce751 to a5e9203 Compare October 15, 2024 18:58
@renovate renovate bot force-pushed the renovate/vue-eslint-config-typescript-14.x branch 13 times, most recently from d4320ca to f343eed Compare October 22, 2024 17:08
@renovate renovate bot force-pushed the renovate/vue-eslint-config-typescript-14.x branch 13 times, most recently from 17e5e39 to ad85c04 Compare December 3, 2024 11:25
@renovate renovate bot force-pushed the renovate/vue-eslint-config-typescript-14.x branch 14 times, most recently from d90ab26 to 86efea6 Compare December 11, 2024 15:08
@renovate renovate bot force-pushed the renovate/vue-eslint-config-typescript-14.x branch from 86efea6 to 564162f Compare December 14, 2024 12:18
@renovate renovate bot force-pushed the renovate/vue-eslint-config-typescript-14.x branch from 564162f to 95bb675 Compare December 16, 2024 03:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants