Skip to content

chore(deps): update dependency @vue/tsconfig to ^0.9.0#2310

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/vue-tsconfig-0.x
Open

chore(deps): update dependency @vue/tsconfig to ^0.9.0#2310
renovate[bot] wants to merge 1 commit intomainfrom
renovate/vue-tsconfig-0.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Mar 3, 2026

This PR contains the following updates:

Package Change Age Confidence
@vue/tsconfig ^0.5.1^0.9.0 age confidence

Release Notes

vuejs/tsconfig (@​vue/tsconfig)

v0.9.0

Compare Source

Noticeable Changes
  • feat: update lib to ES2022 by @​Slessi in #​41
  • chore: move noUncheckedIndexedAccess from base config to the lib config [fa4423b]
    • This is because noUncheckedIndexedAccess may have false positives, making it hard for existing codebases to upgrade.
    • But for new codebases, it’s still recommended to enable this flag from the beginning.
New Contributors

Full Changelog: vuejs/tsconfig@v0.8.1...v0.9.0

v0.8.1

Compare Source

fix: do not turn on exactOptionalPropertyTypes for now [a235c5f]

Full Changelog: vuejs/tsconfig@v0.8.0...v0.8.1

v0.8.0

Compare Source

Breaking Changes


If you experience a significant number of type errors in your projects after upgrading to this version, you might want to consider a gradual approach to adopting the new options:

  • After upgrading to @vue/tsconfig, use supress-ts-errors (npx suppress-ts-errors && npx suppress-ts-errors vue src/**/*.vue) to insert @ts-expect-error comments in your current codebase.
  • This way, the stricter configuration will only apply to any new code you add, allowing you to address the existing errors later when you have more time.

Full Changelog: vuejs/tsconfig@v0.7.0...v0.8.0

v0.7.0

Compare Source

Breaking Changes

  • Set skipLibCheck: false in tsconfig.lib.json [cee76cf]
  • Require Vue.js >= 3.4

Full Changelog: vuejs/tsconfig@v0.6.0...v0.7.0

v0.6.0

Compare Source

Notable Changes

Full Changelog: vuejs/tsconfig@v0.5.1...v0.6.0


Configuration

📅 Schedule: Branch creation - "before 5am every weekday,every weekend" in timezone Europe/Berlin, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, 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 requested a review from max-nextcloud as a code owner March 3, 2026 00:42
@renovate renovate bot added the dependencies label Mar 3, 2026
@renovate renovate bot requested review from mejo- and silverkszlo as code owners March 3, 2026 00:42
@renovate renovate bot added the dependencies label Mar 3, 2026
@renovate
Copy link
Contributor Author

renovate bot commented Mar 3, 2026

⚠️ 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 warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @vue/tsconfig@0.9.0
npm error Found: vue@2.7.16
npm error node_modules/vue
npm error   vue@"^2.7.16" from the root project
npm error   peer vue@"^2.6.6" from @linusborg/vue-simple-portal@0.1.5
npm error   node_modules/@linusborg/vue-simple-portal
npm error     @linusborg/vue-simple-portal@"^0.1.5" from @nextcloud/vue@8.36.0
npm error     node_modules/@nextcloud/vue
npm error       @nextcloud/vue@"^8.36.0" from the root project
npm error   16 more (@nextcloud/vue, @nextcloud/vue-select, ...)
npm error
npm error Could not resolve dependency:
npm error peerOptional vue@"^3.4.0" from @vue/tsconfig@0.9.0
npm error node_modules/@vue/tsconfig
npm error   dev @vue/tsconfig@"^0.9.0" from the root project
npm error
npm error Conflicting peer dependency: vue@3.5.30
npm error node_modules/vue
npm error   peerOptional vue@"^3.4.0" from @vue/tsconfig@0.9.0
npm error   node_modules/@vue/tsconfig
npm error     dev @vue/tsconfig@"^0.9.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 /runner/cache/others/npm/_logs/2026-03-09T11_12_25_797Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-03-09T11_12_25_797Z-debug-0.log

@github-actions github-actions bot enabled auto-merge March 3, 2026 00:43
@renovate renovate bot force-pushed the renovate/vue-tsconfig-0.x branch 3 times, most recently from c80b07b to df5c63a Compare March 6, 2026 00:51
@renovate renovate bot force-pushed the renovate/vue-tsconfig-0.x branch from df5c63a to 6a4ac31 Compare March 9, 2026 11:12
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