Skip to content

fix(deps): update dependency @nextcloud/dialogs to v8 - #2901

Open
renovate[bot] wants to merge 2 commits into
mainfrom
renovate/nextcloud-dialogs-8.x
Open

renovate[bot] wants to merge 2 commits into
mainfrom
renovate/nextcloud-dialogs-8.x

Conversation

@renovate

@renovate renovate Bot commented Oct 27, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@nextcloud/dialogs ^7.5.0 → ^8.0.0 age confidence

Release Notes

nextcloud-libraries/nextcloud-dialogs (@​nextcloud/dialogs)

v8.0.0

Compare Source

Breaking
  • The styles are now imported automatically by the package entry points, so the @nextcloud/dialogs/style.css export was removed.
    Remove the import from your app:
- import '@nextcloud/dialogs/style.css'
  • The reworked - and accessible - toast notifications from v7.5.0 (reverted in v7.6.0) are back.
    Toasts no longer use toastify-js, the toast functions return a ToastHandle instead of a Toastify Toast.
  • Those new toast messages will be displayed on the bottom start of the page, this is by design and not a bug.
    Apps can adjust the toasts position with a CSS variable, the value is added to the default distance to the bottom (default: 0px):
:root {
	--toast-offset-block-end: 80px;
}
Added
Fixed
Changed
  • Updated p-queue to version 10.0.0
  • Updated development dependencies

v7.6.0

Compare Source

Notes

The reworked toast notifications from v7.5.0 were considered a breaking change and are moved to v8.
This version restores the previous toastify-js based toasts and removes the toast timeout configuration.

If your app only needs toasts, you can import them from the @nextcloud/dialogs/toast entry point instead.
(Note: Webpack issue - bundler might include other components source, e.g. the FilePicker, in the app)

import { showError } from '@nextcloud/dialogs/toast'
Added
Fixed
Changed
  • revert: accessible toast and toast timeout configuration #​2712 (Antreesy)
  • perf(FilePicker): replace NcActionInput with NcPopover and NcTextField #​2690 (Antreesy)
  • Updated translations
  • Updated development dependencies

Configuration

📅 Schedule: (in timezone Europe/Berlin)

  • Branch creation
    • "before 5am every weekday,every weekend"
  • 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 commented Oct 27, 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 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 warn ERESOLVE overriding peer dependency
npm warn While resolving: @nextcloud/image-editor@1.0.0-beta.7
npm warn Found: @nextcloud/dialogs@8.0.0
npm warn node_modules/@nextcloud/dialogs
npm warn   @nextcloud/dialogs@"^8.0.0" from the root project
npm warn
npm warn Could not resolve dependency:
npm warn peer @nextcloud/dialogs@"^7.0.0" from @nextcloud/image-editor@1.0.0-beta.7
npm warn node_modules/@nextcloud/image-editor
npm warn   @nextcloud/image-editor@"^1.0.0-beta.6" from @nextcloud/viewer@2.0.0-beta.19
npm warn   node_modules/@nextcloud/viewer
npm warn
npm warn Conflicting peer dependency: @nextcloud/dialogs@7.6.0
npm warn node_modules/@nextcloud/dialogs
npm warn   peer @nextcloud/dialogs@"^7.0.0" from @nextcloud/image-editor@1.0.0-beta.7
npm warn   node_modules/@nextcloud/image-editor
npm warn     @nextcloud/image-editor@"^1.0.0-beta.6" from @nextcloud/viewer@2.0.0-beta.19
npm warn     node_modules/@nextcloud/viewer
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @nextcloud/viewer@2.0.0-beta.19
npm error Found: @nextcloud/dialogs@8.0.0
npm error node_modules/@nextcloud/dialogs
npm error   @nextcloud/dialogs@"^8.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @nextcloud/dialogs@"^7.5.0" from @nextcloud/viewer@2.0.0-beta.19
npm error node_modules/@nextcloud/viewer
npm error   @nextcloud/viewer@"^2.0.0-beta.19" from the root project
npm error
npm error Conflicting peer dependency: @nextcloud/dialogs@7.6.0
npm error node_modules/@nextcloud/dialogs
npm error   peer @nextcloud/dialogs@"^7.5.0" from @nextcloud/viewer@2.0.0-beta.19
npm error   node_modules/@nextcloud/viewer
npm error     @nextcloud/viewer@"^2.0.0-beta.19" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps 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-10-27T01_21_40_395Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-10-27T01_21_40_395Z-debug-0.log

@github-actions
github-actions Bot enabled auto-merge October 27, 2026 01:22
@blizzz

blizzz commented Oct 28, 2026

Copy link
Copy Markdown
Member

npm warn peer @nextcloud/dialogs@"^7.0.0" from @nextcloud/image-editor@1.0.0-beta.7

Maybe the package-lock.json needs to be totally recreated once. It contains image-editor, while npm why tells me that there is not reason to have that dependency.

Apart of that, bumping dialogs would still fail as @nextcloud/viewer depends on ^7.5.0

@mejo-
mejo- force-pushed the renovate/nextcloud-dialogs-8.x branch from 13dd623 to e500a2a Compare November 2, 2026 12:29
@renovate

renovate Bot commented Nov 2, 2026

Copy link
Copy Markdown
Contributor Author

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@mejo-

mejo- commented Nov 2, 2026

Copy link
Copy Markdown
Member

@nextcloud/viewer still requires @nextcloud/dialogs 7.5.0, so we'll have to wait before being able to bump it in Collectives.

This branch has not been deployed

No deployments
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.

2 participants