* fix(core): `restart` cannot handle binary name change on macOS
Tauri v2 changed the default binary name of the bundled apps (no longer follows the productName, just uses the default name from Cargo instead). This breaks the `restart` function, which expects the current binary path to match the new one.
Due to this change, the restart() function for macOS is broken - the .app is correctly replaced even if the productName changed, but the restart() function cannot handle the new binary path. This change adds a simple check on macOS to read the `Contents/MacOS` folder and if it only contains a single binary, we use it to restart instead.
This inference cannot be used if there's sidecars, so in this case we just let the existing implementation run and if it fails to restart, we do not panic but only warn and exit instead.
AppImage updates are not affected by this, and the Windows installer is responsible for restarting, so this change is only applied to macOS binaries.
* fix: use Info.plist to determine binary name
* use log instead of eprintln
* move log
* fix#10935
Check if window has __TAURI_INVOKE__ before using it blindly.
* Update core/tauri/scripts/init.js
---------
Co-authored-by: Lucas Fernandes Nogueira <lucas@tauri.app>
* feat(bundler): store main binary name to be used in registry for furture updates
* revert wix changes as leftover binaries are fixed by https://github.com/tauri-apps/tauri/pull/10967
* feat(updater): support updating using non-zipped files
* minor
* fix compilation
* clippy
* pass `/UPDATE` to NSIS installer on updates
* clippy
* revert user-agent change
* add v1 -> v2 migration e2e test
* fix npm exec on windows
* downgrade serial-test for msrv
* fix sig ext for nsis v2
* fix windows e2e test
* add lcense headers
* fix conflict on e2e test on windows [skip ci]
---------
Co-authored-by: Lucas Nogueira <lucas@tauri.studio>
* chore(deps) Update Tauri Bundler
* ci: Also check bundler and cli in msrv check
* fix
* 1
* 2
* 3
* msrv
* downgrade handlebars again
* x
* x
* x
* x
* x
* x
* this makes no sense
* srsly wtf
* me dumb dumb
* bufreader
* x
* x
* changefile
* fix permissions
---------
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Lucas Nogueira <lucas@tauri.app>
* fix(core): fallback to file system for AssetResolver::get, closes#8411
Changes the AssetResolver::get implementation to fallback to reading the distDir directly when using the development mode pointing to a external URL (which is the way most people use the dev mode and means there's no embedded assets to pull from).
* fix clippy
* fix test
* clippy
* clippy2
* update time
* test if an uninitialized iframe can call the ipc
* test that calls without __TAURI_INVOKE_KEY__ fail
* fix cargo manifest newline change
* add comment to help unknown error message changes
* license headers
* add identifier and icons to config
* fix clippy error
* Create change-pr-9983.md
* add tag to changefile
* rename changefile
* feat(bundler/windows): Update wix to fix vulnerbilities and add arm support
* is this what it's complaining about?
* delete change file
---------
Co-authored-by: Lucas Nogueira <lucas@tauri.app>
* Use WinShell instead of ApplicationID
* Uninst shortcut before removing start menu one
* Use nsis's buit-in com plugin instead of WinShell
* Remove download ApplicationID code
* Add change file
* Clippy and format
* Allow dead code on extract_zip
* Qualify extract_zip path to make clippy happy
* Move macro up
Co-authored-by: Tony <68118705+Legend-Master@users.noreply.github.com>
* ci: Fix publishing of cli-macos-x64
* temp: only publish darwin-x64
* temp: wrong version
* temp: disable everything but darwin-x64
* temp: wrong test arch...
* temp: last one
* temp: last one for realsies
* remove temp stuff
* revert more
* fix(bundler): Don't convert product name to snake case when cross compiling
fixes#9221
* Update bundler-cross-uppercase-productname.md
* Update .changes/bundler-cross-uppercase-productname.md
* fix(core/path): remove suffix in basename only once
ref: #9064
* Update tooling/api/src/path.ts
---------
Co-authored-by: Lucas Fernandes Nogueira <lucas@tauri.app>
* fix: taurignore ignoreing folders not working for watch
* docs: add to changes
* fix: panic: path is expected to be under the root
* Update taurignore-ignoring-folders-not-working-for-watch.md
* Update taurignore-ignoring-folders-not-working-for-watch.md
* fix(bundler): escape potentially problematic strings in an XML (#9030)
- replace characters invalid in XML with their escaped form to properly bundle resources with such characters in their pathnames.
* change file
* fix(clipboard): fail to build on wayland
* specify exact version
* bump MSRV to 1.63
* revert msrv changes
---------
Co-authored-by: Amr Bashir <amr.bashir2015@gmail.com>
* fix(core): Retain order of map keys in ipc, fixes#7922
* enable dep on http-api feature instead of http-request
* Create fix-formbody-order.md
* Update fix-formbody-order.md
* fix(cli): Watch workspace members if tauri dir is ws root
See title. This PR also includes a fix/workaround for paths with funny characters that may not make the glob expansion panic.
Fixes#8509
* extract into function
* cleanup
* feat(bundler): codesign nested code on macos
* chore: update changelog tag
* typo
* also sign stuff in the Libraries folder
tested this for spacedrive, which has a bunch of dylib inside the libraries folder
* Update .changes/mac-bundler-nested-code-sign.md [skip ci]
---------
Co-authored-by: Lucas Nogueira <lucas@tauri.app>
* fix(core): Prevent crash when sending events.
* add change file
* use dedicated type for windows refcell map
---------
Co-authored-by: Lucas Nogueira <lucas@tauri.app>
Co-authored-by: Lucas Nogueira <lucas@tauri.studio>
* refactor(api): generate types next to modules"
this fixes an issue with `moduleResolution: node`
* change file
* Update api-module-resolution-node.md
* feat(core): Add additional functions to the
* Add documentation and cleanup the code
* Improve and add tests to helper functions
* Clean unecessary code and correct tests
* Make `Ipc` and `IpcKey` public
* Open `Ipc` with public functions
* Update core/tauri/src/test/mod.rs
Co-authored-by: Lucas Fernandes Nogueira <lucas@tauri.app>
* cleanup, change file
---------
Co-authored-by: Lucas Fernandes Nogueira <lucas@tauri.app>
Co-authored-by: Lucas Nogueira <lucas@crabnebula.dev>
* perf: Skip large Window and AppHandle fields on traces
These contain large fields like image buffers, causing spans/events to be very large when serialized.
Especially the `window::emit::eval` one which is in a hot code path.
* fix: MSRV issues
* fix(bundler): Fix nsis installer taking longer than expected to install resources
* create dir structure for resources before extracting files
* calculate size in rust on the build system
* i'm sorry clippy, i programmed in unholy languages where += wasn't a thing so i forgot it exists in rust...
* i'm a better clippy than clippy🌚
* fix(api): do nothing in clearMocks if __TAURI_INTERNALS__ is not defined (fix: #8179)
Prevents tests that didn't define any mocks from failing in `afterEach` test hook.
* Update fix-clearmocks.md
* check for indvidiual properties instead
Co-authored-by: Lucas Fernandes Nogueira <lucas@tauri.app>
Co-authored-by: lucasfernog <lucasfernog@users.noreply.github.com>
fix(bundler): team ID is now required for notarytool via app password (#7972)
fix(bundler): team ID is now required for notarytool via app password (#7972)"
* fix(bundler): Use escaped installer path when starting the updater setup, fixes#7931
* fun ci stuff
* who needs lockfiles anyway
* stahp
* please let it be the last one. i want to leave
* chore: resolves a warning seen while running cargo update
warning: some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"`
note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest
note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest
* Now using resolver 2.
* fix(bundler/nsis): delete app data of current user when uninstall, closes#7588
* fix(bundler/nsis): delete app data of current user when uninstall, closes#7588
* Update .changes/fix-nsis-uninstall-delete-app-data.md
---------
* fix(bundler/nsis): use temp dir for webview2 installer, closes#7409
* Update .changes/fix-nsis-webview2-installer-use-tempdir.md
---------
Co-authored-by: Amr Bashir <amr.bashir2015@gmail.com>
* ci: check for change tag
* fix workflow
* Update .scripts/ci/check-change-tags.js
* feat: also check if tag is known
seems like covector does not check that so we can do it here for now
* remove push run
* only check changed files
* add missing tag
---------
Co-authored-by: Lucas Fernandes Nogueira <lucas@tauri.studio>
* feat: try_get_item() for window menu
Add a method in the MenuHandle struct, that will return an Optional MenuItemHandle
feat: try_get_item() for systemtray
Add a method in the SystemTrayHandle struct, that will return an Optional SystemTrayMenuItemHandle
docs: features documented in ./changes/minor.md
fix: suggested changes
fix CI
* Update .changes/tray_get_item.md
---------
* fix(bundler): ensure that there are no duplicate extension arguments during bundling on Windows (fix#6103)
* fix(bundler): ensure that there are no duplicate extension arguments during bundling on Windows (fix#6103)
* refactor: add useful diagnostics to `tauri info`
this also paves the way for interactive fixes in the future
* refactor: add useful diagnostics to `tauri info`
this also paves the way for interactive fixes in the future
* fix use_npm logic [skip ci]
* lint [skip ci]
---------
Co-authored-by: Lucas Nogueira <lucas@tauri.studio>
* docs: update formdata usage
* update generated files
* update generated files
* run workflow on push for dev only
* remove `js-api.json` from generated files check
* restore js-api.json before checking diff
As you create PRs and make changes that require a version bump, please add a new markdown file in this folder. You do not note the version _number_, but rather the type of bump that you expect: major, minor, or patch. The filename is not important, as long as it is a `.md`, but we recommend that it represents the overall change for organizational purposes.
When you select the version bump required, you do _not_ need to consider dependencies. Only note the package with the actual change, and any packages that depend on that package will be bumped automatically in the process.
Use the following format:
```md
---
"package-a": patch
"package-b": patch
---
Change summary goes here
```
Summaries do not have a specific character limit, but are text only. These summaries are used within the (future implementation of) changelogs. They will give context to the change and also point back to the original PR if more details and context are needed.
Changes will be designated as a `major`, `minor` or `patch` as further described in [semver](https://semver.org/).
Given a version number MAJOR.MINOR.PATCH, increment the:
- MAJOR version when you make incompatible API changes,
-MINOR version when you add functionality in a backwards compatible manner, and
- PATCH version when you make backwards compatible bug fixes.
Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format, but will be discussed prior to usage (as extra steps will be necessary in consideration of merging and publishing).
# Changes
##### via https://github.com/jbolda/covector
As you create PRs and make changes that require a version bump, please add a new markdown file in this folder. You do not note the version _number_, but rather the type of bump that you expect: major, minor, or patch. The filename is not important, as long as it is a `.md`, but we recommend that it represents the overall change for organizational purposes.
When you select the version bump required, you do _not_ need to consider dependencies. Only note the package with the actual change, and any packages that depend on that package will be bumped automatically in the process.
Use the following format:
```md
---
'package-a': patch
'package-b': patch
---
Change summary goes here
```
Summaries do not have a specific character limit, but are text only. These summaries are used within the (future implementation of) changelogs. They will give context to the change and also point back to the original PR if more details and context are needed.
Changes will be designated as a `major`, `minor` or `patch` as further described in [semver](https://semver.org/).
Given a version number MAJOR.MINOR.PATCH, increment the:
- MAJOR version when you make incompatible API changes,
- MINOR version when you add functionality in a backwards compatible manner, and
-PATCH version when you make backwards compatible bug fixes.
Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format, but will be discussed prior to usage (as extra steps will be necessary in consideration of merging and publishing).
Additionally you could specify a tag for the change file to group it with other changes by prefixing the bump with `:<tag>`, for example:
```md
---
'package-a': patch:bug
---
Change summary goes here
```
which will group this change file with other changes that specify the `bug` tag.
For list of available tags, see the `changeTags` key in [./config.json](./config.json)
@@ -54,20 +54,20 @@ Some Tauri packages will be automatically built when running one of the examples
### Packages Overview
- The JS API (`/tooling/api`) contains JS bindings to the builtin Rust functions in the Rust API.
- cli.rs (`/tooling/cli`) is the primary CLI for creating and developing Tauri apps.
- cli.js (`/tooling/cli/node`) is a Node.js CLI wrapper for `cli.rs`.
- Tauri Bundler (`/tooling/bundler`) is used by the Rust CLI to package executables into installers.
- Tauri Core (`/core/tauri`) is the heart of Tauri. It contains the code that starts the app, configures communication between Rust and the Webview, and ties all the other packages together.
- The Macros (`/core/tauri-macros`) are used by Tauri Core for various functions.
### Developing The Node.js CLI (cli.js)
`cli.js` is a wrapper to `cli.rs` so most changes should be written on the Rust CLI. The `[Tauri repo root]/tooling/cli/node` folder contains only packaging scripts to properly publish the Rust CLI binaries to NPM.
- Tauri Bundler (`/tooling/bundler`) is used by the Rust CLI to package executables into installers.
- The Rust CLI aka `tauri-cli` (`/tooling/cli`) is the primary CLI for creating and developing Tauri apps.
- The JS CLI aka `@tauri-apps/cli` (`/tooling/cli/node`) is a Node.js CLI wrapper for `tauri-cli`.
- The JS API aka `@tauri-apps/api` (`/tooling/api`) contains JS bindings to the builtin Rust functions in the Rust API.
### Developing Tauri Bundler and Rust CLI
The code for the bundler is located in `[Tauri repo root]/tooling/bundler`, and the code for the Rust CLI is located in `[Tauri repo root]/tooling/cli`. If you are using your local copy of cli.js (see above), any changes you make to the bundler and CLI will be automatically built and applied when running the build or dev command. Otherwise, running `cargo install --path .` in the Rust CLI directory will allow you to run `cargo tauri build` and `cargo tauri dev` anywhere, using the updated copy of the bundler and cli. You will have to run this command each time you make a change in either package.
The code for the bundler is located in `[Tauri repo root]/tooling/bundler`, and the code for the Rust CLI is located in `[Tauri repo root]/tooling/cli`. If you are using your local copy of `@tauri-apps/cli` (see above), any changes you make to the bundler and CLI will be automatically built and applied when running the build or dev command. Otherwise, running `cargo install --path .` in the Rust CLI directory will allow you to run `cargo tauri build` and `cargo tauri dev` anywhere, using the updated copy of the bundler and cli. You will have to run this command each time you make a change in either package.
### Developing The Node.js CLI (`@tauri-apps/cli`)
`@tauri-apps/cli` is a wrapper to `tauri-cli` so most changes should be written on the Rust CLI. The `[Tauri repo root]/tooling/cli/node` folder contains only packaging scripts to properly publish the Rust CLI binaries to NPM.
### Developing Tauri Core and Related Components (Rust API, Macros, Codegen, and Utils)
Before submitting a PR, please read https://github.com/tauri-apps/tauri/blob/dev/.github/CONTRIBUTING.md#pull-request-guidelines
Please make sure to read the Pull Request Guidelines: https://github.com/tauri-apps/tauri/blob/dev/.github/CONTRIBUTING.md#pull-request-guidelines
1. Give the PR a descriptive title.
Examples of good title:
- fix(windows): fix race condition in event loop
- docs: update docstrings
- feat: add `Window::set_fullscreen`
Examples of bad title:
- fix #7123
- update docs
- fix bugs
2. If there is a related issue, reference it in the PR text, e.g. closes #123.
3. If this change requires a new version, then add a change file in `.changes` directory with the appropriate bump, see https://github.com/tauri-apps/tauri/blob/dev/.changes/readme.md
4. Ensure that all your commits are signed https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits
5. Ensure `cargo test` and `cargo clippy` passes.
6. Propose your changes as a draft PR if your work is still in progress.
-->
### What kind of change does this PR introduce?
<!-- Check at least one. If you are introducing a new binding, you must reference an issue where this binding has been proposed, discussed and approved by the maintainers. -->
- [ ] Bugfix
- [ ] Feature
- [ ] Docs
- [ ] New Binding issue #___
- [ ] Code style update
- [ ] Refactor
- [ ] Build-related changes
- [ ] Other, please describe:
### Does this PR introduce a breaking change?
<!-- If yes, please describe the impact and migration path for existing applications in an attached issue. -->
- [ ] Yes, and the changes were approved in issue #___
- [ ] No
### Checklist
- [ ] When resolving issues, they are referenced in the PR's title (e.g `fix: remove a typo, closes #___, #___`)
- [ ] A change file is added if any packages will require a version bump due to this PR per [the instructions in the readme](https://github.com/tauri-apps/tauri/blob/dev/.changes/readme.md).
- [ ] I have added a convincing reason for adding this feature, if necessary
A TypeScript library that creates `cjs` and `esm` JavaScript endpoints for you to import into your Frontend framework so that the Webview can call and listen to backend activity. We also ship the pure TypeScript, because for some frameworks this is more optimal. It uses the message passing of webviews to their hosts.
The bundler is a library that builds a Tauri App for the platform triple it detects / is told. At the moment it currently supports macOS, Windows and Linux - but in the near future will support mobile platforms as well. May be used outside of Tauri projects.
It is a wrapper around [cli.rs](https://github.com/tauri-apps/tauri/blob/dev/tooling/cli) using [napi-rs](https://github.com/napi-rs/napi-rs) to produce NPM packages for each platform.
It is a wrapper around [tauri-cli](https://github.com/tauri-apps/tauri/blob/dev/tooling/cli) using [napi-rs](https://github.com/napi-rs/napi-rs) to produce NPM packages for each platform.
This rust executable provides the full interface to all of the required activities for which the CLI is required. It will run on macOS, Windows, and Linux.
This is the delivery mechanism for tauri prebuilt binaries: currently the cli.rs (used by cli.js) and rustup binaries (used by the deps install command of cli.js). These artifacts are automatically created on release.
This is a github workflow that builds tauri binaries for all platforms. It is not the fastest out there, but it gets the job done and is highly configurable. Even allowing you to create a (very basic) tauri app even if tauri is not setup.
@@ -119,7 +116,7 @@ This will do several things:
1. start the JS Framework devserver
2. begin the long process of downloading and compiling the rust libraries
3. open an application window with devtools enabled
4. keep a long-lived console alive
4. keep a long-lived console alive
If you change your HTML/CSS/TS/JS, your framework devserver should give you its best shot at instant hot module reloading and you will see the changes instantly.
@@ -149,7 +146,7 @@ After some time, the process will end and you can see the results in the `./src-
End users will be provided with binaries in ways that are appropriate for their systems. Whether macOS, Linux, or Windows, direct download or store installations - they will be able to follow procedures for installing and removing that they are used to.
## What does the Updating flow look like?
When a new version is ready, the developer publishes the new signed artifacts to a server (that they have configured within `tauri.conf.json`).
When a new version is ready, the developer publishes the new signed artifacts to a server (that they have configured within `tauri.conf.json`).
The application can poll this server to see if there is a new release. When there is a new release, the user is prompted to update. The application update is downloaded, verified (checksum & signature), updated, closed, and restarted.
- [`2e87e85f8`](https://www.github.com/tauri-apps/tauri/commit/2e87e85f8550eccf2a3b23a36b135f3ad682509e) ([#10976](https://www.github.com/tauri-apps/tauri/pull/10976) by [@FabianLars](https://www.github.com/tauri-apps/tauri/../../FabianLars)) The executable and NSIS installer on Windows will now use the `productName` config for the `FileDescription` property instead of `shortDescription`.
## \[1.5.4]
### What's Changed
- [`fbcbc5ef7`](https://www.github.com/tauri-apps/tauri/commit/fbcbc5ef7cb5e3a69e3c23d6af24c8d340ae5f6b) ([#10392](https://www.github.com/tauri-apps/tauri/pull/10392) by [@github-actions](https://www.github.com/tauri-apps/tauri/../../github-actions)) Emit `cargo:rustc-check-cfg` instruction so Cargo validates custom cfg attributes on Rust 1.80 (or nightly-2024-05-05).
### Dependencies
- Upgraded to `tauri-codegen@1.4.5`
- Upgraded to `tauri-utils@1.6.1`
## \[1.5.3]
### Dependencies
- Upgraded to `tauri-utils@1.6.0`
- Upgraded to `tauri-codegen@1.4.4`
## \[1.5.2]
### Dependencies
- Upgraded to `tauri-utils@1.5.4`
- Upgraded to `tauri-codegen@1.4.3`
## \[1.5.1]
### Dependencies
- Upgraded to `tauri-utils@1.5.2`
- Upgraded to `tauri-codegen@1.4.2`
## \[1.5.0]
### What's Changed
- [`d1e09da0`](https://www.github.com/tauri-apps/tauri/commit/d1e09da084b849b9e384fc27ed250dd17e72c7a3)([#7918](https://www.github.com/tauri-apps/tauri/pull/7918)) Bump to 1.5 due to tauri-utils dependency bump.
## \[1.4.1]
### Bug Fixes
- [`5ecb46b3`](https://www.github.com/tauri-apps/tauri/commit/5ecb46b3410afd1b5c82494c1e0a91d5a358c41a)([#7773](https://www.github.com/tauri-apps/tauri/pull/7773)) Automatically set rpath on macOS if frameworks are bundled and copy frameworks to `src-tauri/target/Frameworks` for usage in development.
- [`290e366a`](https://www.github.com/tauri-apps/tauri/commit/290e366ae98e9a52b1b43bfd3e285150427ebffa)([#7419](https://www.github.com/tauri-apps/tauri/pull/7419)) Correctly copy the WebView2 runtime in development when `webviewInstallMode` is used instead of `webviewFixedRuntimePath`.
### Dependencies
- Upgraded to `tauri-utils@1.5.0`
- Upgraded to `tauri-codegen@1.4.1`
## \[1.4.0]
### Enhancements
- [`52474e47`](https://www.github.com/tauri-apps/tauri/commit/52474e479d695865299d8c8d868fb98b99731020)([#7141](https://www.github.com/tauri-apps/tauri/pull/7141)) Enhance Cargo features check.
- [`af937290`](https://www.github.com/tauri-apps/tauri/commit/af93729031565a69d1fde6cf16bea3b9b6e43a65)([#6676](https://www.github.com/tauri-apps/tauri/pull/6676)) On Windows, set `LegalCopyright` and `FileDescription` file properties on the executable from `tauri.bundle.copyright` and `tauri.bundle.shortDescription`,
- [`d2710e9d`](https://www.github.com/tauri-apps/tauri/commit/d2710e9d2e8fd93975ef6494512370faa8cb3b7e)([#6944](https://www.github.com/tauri-apps/tauri/pull/6944)) Unpin `time`, `ignore`, and `winnow` crate versions. Developers now have to pin crates if needed themselves. A list of crates that need pinning to adhere to Tauri's MSRV will be visible in Tauri's GitHub workflow: https://github.com/tauri-apps/tauri/blob/dev/.github/workflows/test-core.yml#L85.
## \[1.3.0]
- Bump minimum supported Rust version to 1.60.
- [5fdc616d](https://www.github.com/tauri-apps/tauri/commit/5fdc616df9bea633810dcb814ac615911d77222c) feat: Use the zbus-backed of notify-rust ([#6332](https://www.github.com/tauri-apps/tauri/pull/6332)) on 2023-03-31
- Add initial support for building `nsis` bundles on non-Windows platforms.
- [60e6f6c3](https://www.github.com/tauri-apps/tauri/commit/60e6f6c3f1605f3064b5bb177992530ff788ccf0) feat(bundler): Add support for creating NSIS bundles on unix hosts ([#5788](https://www.github.com/tauri-apps/tauri/pull/5788)) on 2023-01-19
- Add `WindowsAttributes::app_manifest` to specify the application manifest on Windows.
- [bca09f7f](https://www.github.com/tauri-apps/tauri/commit/bca09f7f5ff1c9c5a4b51da043bdd5da668a179b) feat(tauri-build): add option to specify Windows manifest, closes [#5584](https://www.github.com/tauri-apps/tauri/pull/5584) ([#5730](https://www.github.com/tauri-apps/tauri/pull/5730)) on 2022-12-14
- Added support for Cargo's workspace inheritance for package information. The cli now also detects inherited `tauri` and `tauri-build` dependencies and disables manifest rewrites accordingly.
- [cd8c074a](https://www.github.com/tauri-apps/tauri/commit/cd8c074ae6592303d3f6844a4fb6d262eae913b2) feat(cli): add support for Cargo's workspace inheritance for the package version, closes [#5070](https://www.github.com/tauri-apps/tauri/pull/5070) ([#5775](https://www.github.com/tauri-apps/tauri/pull/5775)) on 2022-12-14
- [d20a7288](https://www.github.com/tauri-apps/tauri/commit/d20a728892eee1858ab525ab6216cd721f473ab5) feat: Further improve workspace inheritance, closes [#6122](https://www.github.com/tauri-apps/tauri/pull/6122), [#5070](https://www.github.com/tauri-apps/tauri/pull/5070) ([#6144](https://www.github.com/tauri-apps/tauri/pull/6144)) on 2023-01-26
- Pin `winnow` crate to 0.4.1 to keep the 1.60 MSRV.
"Cannot define a sidecar with the same name as the Cargo package name `{}`. Please change the sidecar name in the filesystem and the Tauri configuration.",
- [`67b7ca6ef`](https://www.github.com/tauri-apps/tauri/commit/67b7ca6ef45b2b1eda97cd2a917fc98b24d90be1) ([#10356](https://www.github.com/tauri-apps/tauri/pull/10356) by [@github-actions](https://www.github.com/tauri-apps/tauri/../../github-actions)) Enhance `AssetResolver::get` in development mode by reading distDir directly as a fallback to the embedded assets.
### Bug Fixes
- [`a3946222b`](https://www.github.com/tauri-apps/tauri/commit/a3946222b3047247cc46c7336ea1026f78bec012) ([#10433](https://www.github.com/tauri-apps/tauri/pull/10433) by [@github-actions](https://www.github.com/tauri-apps/tauri/../../github-actions)) Fixes asset resolving when not using the `compression` feature.
### Dependencies
- Upgraded to `tauri-utils@1.6.1`
## \[1.4.4]
### Dependencies
- Upgraded to `tauri-utils@1.6.0`
## \[1.4.3]
### Dependencies
- Upgraded to `tauri-utils@1.5.4`
## \[1.4.2]
### Dependencies
- Upgraded to `tauri-utils@1.5.2`
## \[1.4.1]
### Dependencies
- Upgraded to `tauri-utils@1.5.0`
## \[1.4.0]
### Enhancements
- [`17d5a4f5`](https://www.github.com/tauri-apps/tauri/commit/17d5a4f51f244d3ff42014b5d1b075fad7c636a5)([#6706](https://www.github.com/tauri-apps/tauri/pull/6706)) Early panic if the PNG icon is not RGBA.
- [`d2710e9d`](https://www.github.com/tauri-apps/tauri/commit/d2710e9d2e8fd93975ef6494512370faa8cb3b7e)([#6944](https://www.github.com/tauri-apps/tauri/pull/6944)) Unpin `time`, `ignore`, and `winnow` crate versions. Developers now have to pin crates if needed themselves. A list of crates that need pinning to adhere to Tauri's MSRV will be visible in Tauri's GitHub workflow: https://github.com/tauri-apps/tauri/blob/dev/.github/workflows/test-core.yml#L85.
## \[1.3.0]
- Bump minimum supported Rust version to 1.60.
- [5fdc616d](https://www.github.com/tauri-apps/tauri/commit/5fdc616df9bea633810dcb814ac615911d77222c) feat: Use the zbus-backed of notify-rust ([#6332](https://www.github.com/tauri-apps/tauri/pull/6332)) on 2023-03-31
- Pin `time` to `0.3.15`.
- [3d16461b](https://www.github.com/tauri-apps/tauri/commit/3d16461b68583ba7db037fbc217786e79b46ddf2) fix(core): pin time to 0.3.15 ([#6312](https://www.github.com/tauri-apps/tauri/pull/6312)) on 2023-02-19
// Copyright 2019-2022 Tauri Programme within The Commons Conservancy
// Copyright 2019-2023 Tauri Programme within The Commons Conservancy
// SPDX-License-Identifier: Apache-2.0
// SPDX-License-Identifier: MIT
Some files were not shown because too many files have changed in this diff
Show More
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
