chore: release v0.1.11

[github-actions]

🤖 New release

• rusty_time-core: 0.1.10 -> 0.1.11
• rusty_time-nts: 0.1.10 -> 0.1.11
• rusty_time-clock: 0.1.10 -> 0.1.11
• rusty_time-api: 0.1.10 -> 0.1.11 (✓ API compatible changes)
• rusty_time-alloc: 0.1.10 -> 0.1.11
• rusty_time-daemon: 0.1.10 -> 0.1.11
• rusty_time-ctl: 0.1.10 -> 0.1.11 (✓ API compatible changes)
• rusty_time-wasm: 0.1.10 -> 0.1.11
• rusty_time-sim: 0.1.10 -> 0.1.11

Changelog

rusty_time-api

0.1.11 - 2026-09-06

Other

• Merge remote-tracking branch 'origin/main' into feat/tracking-op
• serve the tracking op from the discipline loop

rusty_time-alloc

0.1.10 - 2026-08-28

Other

• bump rusty_alloc-api to =1.1.6 (#2)

rusty_time-daemon

0.1.11 - 2026-09-06

Other

• Merge remote-tracking branch 'origin/main' into feat/tracking-op
• serve the tracking op from the discipline loop

rusty_time-ctl

0.1.11 - 2026-09-06

Other

• Merge remote-tracking branch 'origin/main' into feat/tracking-op
• serve the tracking op from the discipline loop

---

This PR was generated with release-plz.

[Ttimmahlax]

Superseded and now unsafe to merge.

This release PR was opened on 2026-08-29 against a workspace at 0.1.10 and proposes 0.1.11. The workspace has since gone to 0.2.0 (breaking: rusty_time-core gained a no_std leaf and now gates its std-only modules behind a default-on std feature, so default-features = false narrows — see #6), and release-plz published all nine crates at 0.2.0 directly, because the manifest version was already ahead of the registry.

Merging this now would move the manifests backwards to 0.1.11, below what is on crates.io. Closing rather than leaving it to be merged by accident; release-plz will open a fresh one when there is a next release.