[dependabot]

Bumps the cargo-minor-patch group in /src-tauri with 8 updates:

Package	From	To
tauri-plugin-opener	2.7.2	2.7.3
tauri-plugin-notification	2.8.0	2.8.1
tauri-plugin-log	2.10.1	2.10.2
uuid	1.29.0	1.29.2
trash	5.2.9	5.3.0
notify	8.2.1	8.2.2
tauri-plugin-store	2.5.0	2.5.1
serde-saphyr	2.0.0	2.1.1

Updates tauri-plugin-opener from 2.7.2 to 2.7.3

Release notes

Sourced from tauri-plugin-opener's releases.

opener-js v2.7.3

[2.7.3]

• 74a44c1d (#3739 by @​ericroberts) Fixed automatic link opening to respect <base target="_blank"> when the link has no explicit target attribute.

npm warn publish npm auto-corrected some errors in your package.json when publishing.  Please run "npm pkg fix" to address these errors.
npm warn publish errors corrected:
npm warn publish "repository" was changed from a string to an object
npm warn publish "repository.url" was normalized to "git+https://github.com/tauri-apps/plugins-workspace.git"
npm notice
npm notice 📦  @tauri-apps/plugin-opener@2.7.3
npm notice Tarball Contents
npm notice 888B LICENSE.spdx
npm notice 4.2kB README.md
npm notice 3.1kB dist-js/index.cjs
npm notice 2.0kB dist-js/index.d.ts
npm notice 3.1kB dist-js/index.js
npm notice 11B dist-js/init.d.ts
npm notice 730B package.json
npm notice Tarball Details
npm notice name: @tauri-apps/plugin-opener
npm notice version: 2.7.3
npm notice filename: tauri-apps-plugin-opener-2.7.3.tgz
npm notice package size: 3.5 kB
npm notice unpacked size: 14.1 kB
npm notice shasum: a0a264bd038200bd616c0c390c6a812d10ce4e70
npm notice integrity: sha512-Nm+v7vLBCDzYZ[...]1/j0pmC9SmBVA==
npm notice total files: 7
npm notice
npm notice npm tokens that bypass 2FA are being restricted for account changes and direct publishing. Learn how to prepare: https://gh.io/npm-gat-bypass2fa-deprecation
npm notice Publishing to https://registry.npmjs.org/ with tag latest and public access
npm notice publish Signed provenance statement with source and build information from GitHub Actions
npm notice publish Provenance statement published to transparency log: https://search.sigstore.dev/?logIndex=3783436817
npm notice Your package is being processed and may take a few minutes to become available.
+ @tauri-apps/plugin-opener@2.7.3

opener v2.7.3

[2.7.3]

• 74a44c1d (#3739 by @​ericroberts) Fixed automatic link opening to respect <base target="_blank"> when the link has no explicit target attribute.

... (truncated)

Commits

• 6aa2854 publish new versions (#3509)
• 9d6d032 chore(deps): update h2 to 0.4.19 (#3556)
• 98f8787 ci: fix typo in workflow permissions
• 1a7b12c ci: add explicit token permissions
• 2f4c85c chore(deps): bump serde_with (#3490)
• c546de0 chore(deps): update dependency rollup to v4.62.5 (#3520)
• db9c599 fix(android): missing consumer-rules.pro (#3531)
• 9c93437 chore(deps): update dependency typescript-eslint to v8.66.0 (#3391)
• 685610a fix(fs): default permissions (#3507)
• f8053e6 docs: cargo features (#3527)
• Additional commits viewable in compare view

Updates tauri-plugin-notification from 2.8.0 to 2.8.1

Release notes

Sourced from tauri-plugin-notification's releases.

notification-js v2.8.1

[2.8.1]

• 52edb98e (#3758 by @​Lorkydey) Fix notification permission requests never resolving on Android 13 and newer when the permission has already been granted.

npm warn publish npm auto-corrected some errors in your package.json when publishing.  Please run "npm pkg fix" to address these errors.
npm warn publish errors corrected:
npm warn publish "repository" was changed from a string to an object
npm warn publish "repository.url" was normalized to "git+https://github.com/tauri-apps/plugins-workspace.git"
npm notice
npm notice 📦  @tauri-apps/plugin-notification@2.8.1
npm notice Tarball Contents
npm notice 888B LICENSE.spdx
npm notice 4.2kB README.md
npm notice 16.6kB dist-js/index.cjs
npm notice 27.0kB dist-js/index.d.ts
npm notice 16.2kB dist-js/index.js
npm notice 11B dist-js/init.d.ts
npm notice 663B package.json
npm notice Tarball Details
npm notice name: @tauri-apps/plugin-notification
npm notice version: 2.8.1
npm notice filename: tauri-apps-plugin-notification-2.8.1.tgz
npm notice package size: 11.4 kB
npm notice unpacked size: 65.7 kB
npm notice shasum: 7c90843110982e4e0b8d8417d168f85c44356d12
npm notice integrity: sha512-B+OCJv17XCFQx[...]ONclHeZn65mJA==
npm notice total files: 7
npm notice
npm notice npm tokens that bypass 2FA are being restricted for account changes and direct publishing. Learn how to prepare: https://gh.io/npm-gat-bypass2fa-deprecation
npm notice Publishing to https://registry.npmjs.org/ with tag latest and public access
npm notice publish Signed provenance statement with source and build information from GitHub Actions
npm notice publish Provenance statement published to transparency log: https://search.sigstore.dev/?logIndex=3783455244
npm notice Your package is being processed and may take a few minutes to become available.
+ @tauri-apps/plugin-notification@2.8.1

notification v2.8.1

[2.8.1]

• 52edb98e (#3758 by @​Lorkydey) Fix notification permission requests never resolving on Android 13 and newer when the permission has already been granted.

... (truncated)

Commits

• 7eb8246 publish new versions (#3673)
• 65ce65b fix(ci): Android e2e flakes, shell Terminated sent before output (#3672)
• cbd691b chore(examples): update Android project for API example
• 974bbdc publish new versions (#3667)
• 3113a54 chore(deps): update urlpattern to 0.6 (#3670)
• b443d6b fix(http): release the request's resources once fetch_send settles (#3669)
• 2a9c29e fix(updater): restore the current app when a macOS install fails (fix #3505, ...
• d4835d0 publish new versions (#3660)
• 569ee82 fix: mobile docs.rs builds
• 25f3874 chore(deps): update dependency eslint-plugin-security to v4.1.0 (#3661)
• Additional commits viewable in compare view

Updates tauri-plugin-log from 2.10.1 to 2.10.2

Release notes

Sourced from tauri-plugin-log's releases.

log-js v2.10.2

[2.10.2]

• 92e47a1c (#3718 by @​h55n) Fixed RotationStrategy::KeepSome never deleting .log.bak files created by same-second rotations, so the log directory could grow past the configured cap. Same-second rotations now pick a unique <name>_<date>_<n>.log name instead of overwriting the existing .log.bak, and the cleanup counts legacy .log.bak files against the keep cap.

npm warn publish npm auto-corrected some errors in your package.json when publishing.  Please run "npm pkg fix" to address these errors.
npm warn publish errors corrected:
npm warn publish "repository" was changed from a string to an object
npm warn publish "repository.url" was normalized to "git+https://github.com/tauri-apps/plugins-workspace.git"
npm notice
npm notice 📦  @tauri-apps/plugin-log@2.10.2
npm notice Tarball Contents
npm notice 888B LICENSE.spdx
npm notice 3.5kB README.md
npm notice 8.4kB dist-js/index.cjs
npm notice 4.7kB dist-js/index.d.ts
npm notice 8.2kB dist-js/index.js
npm notice 716B package.json
npm notice Tarball Details
npm notice name: @tauri-apps/plugin-log
npm notice version: 2.10.2
npm notice filename: tauri-apps-plugin-log-2.10.2.tgz
npm notice package size: 5.3 kB
npm notice unpacked size: 26.4 kB
npm notice shasum: f0ae0225dde23c6a88eaaffc4cb58f72569e88d0
npm notice integrity: sha512-Vx6uLv9GIqzrn[...]v1DiRcSyxI/Mw==
npm notice total files: 6
npm notice
npm notice npm tokens that bypass 2FA are being restricted for account changes and direct publishing. Learn how to prepare: https://gh.io/npm-gat-bypass2fa-deprecation
npm notice Publishing to https://registry.npmjs.org/ with tag latest and public access
npm notice publish Signed provenance statement with source and build information from GitHub Actions
npm notice publish Provenance statement published to transparency log: https://search.sigstore.dev/?logIndex=3783449570
npm notice Your package is being processed and may take a few minutes to become available.
+ @tauri-apps/plugin-log@2.10.2

log v2.10.2

[2.10.2]

• 92e47a1c (#3718 by @​h55n) Fixed RotationStrategy::KeepSome never deleting .log.bak files created by same-second rotations, so the log directory could grow past the configured cap. Same-second rotations now pick a unique <name>_<date>_<n>.log name instead of overwriting the existing .log.bak, and the cleanup counts legacy .log.bak files against the keep cap.

... (truncated)

Commits

• 8c588be test: disable load_close_race test on windows
• 3aa71fe publish new versions (#3742)
• b4a6ed0 ci: ignore exit code of first cargo-audit run
• a238eef ci: use prebuilt cargo-audit. print human-readable output.
• 2d0314d chore(deps): update dependency typescript-eslint to v8.72.1 (#3726)
• ff4a19d chore(deps): update dependency eslint to v10.14.0 (#3721)
• 011527a chore(deps): update dependency rollup to v4.67.5 (#3736)
• 52edb98 fix(notification): resolve granted Android permission requests (fix #3757) (#...
• 937f03b chore(deps): update dependency tslib to v2.9.1 (#3768)
• 92e47a1 fix(log): keep KeepSome cap across same-second rotations (#3718)
• Additional commits viewable in compare view

Updates uuid from 1.29.0 to 1.29.2

Release notes

Sourced from uuid's releases.

v1.29.2

What's Changed

• Support wasm64 in the js feature by @​nickbabcock in uuid-rs/uuid#928
• Prepare for 1.29.2 release by @​KodrAus in uuid-rs/uuid#929

New Contributors

• @​nickbabcock made their first contribution in uuid-rs/uuid#928

Full Changelog: uuid-rs/uuid@v1.29.1...v1.29.2

v1.29.1

What's Changed

• Remove some deprecated attrs and resolve Cargo lints by @​KodrAus in uuid-rs/uuid#921
• Deprecate the borsh feature of uuid in favour of a uuid feature in borsh by @​KodrAus in uuid-rs/uuid#923
• Fix up several bugs in v7 monotonicity raised by automated scanning by @​KodrAus in uuid-rs/uuid#926
• Prepare for 1.29.1 release by @​KodrAus in uuid-rs/uuid#927

Full Changelog: uuid-rs/uuid@v1.29.0...v1.29.1

Commits

• 5205a6e Merge pull request #929 from uuid-rs/cargo/v1.29.2
• ff39846 prepare for 1.29.2 release
• c879f61 Merge pull request #928 from nickbabcock/wasm64
• 4b57852 Support wasm64 in the js feature
• 0fe2dab Merge pull request #927 from uuid-rs/cargo/v1.29.1
• 8896d2e prepare for 1.29.1 release
• 2eef370 Merge pull request #926 from uuid-rs/fix/timestamp-edges
• de33fde fix up several bugs in v7 monotonicity raised by automated scanning
• 7c7326d Merge pull request #923 from uuid-rs/fix/deprecate-borsh
• 13e1ff0 deprecate the borsh feature of uuid in favour of a uuid feature in borsh
• Additional commits viewable in compare view

Updates trash from 5.2.9 to 5.3.0

Release notes

Sourced from trash's releases.

v5.3.0

Documentation

• configure docs.rs platform targets

  I reduced the target list to the 3 common ones. Let's see if it works.

  Recent docs.rs releases only expose Linux documentation. Explicitly request the five standard docs.rs targets so macOS and Windows documentation are included, keeping Linux first as the default landing page.

  A Cargo metadata assertion failed before the change because the docs.rs target list was absent, and passes with the configured targets.

New Features

• add Portal backend This only adds the basic functionality to make it work.

Bug Fixes

• preserve path prefixes when decoding slashes

  Decode the complete path byte string instead of collecting decoded components into a PathBuf. A component beginning with %2F previously discarded the prefix, redirected restoration to the filesystem root, and could erase relative parent traversal before validation.

  Add relative and absolute encoded-separator regressions, traversal rejection, and restoration coverage. The relative separator case fails before the fix.

• reject original paths without filenames

  Validate the decoded path before joining the trash base so dot paths cannot resolve to the base directory. Route roots and paths ending in parent components through the invalid-original-path warning as well.

  Add literal and encoded dot and parent regression cases. The dot-path case fails before the fix; the listing regression passes with and without chrono afterward.

• trim surrounding trashinfo path whitespace

  Trim both ends of the encoded Path value before decoding so trailing spaces and tabs do not become filename bytes. Extend the whitespace fixture while retaining encoded filename space coverage.

• report why the shell refused to recycle an item delete answered every item the shell skipped with Error::Unknown { "Some operations were aborted" }. With FOF_NO_UI a refused item is skipped, not asked about: PerformOperations and FinishOperations both report success, and only GetAnyOperationsAborted says that something

... (truncated)

Changelog

Sourced from trash's changelog.

5.3.0 (2026-11-05)

Documentation

• configure docs.rs platform targets

  I reduced the target list to the 3 common ones. Let's see if it works.

  Recent docs.rs releases only expose Linux documentation. Explicitly request the five standard docs.rs targets so macOS and Windows documentation are included, keeping Linux first as the default landing page.

  A Cargo metadata assertion failed before the change because the docs.rs target list was absent, and passes with the configured targets.

New Features

• add Portal backend This only adds the basic functionality to make it work.

Bug Fixes

• preserve path prefixes when decoding slashes

  Decode the complete path byte string instead of collecting decoded components into a PathBuf. A component beginning with %2F previously discarded the prefix, redirected restoration to the filesystem root, and could erase relative parent traversal before validation.

  Add relative and absolute encoded-separator regressions, traversal rejection, and restoration coverage. The relative separator case fails before the fix.

• reject original paths without filenames

  Validate the decoded path before joining the trash base so dot paths cannot resolve to the base directory. Route roots and paths ending in parent components through the invalid-original-path warning as well.

  Add literal and encoded dot and parent regression cases. The dot-path case fails before the fix; the listing regression passes with and without chrono afterward.

• trim surrounding trashinfo path whitespace

  Trim both ends of the encoded Path value before decoding so trailing spaces and tabs do not become filename bytes. Extend the whitespace fixture while retaining encoded filename space coverage.

• report why the shell refused to recycle an item delete answered every item the shell skipped with Error::Unknown { "Some operations were aborted" }. With FOF_NO_UI a refused item is skipped, not asked about: PerformOperations and FinishOperations both

... (truncated)

Commits

• 0fdaf8d Release trash v5.3.0
• dd2b8f7 Merge pull request #161 from Byron/fix/freedesktop-trashinfo-reviewed
• b6e2624 fix(freedesktop): preserve path prefixes when decoding slashes
• 4ee80bd fix(freedesktop): reject original paths without filenames
• 6fcae5b fix(freedesktop): trim surrounding trashinfo path whitespace
• e00d049 Merge pull request #158 from stefan-siebert/fix/windows-list-file-name
• b8f46cc Merge pull request #159 from stefan-siebert/fix/windows-report-hresult
• 0d0a038 review
• 8afaa34 fix(windows): report why the shell refused to recycle an item (#96)
• 7f63659 fix(windows): list items under their file name, extension included
• Additional commits viewable in compare view

Updates notify from 8.2.1 to 8.2.2

Release notes

Sourced from notify's releases.

notify: v8.2.2

notify 8.2.2 (2026-11-08)

• CHANGE: raise MSRV from 1.85 to 1.88 breaking
• FIX: [windows] prevent watch shutdown from rearming reads on closed handles, which could deadlock when handles are reused #958 #1051 #1052

#958: notify-rs/notify#958 #1051: notify-rs/notify#1051 #1052: notify-rs/notify#1052

Changelog

Sourced from notify's changelog.

notify 8.2.2 (2026-11-08)

• CHANGE: raise MSRV from 1.85 to 1.88 breaking
• FIX: [windows] prevent watch shutdown from rearming reads on closed handles, which could deadlock when handles are reused #958 #1051 #1052

#958: notify-rs/notify#958 #1051: notify-rs/notify#1051 #1052: notify-rs/notify#1052

Commits

• 603674a prepare notify 8.2.2 (#1084)
• 3386e5f windows: backport #958 (#1083)
• See full diff in compare view

Updates tauri-plugin-store from 2.5.0 to 2.5.1

Release notes

Sourced from tauri-plugin-store's releases.

store-js v2.5.1

[2.5.1]

• 685d3424 (#3746 by @​963s) Fixed a deadlock between loading a store and closing a store at the same time, which could freeze the main thread for good. StoreExt::get_store and the save on exit took the same two locks in the wrong order too. Store files are also no longer read while the plugin's stores lock is held.

npm warn publish npm auto-corrected some errors in your package.json when publishing.  Please run "npm pkg fix" to address these errors.
npm warn publish errors corrected:
npm warn publish "repository" was changed from a string to an object
npm warn publish "repository.url" was normalized to "git+https://github.com/tauri-apps/plugins-workspace.git"
npm notice
npm notice 📦  @tauri-apps/plugin-store@2.5.1
npm notice Tarball Contents
npm notice 888B LICENSE.spdx
npm notice 4.4kB README.md
npm notice 23.2kB dist-js/index.cjs
npm notice 25.2kB dist-js/index.d.ts
npm notice 23.0kB dist-js/index.js
npm notice 712B package.json
npm notice Tarball Details
npm notice name: @tauri-apps/plugin-store
npm notice version: 2.5.1
npm notice filename: tauri-apps-plugin-store-2.5.1.tgz
npm notice package size: 7.6 kB
npm notice unpacked size: 77.4 kB
npm notice shasum: 1d9f13ee32a8d2378a529a0770d1c0acc711cf78
npm notice integrity: sha512-lm/84hFRWHKay[...]DDHrPk1C5psaQ==
npm notice total files: 6
npm notice
npm notice npm tokens that bypass 2FA are being restricted for account changes and direct publishing. Learn how to prepare: https://gh.io/npm-gat-bypass2fa-deprecation
npm notice Publishing to https://registry.npmjs.org/ with tag latest and public access
npm notice publish Signed provenance statement with source and build information from GitHub Actions
npm notice publish Provenance statement published to transparency log: https://search.sigstore.dev/?logIndex=3783460421
npm notice Your package is being processed and may take a few minutes to become available.
+ @tauri-apps/plugin-store@2.5.1

store v2.5.1

[2.5.1]

• 685d3424 (#3746 by @​963s) Fixed a deadlock between loading a store and closing a store at the same time, which could freeze the main thread for good. StoreExt::get_store and the save on exit took the same two locks in the wrong order too. Store files are also no longer read while the plugin's stores lock is held.

... (truncated)

Commits

• 5c7668b publish new versions (#3397)
• ec05401 chore(deps): update rust crate toml to v1 (#3323)
• b86e999 chore(deps): update tauri packages to 2.11 (#3407)
• c463d8a chore(deps): update rustls-webpki in lockfile, ignore core2 in audit (#3405)
• 1bb7beb chore(deps): bump openssl (#3402)
• 3412fa2 docs(readme): fix platform support matrix (opener supports mobile)
• af81fda docs(readme): fix platform support matrix (mobile is supported)
• c1fd33b fix(opener): allow open network share locations (#3343)
• 250857b chore(deps): update dependency typescript to v6 (#3363)
• 964e13f fix(store): dead lock trying to set while exiting (#3395)
• Additional commits viewable in compare view

Updates serde-saphyr from 2.0.0 to 2.1.1

Release notes

Sourced from serde-saphyr's releases.

2.1.1 Optimization and maintenance release

Fixed

• Fixed 2.1.0 regression empty documents producing errors (#265). Empty document is a valid YAML document. Fix of this regression is the reason of making this release so early.

Performance improvements

• Significantly reduced allocations when deserializing (#262), thanks @​mat-gas

2.1.0 Minor feature extension, maintenance and performance release

Added

• Added opt-in Options::reject_tagged_field_names to catch misplaced tags on struct field names, with Error::TaggedStructFieldName diagnostics. Struct field names can only be strings; !!str is still accepted. As other tags can only be ignored, tag on a structure field name is almost for sure placed wrongly. This setting will be default in next major release.
• Added Options::leading_zero_numbers_as_strings and Options::underscored_numbers_as_strings to preserve numeric spellings such as 0755 and 1_000 as strings in untyped values, including untagged enums and flattened fields (#225). Both default to false; direct typed parsing, explicit numeric tags, and mapping-key comparison keep their existing behavior.
• Added Error::render_to to append diagnostics to any std::fmt::Write using RenderOptions, without collecting the complete output in an intermediate string (#221).
• Added DuplicateKeyPolicy::PassThrough to delegate repeated explicit mapping entries to Serde visitors, matching serde_yaml's handling for structs, standard maps, and custom multimap visitors (#226). The default remains Error; merge expansion retains its precedence rules. See the README migration note for the scope of this option.

Deprecated

• Deprecated SerializerOptions::empty_as_braces. Setting it to false emits YAML null for empty block collections without tags or anchors. These values do not round-trip into collection types. Omit the setting to keep the default true and emit [] or {}. Existing serialization behavior remains supported for compatibility.

Fixed

• Emit empty lines in literal and folded block scalars without indentation, avoiding trailing whitespace while preserving whitespace in the string content (#249).
• Expose the original std::io::Error from deserialization failures through std::error::Error::source(). The outer message is IO error, so error chains include the underlying cause only once. Standalone Miette, Figment, and Figment2 diagnostics retain the cause in their messages. Custom Miette formatters retain control over the complete message through MessageFormatter::format_standalone_message.
• Avoid duplicate messages from Error::WithSnippet when following std::error::Error::source() by forwarding the wrapped error's source. Use without_snippet() to inspect the wrapped error. Alias errors retain their complete source chain, including snippet wrappers, for compatibility.

... (truncated)

Changelog

Sourced from serde-saphyr's changelog.

2.1.1

Fixed

• Fixed 2.1.0 regression empty documents producing errors (#265). Empty document is a valid YAML document.

Performance improvements

• Significantly reduced allocations when deserializing (#262)

2.1.0

–

Added

• Added PropertySyntax::DockerComposeWithNulls: Compose interpolation where a value that is solely a reference to an unset property, or whose expansion is null/~, becomes YAML null. Explicitly empty properties and empty defaults stay empty strings, and DockerCompose itself is unchanged.
• Added opt-in Options::reject_tagged_field_names to catch misplaced tags on struct field names, with Error::TaggedStructFieldName diagnostics. Struct field names can only be strings, !!str is still accepted. As other tags can only be ignored, tag on a structure field name is almost for sure placed wrongly. This setting will be default in next major release.
• Added Options::leading_zero_numbers_as_strings and Options::underscored_numbers_as_strings to preserve numeric spellings such as 0755 and 1_000 as strings in untyped values, including untagged enums and flattened fields (#225). Both default to false; direct typed parsing, explicit numeric tags, and mapping-key comparison keep their existing behavior.
• Added Error::render_to to append diagnostics to any std::fmt::Write using RenderOptions, without collecting the complete output in an intermediate string (#221).
• Added DuplicateKeyPolicy::PassThrough to delegate repeated explicit mapping entries to Serde visitors, matching serde_yaml's handling for structs, standard maps, and custom multimap visitors (#226). The default remains Error; merge expansion retains its precedence rules. See the README migration note for the scope of this option.

Deprecated

• Deprecated SerializerOptions::empty_as_braces. Setting it to false emits YAML null for empty block collections without tags or anchors. These values do not round-trip into collection types. Omit the setting to keep the default true and emit [] or {}. Existing serialization behavior remains supported for compatibility.

Fixed

• Preserve application-tagged null-like documents in multi-document APIs, including the garde and validator integrations. A document such as !Maybe null now reaches enum dispatch instead of being skipped. This also affects default options: an Option<String> target receives a None item for !Foo null, while a String target reports NullIntoString. Untagged null documents and explicit !!null are still skipped.
• Resolve tagged enum payloads according to their target type under no_schema:

... (truncated)

Commits

• 07bfc26 Fix formatting
• a988642 Advance release version number
• ef4862b Restore empty YAML stream deserialization into collections (#265)
• 3501fa9 Reduce allocations when deserializing (#262)
• 38f4202 Removed unneeded here file
• 57f72d5 The failed parser now releases its cached error before conversion, preserving...
• 346afe2 Tag lookup optimization, this way confirmed to work faster.
• aa5d474 Number of tests goes over 4000
• 1cadc9c Prepare to 2.1.0 release
• 1d509d2 Add DockerComposeWithNulls with consistent null handling (#261)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions