[pull] dev from tauri-apps:dev #112
Open
+47,088
−63,831
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![pull[bot]](https://avatars.githubusercontent.com/in/12910?s=60&v=4){kind=small}
* feat: add `Window::set_enabled` and `Window::is_enabled` closes #6660 * license headers * fix build * fix mobile and macos * fix macos * again * unsafe * fix macos is_enabled * update example --------- Co-authored-by: Lucas Nogueira <[email protected]>
Co-authored-by: lucasfernog <[email protected]>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…#11184) * fix(cli): iOS app signature not retaining entitlements, closes #11089 The IPA does not retain the entitlements as a regression from #10854 which removed the signing step from the build() and archive(), deferring to the export() call To retain the entitlements we need to force sign one of the files in the app bundle. The most reliable way to do this is to use a self signed certificate as a dummy signature - it is replaced by the export() call so we do not rely on any user provided certificate Additionally the export options are incorrectly configuring a manual signing, preventing Xcode from properly managing provisioning profiles, which is also part of the fix * fix header
lets us catch runtime errors early on the testing phase - for instance when we add two arguments with the same flag
…id devices, closes #11137 (#11185) * feat(cli): enhance Android dev port forwarding, closes #11137 this changes the `android dev` port forwarding (that is actually handled by the `android-studio-script` command - triggered by our Gradle plugin) with some enhancements: - make the whole process more resilient by checking if the port was actually forwarded and rerunning the `adb reverse` command until it tells us the forward is ready - if the `adb devices` list is empty, retry a few times (waiting a few seconds) to tolerate devices being booted - slows down "raw builds" (Build Project Android Studio menu for instance) that shouldn't happen often anyway - if you're running `android dev` you're usually running the app on a device instead of simply testing builds * use host IP to run on android physical device
Co-authored-by: lucasfernog <[email protected]>
* chore: promote to v2 stable - deletes all RC change files - adds a new change file to promote all packages to v2 stable - manually fix the tauri-driver, tauri-macos-sign, tauri-bundler versions so the next covector bump will move them to 2.0.0 - manually patch the metadata-v2.json file so the next covector update will mark all packages as 2.0.0 * ignore audit vuln without fixes * bump msrv to 1.78 * run covector version * fix sync lockfile covector * #[allow(clippy::manual_inspect)]
Co-authored-by: lucasfernog <[email protected]>
* fix: downgrade MSRV to 1.77.2 to support Windows 7 * add chang file
* chore(tauri): enhance Manager::add_capability documentation * enhance example * add note on config
Co-authored-by: tweidinger <[email protected]>
we missed one `--tag next` usage in #11199
custom IPC systems that manually call Webview::on_message must know the invoke key checked by Tauri. This exposes that key in the App/AppHandle instances. This is safe because the key is never leaked to remote denied webview URLs
Co-authored-by: lucasfernog <[email protected]>
…n binary if has spaces (#11218) * fix(bundler): wrap `Exec` in desktop with quotes, rename appimage main binary if has spaces * Update .changes/main-binary-name-spaces-linux.md [skip ci[ --------- Co-authored-by: Lucas Fernandes Nogueira <[email protected]>
Co-authored-by: FabianLars <[email protected]>
* ci: Switch to upstream create-pull-request * what the actual f * fix version comment --------- Co-authored-by: Tillmann <[email protected]>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: FabianLars <[email protected]>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: FabianLars <[email protected]>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Fabian-Lars <[email protected]>
Co-authored-by: Max Katz <[email protected]>
Co-authored-by: Fabian-Lars <[email protected]>
Even though I couldn't even get the build to succeed when using the team name as the "developmentTeam" configuration (instead of the team ID), I've received reports that our processing of that value is broken and only works when it is escaped using `\"`.
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
It currently isn't possible to simply add a community plugin the same was as adding official plugins.
Trying to perform `npm run tauri add tauri-plugin-python` is trying to install npm package `@tauri-apps/plugin-python`.
But the npm scope `@tauri-apps/` is reserved for official tauri plugins.
The official documentation recommends to name the npm package `tauri-plugin-{name}-api` and it should be possible to have a parameter that makes it possible to install that package.
- closes #12217
This changes the command to check if the plugin is an official tauri plugin or not, using the appropriate npm package name format
---------
Co-authored-by: Lucas Nogueira <[email protected]>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: FabianLars <[email protected]>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: FabianLars <[email protected]>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: FabianLars <[email protected]>
Co-authored-by: FabianLars <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot]
Can you help keep this open source service alive? 💖 Please sponsor : )