chore: Release [email protected], ic-cdk-executor@2, ic-cdk-timers@1 (#676)

Author: adamspofford-dfinity

Cargo.toml

@@ -32,11 +32,11 @@ opt-level = 'z'
 
 [workspace.dependencies]
 ic0 = { path = "ic0", version = "1.0.1" }
-ic-cdk = { path = "ic-cdk", version = "0.19.0-beta.3" }
+ic-cdk = { path = "ic-cdk", version = "0.19.0" }
 ic-cdk-bindgen = { path = "ic-cdk-bindgen", version = "0.2.0-alpha.2" }
-ic-cdk-timers = { path = "ic-cdk-timers", version = "1.0.0-beta.1" }
-ic-cdk-executor = { path = "ic-cdk-executor", version = "2.0.0-beta.1" }
-ic-management-canister-types = { path = "ic-management-canister-types", version = "0.4.1" }
+ic-cdk-timers = { path = "ic-cdk-timers", version = "1.0.0" }
+ic-cdk-executor = { path = "ic-cdk-executor", version = "2.0.0" }
+ic-management-canister-types = { path = "ic-management-canister-types", version = "0.5.0" }
 
 candid = "0.10.18"      # sync with the doc comment in ic-cdk/README.md
 candid_parser = "0.2.1"

TROUBLESHOOTING.md

@@ -17,10 +17,10 @@ Only one package in the dependency graph may specify the same links value. This
 failed to select a version for `ic-cdk-executor` which could resolve this conflict
 ```
 
-You have two incompatible versions of `ic-cdk` in your dependency tree. There are two common reasons for this.
+You have two incompatible versions of `ic-cdk` (or `ic-cdk-timers`) in your dependency tree. There are two common reasons for this.
 
-First, a dependency may be using an older (or newer) version of the CDK. Many versions are compatible with each other, but versions 0.17 and earlier are incompatible with version 0.18, and 0.18 is incompatible with 0.19 or later. You will have to wait for those dependencies to update, or patch them yourself.
+First, a dependency may be using an older (or newer) version of the CDK. Many versions of `ic-cdk` are compatible with each other, but versions 0.17 and earlier are incompatible with version 0.18, and 0.18 is incompatible with 0.19 or later. `ic-cdk-timers` does not have non-semver compatibility and any two versions are incompatible. In either case you will have to wait for those dependencies to update, or patch them yourself.
 
-Second, a dependency may be using a nominally compatible version of the CDK, but you are using a GitHub prerelease of the CDK with `ic-cdk = { git =`. Git dependencies are automatically incompatible with everything, even if nothing changed. You will need to create a [patch table](https://doc.rust-lang.org/cargo/reference/overriding-dependencies.html) that replaces `ic-cdk` with a Git dependency at the same commit (you may also need to replace `ic-cdk-executor`).
+Second, a dependency may be using a nominally compatible version of the CDK, but you are using a GitHub prerelease of the CDK with `ic-cdk = { git =`. Git dependencies are automatically incompatible with everything, even if nothing changed. You will need to create a [patch table](https://doc.rust-lang.org/cargo/reference/overriding-dependencies.html) that replaces all CDK dependencies with a Git dependency at the same commit.
 
 You can find the dependencies responsible with the command `cargo tree -i ic-cdk`.

ic-cdk-executor/CHANGELOG.md

@@ -7,12 +7,12 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## Unreleased
 
-## [2.0.0-beta.1] - 2025-10-09
+## [2.0.0] - 2025-11-13
 
 ### Changed
 
 - Breaking: The API has been significantly revised.
-    - `spawn` has been replaced with `spawn_local` and `spawn_migratory`. Local tasks are cancelled when the method ends.
+    - `spawn` has been replaced with `spawn_protected` and `spawn_migratory`. Protected tasks are cancelled when the method ends.
     - Contexts are now 'tracking', meaning that they know when canister methods start and end. Calls to `ic0.call_*` must be accompanied by `extend_current_method_context`; `in_callback_executor_context_for` takes this value.
     - Cancellation is no longer done per-task with the waker, but per-method with the function `cancel_all_tasks_attached_to_current_method`.
 

ic-cdk-executor/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "ic-cdk-executor"
-version = "2.0.0-beta.1"
+version = "2.0.0"
 authors.workspace = true
 edition.workspace = true
 repository.workspace = true

ic-cdk-macros/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "ic-cdk-macros"
-version = "0.19.0-beta.3"                                                            # sync with ic-cdk
+version = "0.19.0"                                                                   # sync with ic-cdk
 authors.workspace = true
 edition.workspace = true
 license.workspace = true

ic-cdk-timers/CHANGELOG.md

@@ -6,12 +6,13 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [unreleased]
 
-- Breaking: Interval timer bodies have been changed from `AsyncFnMut()` to `FnMut() -> impl Future`; some code may need to be changed from `async || {` to `|| async {`.
-
-## [1.0.0-beta.1] - 2025-10-09
+## [1.0.0] - 2025-11-13
 
 - `ic-cdk-timers` no longer has a dependency on `ic-cdk` and no longer needs to be upgraded when `ic-cdk` is upgraded.
-- Breaking: Timer bodies have been changed from `FnOnce`/`FnMut` to `Future`/`AsyncFnMut`, so `spawn` is no longer required to enter an async context from a timer. For `set_timer`, `|| {}` should be changed to `async {}`, and for `set_timer_interval`, `|| {}` should be changed to `async || {}`.
+- Breaking: Timer body function signatures have been updated which eliminating the need for explicit `spawn` calls within timer callbacks. 
+  - `set_timer`: now takes `impl Future<Output = ()>`. `|| {}` should be changed to `async {}`,
+  - `set_timer_interval`: now takes `FnMut() -> impl Future`. `|| {}` should be changed to `|| async {}`.
+  - `set_timer_interval_serial`: new function, takes `AsyncFnMut()`.
   - If you have any immediate `spawn` calls, you can remove them and run the async code directly. (You do not have to.)
 
 ## [0.12.2] - 2025-06-25

ic-cdk-timers/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "ic-cdk-timers"
-version = "1.0.0-beta.1"
+version = "1.0.0"
 authors.workspace = true
 edition.workspace = true
 license.workspace = true
@@ -12,7 +12,10 @@ documentation = "https://docs.rs/ic-cdk-timers"
 readme = "README.md"
 categories = ["api-bindings", "data-structures", "no-std", "development-tools::ffi"]
 keywords = ["internet-computer", "dfinity", "canister", "cdk"]
-include = ["src", "Cargo.toml", "LICENSE", "README.md"]
+include = ["src", "Cargo.toml", "LICENSE", "README.md", "build.rs"]
+# DO NOT change this field, not even to update the link, unless you are updating every existing version of the package.
+# Update the link by updating the links-pin tag.
+links = "ic-cdk-timers (canister_global_timer), see https://github.com/dfinity/cdk-rs/blob/links-pin/TROUBLESHOOTING.md"
 
 [dependencies]
 ic0.workspace = true

ic-cdk-timers/README.md

@@ -16,7 +16,7 @@ In `Cargo.toml`:
 
 ```toml
 [dependencies]
-ic-cdk-timers = "0.9.0"
+ic-cdk-timers = "1.0.0"
 ```
 
 To schedule a one-shot task to be executed 1s later:

ic-cdk-timers/build.rs

@@ -0,0 +1,3 @@
+fn main() {
+    // dummy build script, required by `package.links`
+}

ic-cdk/CHANGELOG.md

@@ -6,7 +6,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [unreleased]
 
-## [0.19.0-beta.3] - 2025-10-09
+## [0.19.0] - 2025-11-13
 
 ### Added