chore(deps): update dependency @nextcloud/dialogs to ^4.2.6 (stable27)
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| @nextcloud/dialogs | ^4.2.2 -> ^4.2.6 |
Release Notes
nextcloud-libraries/nextcloud-dialogs (@​nextcloud/dialogs)
v4.2.6
What's Changed
- [stable4] fix public shares by @​susnux in https://github.com/nextcloud-libraries/nextcloud-dialogs/pull/1243
Full Changelog: https://github.com/nextcloud-libraries/nextcloud-dialogs/compare/v4.2.5...v4.2.6
v4.2.5
What's Changed
- [stable4] fix: Pin nextcloud/files to last resolved version by @​Pytal in https://github.com/nextcloud-libraries/nextcloud-dialogs/pull/1226
- chore: v4.2.5 by @​Pytal in https://github.com/nextcloud-libraries/nextcloud-dialogs/pull/1227
Full Changelog: https://github.com/nextcloud-libraries/nextcloud-dialogs/compare/v4.2.4...v4.2.5
v4.2.4
What's Changed
- [stable4] fix(l10n): Update translations from main branch by @​susnux in https://github.com/nextcloud-libraries/nextcloud-dialogs/pull/1217
- chore: Prepare 4.2.4 release by @​susnux in https://github.com/nextcloud-libraries/nextcloud-dialogs/pull/1220
Full Changelog: https://github.com/nextcloud-libraries/nextcloud-dialogs/compare/v4.2.3...v4.2.4
v4.2.3
v4.2.3 (2024-01-19)
:bug: Fixed bugs
- fix(FilePicker): Use Node::path for current path fixing an clicking favorite folders #​1167 (susnux)
Changed
- Updated dependencies
Configuration
📅 Schedule: Branch creation - "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 has been generated by Mend Renovate. View repository job log here.
/compile
/compile
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.