Skip to content

Conversation

@kandrelczyk
Copy link
Contributor

No description provided.

kandrelczyk and others added 30 commits March 18, 2025 23:30
Signed-off-by: Krzysztof Andrelczyk <cristof@curiana.net>
Signed-off-by: Krzysztof Andrelczyk <cristof@curiana.net>
…auri-apps#12998)

* fix: use bun.lock to identify bun's lockfile

* fix: also check bun.lockb

* doc: add changes doc
…i-apps#12643)

* feat(uninstaller): remove autostart entry during uninstallation

Signed-off-by: animeshchaudri <animeshchaudhri3@gmail.com>

* add change file

* check when not updating

* delete registry value only if install mode is "currentUser"

---------

Signed-off-by: animeshchaudri <animeshchaudhri3@gmail.com>
Co-authored-by: Lucas Nogueira <lucas@tauri.app>
* docs: clarify Capability::windows/webviews OR nature

It is intuitive to expect that for the capability to be enabled,
_both_ the window label and the webview label have to match.
However, this is not the case: the capability is enabled
if _either_ the window label matches a pattern
in `Capability::windows` _or_ the webview label matches a pattern
in `Capability::webviews`.

This commit should somewhat clarify this oddity
and protect developers from adding excessive permissions.

For reference, `Capability::webviews` was added in
0cb0a15
(tauri-apps#8789).

* Apply suggestions from code review

Co-authored-by: Amr Bashir <github@amrbashir.me>

* update schemas

---------

Co-authored-by: Amr Bashir <github@amrbashir.me>
Co-authored-by: Lucas Nogueira <lucas@tauri.app>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
* docs: remove outdated `tauri_build::build` docs

The docstring has been unchanged ever since
40ac529 (2021).
The `build()` function has grown massivly since then,
now it's not only about Windows.

* docs: `tauri_build::build`: see `try_build` for more config

`try_build` is not only about not panicing, but it also takes the
`attributes: Attributes` argument,
which is very important for controlling command permissions.

* Update crates/tauri-build/src/lib.rs

Co-authored-by: Amr Bashir <github@amrbashir.me>

* update docs

---------

Co-authored-by: Amr Bashir <github@amrbashir.me>
Co-authored-by: Lucas Nogueira <lucas@tauri.app>
Bumps [zip](https://github.com/zip-rs/zip2) from 2.2.2 to 2.3.0.
- [Release notes](https://github.com/zip-rs/zip2/releases)
- [Changelog](https://github.com/zip-rs/zip2/blob/master/CHANGELOG.md)
- [Commits](zip-rs/zip2@v2.2.2...v2.3.0)

---
updated-dependencies:
- dependency-name: zip
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
The initial version of the MR that introduced this to Wry
(tauri-apps/wry#1496)
had no Android implementation, but it has been added
in a later version of the MR, so the comment is no longer valid.
…13012)

* feat(core): resolve file names from Android content URIs

This PR adds a new Android path plugin function to resolve file names from content URIs. `PathResolver::file_name` was added to expose this API on Rust, and the existing `@tauri-apps/api/path` basename and extname function now leverages it on Android.

Closes tauri-apps/plugins-workspace#1775

Tauri core port from tauri-apps/plugins-workspace#2421

Co-authored-by: VulnX

* update change file [skip ci]

Co-authored-by: VulnX <62636727+VulnX@users.noreply.github.com>

---------

Co-authored-by: VulnX <62636727+VulnX@users.noreply.github.com>
* fix: channel no longer being always allowed

* Prettier

* Don't change the plugin name just yet

* Handle TAURI_CHANNEL as a special case in macro

* remove commented out code

---------

Co-authored-by: Lucas Nogueira <lucas@tauri.app>
…apps#13033)

* fix: don't ship global api bundle if withGlobalTauri is false

* Comment and prettier
they include necessary bug fixes for the 2.4 release
Co-authored-by: lucasfernog <20051258+lucasfernog@users.noreply.github.com>
Otherwise people might use it and not realize
that `App::run` also takes the callback argument,
which could be useful for some.
…tauri-apps#13057)

* enhance: include permissions in default permission description

* Only include in schema

* Remove 'which includes` to tauri's build script

* Also bump utils

* Clippy
My local clippy didn't report this, weird

* Use `which enables all commands`
for default permissions that enables everything

* Extract description into a variable

* Generate permissions with or without description

* Tweak the docs and generate 'which includes'

* Simplify to just `includes`

* Docs change change file

* Put the change in minor

* Update .changes/include-permissions-in-schema.md

Co-authored-by: Amr Bashir <amr.bashir2015@gmail.com>

* Remove unused change file

---------

Co-authored-by: Amr Bashir <amr.bashir2015@gmail.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Pietagorh and others added 18 commits April 7, 2025 23:10
* chore(deps-dev): bump vite from 6.2.3 to 6.2.4

Bumps [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) from 6.2.3 to 6.2.4.
- [Release notes](https://github.com/vitejs/vite/releases)
- [Changelog](https://github.com/vitejs/vite/blob/v6.2.4/packages/vite/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite/commits/v6.2.4/packages/vite)

---
updated-dependencies:
- dependency-name: vite
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <support@github.com>

* Update esbuild

---------

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Tony <legendmastertony@gmail.com>
* fix(cli): merge config based on the first one

* Add change file
* fix(cli): preserve null when merging patches

* add test

* remove commented out code

---------

Co-authored-by: Lucas Nogueira <lucas@tauri.app>
Co-authored-by: lucasfernog <20051258+lucasfernog@users.noreply.github.com>
…apps#13076)

* api!: expose api to run initialisation scripts on all frames.

* remove breaking change, add new api instead.

* Update .changes/init-script-on-all-frames.md

Co-authored-by: Tony <68118705+Legend-Master@users.noreply.github.com>

* use struct `InitializationScript` instead of tuple

* Update crates/tauri-runtime/src/webview.rs

Co-authored-by: Tony <68118705+Legend-Master@users.noreply.github.com>

* Apply suggestions from code review

* Update crates/tauri/src/webview/webview_window.rs

---------

Co-authored-by: Tony <68118705+Legend-Master@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
* fix: `run_return` not responding to `restart`

* Document run_return will handle restart requests

* Add change file
…ps#13131)

* chore: fix a few internal docs

* Remove label clone

* Unused allow lint

* No way clippy just updated

* `cargo clippy --fix -- -W clippy::redundant_clone`

* format
Bumps [openssl](https://github.com/sfackler/rust-openssl) from 0.10.70 to 0.10.72.
- [Release notes](https://github.com/sfackler/rust-openssl/releases)
- [Commits](rust-openssl/rust-openssl@openssl-v0.10.70...openssl-v0.10.72)

---
updated-dependencies:
- dependency-name: openssl
  dependency-version: 0.10.72
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) from 6.2.4 to 6.2.5.
- [Release notes](https://github.com/vitejs/vite/releases)
- [Changelog](https://github.com/vitejs/vite/blob/v6.2.5/packages/vite/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite/commits/v6.2.5/packages/vite)

---
updated-dependencies:
- dependency-name: vite
  dependency-version: 6.2.5
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…czyk/tauri into feature/binary_patch_bundle_type
@kandrelczyk kandrelczyk requested a review from a team as a code owner April 8, 2025 20:53
@github-project-automation github-project-automation bot moved this to 📬Proposal in Roadmap Apr 8, 2025
@kandrelczyk kandrelczyk marked this pull request as draft April 8, 2025 20:59
@github-actions
Copy link
Contributor

github-actions bot commented Apr 9, 2025

Package Changes Through bb86910

There are 3 changes which include tauri with minor, tauri-runtime with minor, tauri-cli with patch

Planned Package Versions

The following package releases are the planned based on the context of changes in this pull request.

package current next
tauri-runtime 2.5.1 2.6.0
tauri-runtime-wry 2.5.1 2.5.2
tauri 2.4.1 2.5.0
@tauri-apps/cli 2.4.1 2.4.2
tauri-cli 2.4.1 2.4.2

Add another change file through the GitHub UI by following this link.


Read about change files or the docs at github.com/jbolda/covector

@lucasfernog
Copy link
Member

maybe we should use https://github.com/denoland/sui instead

@lucasfernog
Copy link
Member

lucasfernog commented Apr 11, 2025

btw what's exactly the goal of this PR? to support WiX/NSIS at the same time? changing the updater target is a breaking change (cargo-packager fixes this by adding a package format field in the update JSON)

@kandrelczyk
Copy link
Contributor Author

@lucasfernog sorry, this PR is a mess so I turned it into a draft. I have a cleaner one coming, will try to create it today.

I will link the original issue there. Closing this one for now.

@amrbashir
Copy link
Member

amrbashir commented Apr 11, 2025

btw what's exactly the goal of this PR? to support WiX/NSIS at the same time? changing the updater target is a breaking change (cargo-packager fixes this by adding a package format field in the update JSON)

This doesn't break anything, it merely embeds metadata that we can read in the updater plugin and perform certain actions/cleanups when updating.

This could also fix some guessing work we do regarding updates, like when updating .deb or .rpm, we need to know which package manager to use, instead of guessing and falling back if our guess was incorrect

@lucasfernog
Copy link
Member

yeah i meant just the target change would be breaking, adding the format would be ok

@FabianLars
Copy link
Member

The target change is also not breaking if we add the fallback logic. At least that was the plan when we last talked about this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: 📬Proposal

Development

Successfully merging this pull request may close these issues.