Skip to content

fix(deps): update dependency vue to ^3.5.39 (stable32)#2774

Open
renovate[bot] wants to merge 1 commit into
stable32from
renovate/stable32-vue-monorepo
Open

fix(deps): update dependency vue to ^3.5.39 (stable32)#2774
renovate[bot] wants to merge 1 commit into
stable32from
renovate/stable32-vue-monorepo

Conversation

@renovate

@renovate renovate Bot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
vue (source) ^3.5.14^3.5.39 age confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

vuejs/core (vue)

v3.5.39

Compare Source

Bug Fixes

v3.5.38

Compare Source

v3.5.37

Compare Source

v3.5.36

Compare Source

Bug Fixes

v3.5.35

Compare Source

Bug Fixes
Performance Improvements

v3.5.34

Compare Source

Bug Fixes

v3.5.33

Compare Source

Bug Fixes

v3.5.32

Compare Source

Bug Fixes
Reverts

v3.5.31

Compare Source

Bug Fixes

v3.5.30

Compare Source

Bug Fixes

v3.5.29

Compare Source

Bug Fixes

Configuration

📅 Schedule: (in timezone Europe/Berlin)

  • Branch creation
    • "before 5am on saturday"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

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 added 4. to release dependencies Pull requests that update a dependency file labels Jul 6, 2026
@renovate renovate Bot enabled auto-merge July 6, 2026 18:21
@cypress

cypress Bot commented Jul 6, 2026

Copy link
Copy Markdown

Activity    Run #3935

Run Properties:  status check failed Failed #3935  •  git commit e1f863e334: fix(deps): update dependency vue to ^3.5.39 (stable32)
Project Activity
Branch Review renovate/stable32-vue-monorepo
Run status status check failed Failed #3935
Run duration 02m 17s
Commit git commit e1f863e334: fix(deps): update dependency vue to ^3.5.39 (stable32)
Committer renovate[bot]
View all properties for this run ↗︎

Test results
Tests that failed  Failures 1
Tests that were flaky  Flaky 0
Tests that did not run due to a developer annotating a test with .skip  Pending 1
Tests that did not run due to a failure in a mocha hook  Skipped 0
Tests that passed  Passing 8
View all changes introduced in this branch ↗︎

Tests for review

Failed  cypress/e2e/sidebar.cy.ts • 1 failed test • Run E2E

View Output

Test Artifacts
Check activity listing in the sidebar > Has share activity Test Replay Screenshots

@codecov

codecov Bot commented Jul 6, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@renovate renovate Bot force-pushed the renovate/stable32-vue-monorepo branch from 1e132b9 to 528dd88 Compare July 6, 2026 19:04
@renovate

renovate Bot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ 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: @vue/server-renderer@3.5.28
npm error Found: vue@3.5.39
npm error node_modules/vue
npm error   vue@"^3.5.39" from the root project
npm error   peer vue@"^3.2.0" from @ckpack/vue-color@1.6.0
npm error   node_modules/@ckpack/vue-color
npm error     @ckpack/vue-color@"^1.6.0" from @nextcloud/vue@9.5.0
npm error     node_modules/@nextcloud/vue
npm error       @nextcloud/vue@"^9.3.0" from the root project
npm error       1 more (@nextcloud/dialogs)
npm error   24 more (@nextcloud/dialogs, @vueuse/core, @vueuse/shared, ...)
npm error
npm error Could not resolve dependency:
npm error peer vue@"3.5.28" from @vue/server-renderer@3.5.28
npm error node_modules/@vue/server-renderer
npm error   peerOptional @vue/server-renderer@"3.x" from @vue/test-utils@2.4.11
npm error   node_modules/@vue/test-utils
npm error     dev @vue/test-utils@"^2.4.11" from the root project
npm error
npm error Conflicting peer dependency: vue@3.5.28
npm error node_modules/vue
npm error   peer vue@"3.5.28" from @vue/server-renderer@3.5.28
npm error   node_modules/@vue/server-renderer
npm error     peerOptional @vue/server-renderer@"3.x" from @vue/test-utils@2.4.11
npm error     node_modules/@vue/test-utils
npm error       dev @vue/test-utils@"^2.4.11" 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-07-12T15_18_59_947Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-07-12T15_18_59_947Z-debug-0.log

@renovate renovate Bot force-pushed the renovate/stable32-vue-monorepo branch from 528dd88 to 770c892 Compare July 7, 2026 15:46
@AndyScherzinger AndyScherzinger added this to the Nextcloud 32.0.13 milestone Jul 7, 2026
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate Bot force-pushed the renovate/stable32-vue-monorepo branch from 770c892 to 309be6e Compare July 12, 2026 15:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

4. to release dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant