chore(deps): update rust crate ctor to v1

[renovate]

This PR contains the following updates:

Package	Type	Update	Change	Pending
ctor	dependencies	major	0.8 → 1.0	1.0.7

---

Release Notes

mmastrac/linktime (ctor)

v1.0.6

Compare Source

What's Changed

Changed

• Bump link-section dependency to 0.17.0.
• MSRV bumped to 1.85.0 (if priority feature is enabled), otherwise remains at
  1.60.0.
  • To restore MSRV to 1.60.0, use ctor = { version = "1.0.6", default-features = false, features = ["proc_macro", "std"] } in your Cargo.toml.

Fixed

• #[ctor] requires significantly less macro recursion.

Full Changelog: mmastrac/linktime@ctor-1.0.5...ctor-1.0.6

v1.0.5

Compare Source

What's Changed

• Ensure WASM meets MSRV of 1.85 by @​mmastrac in #​455

Full Changelog: mmastrac/linktime@ctor-1.0.4...ctor-1.0.5

v1.0.4

Compare Source

What's Changed

• Use target_os=windows rather than target_vendor=pc by @​mmastrac in #​443
• Add uefi support (.init_array) by @​mmastrac in #​444
• Fall back to .init_array on unsupported platforms by @​mmastrac in #​445

Full Changelog: mmastrac/linktime@ctor-1.0.3...ctor-1.0.4

v1.0.3

Compare Source

What's Changed

• Fix unsafe C library access with default priority value by @​mmastrac in #​442

Other changes

• BSD test improvements by @​mmastrac in #​438
• Simplify cargo clean CI setup by @​mmastrac in #​439
• Add more BSDs to CI by @​mmastrac in #​417
• Bump clitest by @​mmastrac in #​440

Full Changelog: mmastrac/linktime@ctor-1.0.2...ctor-1.0.3

v1.0.2

Compare Source

What's Changed

• Improvements to static items for #[ctor]
• const dynamic ctors - use a const block to initialize a set of ctors

• Update link-section behaviour for WASM targets by @​mmastrac in #​426
  github.com/mmastrac/linktime/pull/42828
• Add const option for link-section by @​mmastrac in #​430
• Improved link-section WASM implementation by @​mmastrac in #​431
• Update crate metadata by @​mmastrac in #​432
• Allow various forms of &'static for static ctors by @​mmastrac in #​435
• Allow "optional" ctors where the ctors can be generated by a const function by @​mmastrac in #​436

Full Changelog: mmastrac/linktime@ctor-1.0.1...ctor-1.0.2

v1.0.1

Compare Source

What's Changed

• Fix duplicated ctor calls in WASM #​422

Full Changelog: mmastrac/linktime@ctor-1.0.0...ctor-1.0.1

v1.0.0

Compare Source

What's Changed

• Cleanup pass on build scripts by @​mmastrac in #​416
• Release 1.0 (🎉) by @​mmastrac in #​414

Full Changelog: mmastrac/linktime@ctor-0.13.1...ctor-1.0.0

v0.13.1

Compare Source

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[github-actions]

Package Changes Through 51deaff

There are 3 changes which include tauri-utils with patch, tauri-bundler with patch, tauri 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-utils	2.9.2	2.9.3
tauri-bundler	2.9.2	2.9.3
tauri-runtime	2.11.2	2.11.3
tauri-runtime-wry	2.11.2	2.11.3
tauri-codegen	2.6.2	2.6.3
tauri-macros	2.6.2	2.6.3
tauri-plugin	2.6.2	2.6.3
tauri-build	2.6.2	2.6.3
tauri	2.11.2	2.11.3
@tauri-apps/cli	2.11.2	2.11.3
tauri-cli	2.11.2	2.11.3

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

---

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

[FabianLars]

10 breaking changes in the last 2 weeks and now stable v1? i wonder how that will play out 😂

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: crates/tauri-utils/Cargo.toml

Artifact update for ctor resolved to version 1.0.7, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 1.0.6
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/