publish new versions (#3675)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
2026-10-10 22:38:44 +02:00 · 2026-10-10 12:50:18 -03:00
1 parent fc18d05513
commit 6bbd44d4ef
@@ -1,6 +0,0 @@
---
-dialog: patch
-dialog-js: patch
---
-
-Fix browser `confirm` fails with `Uncaught dialog.confirm not allowed. Command not found`
@@ -1,6 +0,0 @@
---
-fs: minor
-fs-js: minor
---
-
-Added the `scopeDroppedPaths` plugin config option (`plugins > fs > scopeDroppedPaths` in `tauri.conf.json`). Set it to `false` to stop adding the paths dropped onto any window to the fs scope, which otherwise gives every webview with an fs permission access to them (directories recursively). Defaults to `true`, the current behaviour.
@@ -1,6 +0,0 @@
---
-fs: patch
-fs-js: patch
---
-
-Fixed a panic on Android when a content provider returns no file descriptor for a `content://` URI (e.g. virtual files). The fs command now fails with an error instead.
@@ -1,6 +0,0 @@
---
-fs: patch
-fs-js: patch
---
-
-Fixed reading uncompressed Android assets (`$RESOURCE` files such as images or audio that are stored uncompressed in the APK) returning the bytes of the APK instead of the asset. Assets are now always read from a copy in the app cache, like compressed ones.
@@ -1,6 +0,0 @@
---
-fs: patch
-fs-js: patch
---
-
-`startAccessingSecurityScopedResource` and `stopAccessingSecurityScopedResource` now accept absolute paths on iOS, as documented, instead of silently doing nothing unless given a `file://` URL.
@@ -1,6 +0,0 @@
---
-fs: patch
-fs-js: patch
---
-
-**Security:** the `open` command no longer accepts a `customFlags` option from the webview. It was not part of the JavaScript types and let the webview pass arbitrary `open(2)` flags (e.g. `O_TRUNC`) to files it may only read. `OpenOptionsExt::custom_flags` still works from Rust.
@@ -1,6 +0,0 @@
---
-fs: patch
-fs-js: patch
---
-
-`FileHandle.read` no longer allocates a buffer of the requested size up front: the length is capped to the rest of the file (64 MiB for files of unknown size), an allocation failure is reported as an error instead of aborting the app, and only the bytes that were read are sent back to the webview.
@@ -1,6 +0,0 @@
---
-fs: patch
-fs-js: patch
---
-
-**Security:** the fs scope check now resolves symlinks in the ancestors of paths that do not exist yet, and resolves relative symlink targets against the link's directory instead of the process working directory. Previously a new file created below a symlinked directory inside the scope (`writeFile`, `mkdir`, `create`, `rename`, `copyFile`, ...) was written outside of the scope. Deny patterns now also apply to the path as given, so they can name a symlink, and a path whose symlinks cannot be resolved (e.g. a loop) is rejected.
@@ -1,6 +0,0 @@
---
-fs: patch
-fs-js: patch
---
-
-`FileHandle.seek` now rejects a negative offset with `SeekMode.Start` instead of seeking to a huge position.
@@ -1,6 +0,0 @@
---
-fs: patch
-fs-js: patch
---
-
-Fixed `readTextFileLines` with a UTF-16 encoding splitting lines on a `0x0A 0x00` (LE) or `0x00 0x0A` (BE) byte sequence that is not aligned on a code unit, e.g. `ਗĀ`, which garbled every following line.
@@ -1,6 +0,0 @@
---
-fs: patch
-fs-js: patch
---
-
-Fixed `writeFile` with a `ReadableStream` leaving the end of the previous contents in place when the new data is shorter. The file is now truncated first unless `append` is set, like when writing a buffer.
@@ -1,6 +0,0 @@
---
-global-shortcut: patch
-global-shortcut-js: patch
---
-
-Release the shortcuts lock before running shortcut handlers, so a handler that calls back into the plugin, or pumps messages that dispatch another shortcut event, no longer deadlocks the app.
@@ -1,26 +0,0 @@
---
-barcode-scanner: patch
-biometric: patch
-clipboard-manager: patch
-dialog: patch
-geolocation: patch
-haptics: patch
-log: patch
-nfc: patch
-notification: patch
-opener: patch
-shell: patch
-barcode-scanner-js: patch
-biometric-js: patch
-clipboard-manager-js: patch
-dialog-js: patch
-geolocation-js: patch
-haptics-js: patch
-log-js: patch
-nfc-js: patch
-notification-js: patch
-opener-js: patch
-shell-js: patch
---
-
-On iOS, mark the plugin's `init_plugin_*` entry point `public` so release builds made with Xcode 27 keep it global and link.
@@ -1,8 +0,0 @@
---
-biometric: patch
-nfc: patch
-biometric-js: patch
-nfc-js: patch
---
-
-Fix compilation on iOS when the `wry` feature of `tauri` is not enabled by another crate.
@@ -1,8 +0,0 @@
---
-"notification": minor:feat
-"notification-js": minor:feat
---
-
-Report actions on desktop: a click on a notification (`tap`) or on one of the actions of its action type reaches `onAction` and the new Rust `Notification::on_action`, which also works on mobile. `registerActionTypes`, `removeActive` (Linux and the BSDs) and the listener commands no longer fail with "command not found" on desktop.
-
-The `onAction` callback is now typed with the new `ActionPerformed` interface, which is what every platform sends, instead of `Options`. Callbacks annotated with `Options` must be updated.
@@ -1,6 +0,0 @@
---
-"shell": minor
-"shell-js": minor
---
-
-Add `processGroup` option to spawn commands in a new process group (POSIX) or job object (Windows), allowing the entire process tree to be killed when calling `kill()` on the child process.
@@ -1,5 +0,0 @@
---
-"single-instance": patch
---
-
-On Windows, a second instance no longer waits indefinitely for a first instance that stopped processing messages: it stops waiting after 10 seconds and exits. The first instance may still receive the arguments once it resumes processing messages.
@@ -1,5 +0,0 @@
---
-"single-instance": patch
---
-
-A second instance no longer panics when a command-line argument is not valid Unicode: such an argument is forwarded with its invalid parts replaced by U+FFFD. A working directory that is not valid Unicode is now forwarded the same way instead of as an empty string.
@@ -1,6 +0,0 @@
---
-"updater": patch
-"updater-js": patch
---
-
-Update `minisign-verify` to 0.3, which rejects signatures with a non-canonical Ed25519 `S` value. The `Error::Minisign` variant now wraps `minisign_verify` 0.3's `Error`, and its message reads like "The signature verification failed" instead of the variant name (`InvalidSignature`).