chore(deps): update objc2-* crates to 0.3.2

[Legend-Master]

In preparation for tauri-apps/wry#1737

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	cargo/​objc2-app-kit@​0.3.0 ⏵ 0.3.2
	cargo/​objc2-foundation@​0.3.0 ⏵ 0.3.2
	cargo/​objc2-ui-kit@​0.3.0 ⏵ 0.3.2
	cargo/​objc2-web-kit@​0.3.0 ⏵ 0.3.2

View full report

[github-actions]

Package Changes Through 04125a4

There are 14 changes which include tauri with minor, tauri-cli with minor, @tauri-apps/cli with minor, tauri-runtime with minor, tauri-runtime-wry with minor, tauri-utils with minor, tauri-bundler with minor, tauri-build with minor, tauri-macos-sign with minor, tauri-codegen with minor, tauri-macros with minor, tauri-plugin with minor, tauri-driver with minor, @tauri-apps/api with minor

Planned Package Versions

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

package	current	next
@tauri-apps/api	2.11.1	2.12.0
tauri-utils	2.9.3	2.10.0
tauri-macos-sign	2.3.4	2.4.0
tauri-bundler	2.9.4	2.10.0
tauri-runtime	2.11.3	2.12.0
tauri-runtime-wry	2.11.4	2.12.0
tauri-codegen	2.6.3	2.7.0
tauri-macros	2.6.3	2.7.0
tauri-plugin	2.6.3	2.7.0
tauri-build	2.6.3	2.7.0
tauri	2.11.5	2.12.0
@tauri-apps/cli	2.11.4	2.12.0
tauri-cli	2.11.4	2.12.0
tauri-driver	2.0.6	2.1.0

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

---

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

[Legend-Master]

Not sure if it's needed for the tauri and tauri-runtime crates, but just bumped them anyways that we have tauri-runtime-wry on 0.3.2 anyways.

Edit: yeah we need it I guess 04125a4

[sftse]

AFAIK this is a bit of a footgun in Rust. If the version is above 1.0.0 I think it's legitimate to leave out the patch number, but in 0.x.y versions I think there's less guidance on what the patch number means? In 1.x.y versions it's possible to pick a misleading minor version x and not notice it because Cargo defaults to the most recent version, so may pick 1.9.0 even if we put 1.7.0 in the Cargo.toml. People that do try to compile it with 1.7.0 can have a broken build.

Not sure if that is related to your question, but it did catch me off guard once.

[Legend-Master]

Patch versions are to indicate both patch and minor versions for pre 1.0 versions I think

https://doc.rust-lang.org/cargo/reference/semver.html#:~:text=Initial%20development%20releases%20starting%20with%20%E2%80%9C0.y.z%E2%80%9D%20can%20treat%20changes%20in%20%E2%80%9Cy%E2%80%9D%20as%20a%20major%20release%2C%20and%20%E2%80%9Cz%E2%80%9D%20as%20a%20minor%20release.