chore(nervous-system): Update changelog for release 2025-02-07 (#3867)

Update CHANGELOG.md for today's release. ## NNS - [135205](https://dashboard.internetcomputer.org/proposal/135205) - [135206](https://dashboard.internetcomputer.org/proposal/135206) - [135207](https://dashboard.internetcomputer.org/proposal/135207) ## SNS - [135208](https://dashboard.internetcomputer.org/proposal/135208) - [135209](https://dashboard.internetcomputer.org/proposal/135209)
dfinity · Feb 7, 2025 · 4c20acb · 4c20acb
1 parent 2d4bcba
commit 4c20acb
Show file tree

Hide file tree

Showing 11 changed files with 103 additions and 58 deletions.
diff --git a/rs/nns/cmc/CHANGELOG.md b/rs/nns/cmc/CHANGELOG.md
@@ -11,4 +11,17 @@ here were moved from the adjacent `unreleased_changelog.md` file.
 INSERT NEW RELEASES HERE
 
 
+# 2025-02-07: Proposal 135205
+
+http://dashboard.internetcomputer.org/proposals/135205
+
+## Added
+
+* Automatically refund when the memo in an incoming ICP transfer is not one of
+  the special values that indicate the purpose of the transfer (e.g. to create a
+  new canister). This was originally proposed without objection in [the forum].
+
+[the forum]: https://forum.dfinity.org/t/extend-cycles-minting-canister-functionality/37749/2
+
+
 END
diff --git a/rs/nns/cmc/unreleased_changelog.md b/rs/nns/cmc/unreleased_changelog.md
@@ -9,12 +9,6 @@ on the process that this file is part of, see
 
 ## Added
 
-* Automatically refund when the memo in an incoming ICP transfer is not one of
-  the special values that indicate the purpose of the transfer (e.g. to create a
-  new canister). This was originally proposed without objection in [the forum].
-
-[the forum]: https://forum.dfinity.org/t/extend-cycles-minting-canister-functionality/37749/2
-
 ## Changed
 
 ## Deprecated

diff --git a/rs/nns/governance/CHANGELOG.md b/rs/nns/governance/CHANGELOG.md
@@ -98,3 +98,36 @@ the neuron. More precisely,
 
 
 END
+
+
+INSERT NEW RELEASES HERE
+
+
+# 2025-02-07: Proposal 135206
+
+http://dashboard.internetcomputer.org/proposals/135206
+
+## Added
+
+### List Neurons API Change: Query by Subaccount
+
+The `list_neurons` API now supports querying by neuron subaccount.  This is useful for neuron holders who
+have many neurons and want to list only the neurons associated with a particular subaccount.
+
+A new field `neuron_subaccounts` is added to the request, which is a list of subaccounts to query
+for.  If this field is present, any neurons found will be added to the response.  If duplicate
+neurons are found between this field and others, they will be deduplicated before returning the value.
+
+This new field works in the same way that the existing `neuron_ids` field works.
+
+### Migrating Active Neurons to Stable Memory
+
+In this release, we turn on the feature to migrate active neurons to stable memory:
+`migrate_active_neurons_to_stable_memory`. After the feature is turned on, a timer task will
+gradually move active neurons from the heap to stable memory. Clients should not expect any
+functional behavior changes, since no APIs rely on where the neurons are stored.
+
+## Changed
+
+* The limit of the number of neurons is increased from 380K to 400K.
+
diff --git a/rs/nns/governance/unreleased_changelog.md b/rs/nns/governance/unreleased_changelog.md
@@ -9,28 +9,8 @@ on the process that this file is part of, see
 
 ## Added
 
-### List Neurons API Change: Query by Subaccount
-
-The `list_neurons` API now supports querying by neuron subaccount.  This is useful for neuron holders who
-have many neurons and want to list only the neurons associated with a particular subaccount.
-
-A new field `neuron_subaccounts` is added to the request, which is a list of subaccounts to query
-for.  If this field is present, any neurons found will be added to the response.  If duplicate
-neurons are found between this field and others, they will be deduplicated before returning the value.
-
-This new field works in the same way that the existing `neuron_ids` field works.
-
-### Migrating Active Neurons to Stable Memory
-
-In this release, we turn on the feature to migrate active neurons to stable memory:
-`migrate_active_neurons_to_stable_memory`. After the feature is turned on, a timer task will
-gradually move active neurons from the heap to stable memory. Clients should not expect any
-functional behavior changes, since no APIs rely on where the neurons are stored.
-
 ## Changed
 
-* The limit of the number of neurons is increased from 380K to 400K.
-
 ## Deprecated
 
 ## Removed

diff --git a/rs/registry/canister/CHANGELOG.md b/rs/registry/canister/CHANGELOG.md
@@ -11,6 +11,42 @@ here were moved from the adjacent `unreleased_changelog.md` file.
 INSERT NEW RELEASES HERE
 
 
+# 2025-02-07: Proposal 135207
+
+http://dashboard.internetcomputer.org/proposals/135207
+
+## Changed
+
+### Migrate Registry to use ic_stable_structures' MemoryManager
+
+This update migrates registry from using dfn_core to using virtual memory regions provided by ic_stable_structures
+MemoryManager.  This allows in the future to migrate the Registry records into stable memory.
+
+### Automatically replace the nodes when an active API boundary node is replaced
+
+`add_node` will now also automatically replace a node if it is being redeployed and has
+been active as an API boundary node before. It will fail if the redeployed node does not
+meet the requirements for an API boundary node (i.e., is configured with a domain name).
+
+## Deprecated
+
+The legacy ECDSA-specific fields are no longer supported in Registry canister's subnet operations
+(creation, updating, recovery). Please use the more expressive chain key configuration keys:
+
+* `ecdsa_config` → `chain_key_config`
+* `ecdsa_key_signing_enable` → `chain_key_signing_enable`
+* `ecdsa_key_signing_disable` → `chain_key_signing_disable`
+
+## Fixed
+
+### Backfill node_reward_type for existing nodes
+
+A one-time migration to fill in the `node_reward_type` field for existing nodes was added.  Previously, there was no
+on-chain connection between the specific nodes and their reward types.  This data came from off-chain sources
+at DFINITY.  In the future, the `node_reward_type` will be used to determine the reward type for each node, and
+it will be a required field for node registration in the IC.
+
+
 # 2025-01-20: Proposal 134904
 
 http://dashboard.internetcomputer.org/proposals/134904

diff --git a/rs/registry/canister/unreleased_changelog.md b/rs/registry/canister/unreleased_changelog.md
@@ -11,35 +11,10 @@ on the process that this file is part of, see
 
 ## Changed
 
-### Migrate Registry to use ic_stable_structures' MemoryManager
-
-This update migrates registry from using dfn_core to using virtual memory regions provided by ic_stable_structures
-MemoryManager.  This allows in the future to migrate the Registry records into stable memory.
-
-### Automatically replace the nodes when an active API boundary node is replaced
-
-`add_node` will now also automatically replace a node if it is being redeployed and has
-been active as an API boundary node before. It will fail if the redeployed node does not
-meet the requirements for an API boundary node (i.e., is configured with a domain name).
-
 ## Deprecated
 
-The legacy ECDSA-specific fields are no longer supported in Registry canister's subnet operations
-(creation, updating, recovery). Please use the more expressive chain key configuration keys:
-
-* `ecdsa_config` → `chain_key_config`
-* `ecdsa_key_signing_enable` → `chain_key_signing_enable`
-* `ecdsa_key_signing_disable` → `chain_key_signing_disable`
-
 ## Removed
 
 ## Fixed
 
-### Backfill node_reward_type for existing nodes
-
-A one-time migration to fill in the `node_reward_type` field for existing nodes was added.  Previously, there was no
-on-chain connection between the specific nodes and their reward types.  This data came from off-chain sources
-at DFINITY.  In the future, the `node_reward_type` will be used to determine the reward type for each node, and
-it will be a required field for node registration in the IC.
-
 ## Security
diff --git a/rs/sns/governance/CHANGELOG.md b/rs/sns/governance/CHANGELOG.md
@@ -11,6 +11,17 @@ here were moved from the adjacent `unreleased_changelog.md` file.
 INSERT NEW RELEASES HERE
 
 
+# 2025-02-07: Proposal 135208
+
+http://dashboard.internetcomputer.org/proposals/135208
+
+## Added
+
+* Added the `query_stats` field for `canister_status`/`get_sns_canisters_summary` methods.
+* Fix a bug due to which SNS ledger logos were sometimes unset after changing unrelated
+  SNS ledger metadata fields.
+
+
 # 2025-02-03: Proposal 135067
 
 http://dashboard.internetcomputer.org/proposal/135067

diff --git a/rs/sns/governance/unreleased_changelog.md b/rs/sns/governance/unreleased_changelog.md
@@ -9,10 +9,6 @@ on the process that this file is part of, see
 
 ## Added
 
-* Added the `query_stats` field for `canister_status`/`get_sns_canisters_summary` methods.
-* Fix a bug due to which SNS ledger logos were sometimes unset after changing unrelated
-  SNS ledger metadata fields.
-
 ## Changed
 
 ## Deprecated

diff --git a/rs/sns/root/CHANGELOG.md b/rs/sns/root/CHANGELOG.md
@@ -11,6 +11,15 @@ here were moved from the adjacent `unreleased_changelog.md` file.
 INSERT NEW RELEASES HERE
 
 
+# 2025-02-07: Proposal 135209
+
+http://dashboard.internetcomputer.org/proposals/135209
+
+## Added
+
+* Added the `query_stats` field for `canister_status`/`get_sns_canisters_summary` methods.
+
+
 # 2025-02-03: Proposal 135066
 
 http://dashboard.internetcomputer.org/proposal/135066

diff --git a/rs/sns/root/unreleased_changelog.md b/rs/sns/root/unreleased_changelog.md
@@ -9,8 +9,6 @@ on the process that this file is part of, see
 
 ## Added
 
-* Added the `query_stats` field for `canister_status`/`get_sns_canisters_summary` methods.
-
 ## Changed
 
 ## Deprecated

diff --git a/testnet/tools/nns-tools/add-release-to-changelog.sh b/testnet/tools/nns-tools/add-release-to-changelog.sh
@@ -45,7 +45,7 @@ fi
 PROPOSAL_INFO=$(echo "${PROPOSAL_INFO}" | jq '.[0]')
 
 # Get proposal creation timestam.
-PROPOSED_TIMESTAMP_SECONDS=$(echo "${PROPOSAL_INFO}" | jq '.proposal_creation_timestamp_seconds | tonumber')
+PROPOSED_TIMESTAMP_SECONDS=$(echo "${PROPOSAL_INFO}" | jq '.proposal_creation_timestamp_seconds // .proposal_timestamp_seconds | tonumber')
 if [[ "${PROPOSED_TIMESTAMP_SECONDS}" -eq 0 ]]; then
     print_red "💀 Proposal ${PROPOSAL_ID} exists, but had no proposal_creation_timestamp_seconds." >&2
     exit 1