Merge branch 'master' into mraszyk/reject-message-implementation-spec…

…ific

spec/_attachments/interface-spec-changelog.md

@@ -1,6 +1,11 @@
 ## Changelog {#changelog}
 
 ### ∞ (unreleased)
+* The maximum length of a nonce in an ingress message is 32 bytes.
+* Update specification of responses from the endpoint `/api/v2/status`.
+* Stop canister calls might be rejected upon timeout.
+
+### 0.22.0 (2023-11-15) {#0_22_0}
 * Add metrics on subnet usage into the certified state tree and a new HTTP endpoint `/api/v2/subnet/<subnet_id>/read_state` for retrieving them.
 * Add management canister methods to support installing large WebAssembly modules split into chunks.
 * Add a system API method to determine if the canister is running in replicated or non-replicated mode.
@@ -10,9 +15,6 @@
 * Add per-call context performance counter.
 * Update the computation of the representation-independent hash for the case of maps with nested maps.
 * Remove `senders` field from user delegations.
-* The maximum length of a nonce in an ingress message is 32 bytes.
-* Update specification of responses from the endpoint `/api/v2/status`.
-* Stop canister calls might be rejected upon timeout.
 
 ### 0.21.0 (2023-09-18) {#0_21_0}
 * Canister cycle balance cannot decrease below the freezing limit after executing `install_code` on the management canister.

spec/index.md

@@ -1024,8 +1024,6 @@ Additionally, the Internet Computer provides an API endpoint to obtain various s
 
 For this endpoint, the user performs a GET request, and receives a CBOR (see [CBOR](#cbor)) value with the following fields. The IC may include additional implementation-specific fields.
 
--   `impl_version` (string, optional): The precise git revision of the Internet Computer Protocol implementation
-
 -   `root_key` (blob, optional): The public key (a DER-encoded BLS key) of the root key of this instance of the Internet Computer Protocol. This *must* be present in short-lived development instances, to allow the agent to fetch the public key. For the Internet Computer, agents must have an independent trustworthy source for this data, and must not be tempted to fetch it from this insecure location.
 
 See [CBOR encoding of requests and responses](#api-cbor) for details on the precise CBOR encoding of this object.