docs(governance): Added 2025-01-20 CHANGELOG.md entries.

rs/registry/unreleased_changelog.md → rs/registry/canister/CHANGELOG.md

@@ -1,13 +1,19 @@
-# How This File Is Used
+# Changelog
 
-In general, upcoming/unreleased behavior changes are described here. For details
-on the process that this file is part of, see
-`rs/nervous_system/changelog_process.md`.
+Proposals before 2025 are NOT listed in here, because this process was
+introduced later. (We could back fill those later though.)
 
+The process that populates this file is described in
+`rs/nervous_system/changelog_process.md`. In general though, the entries you see
+here were moved from the adjacent `unreleased_changelog.md` file.
 
-# Next Upgrade Proposal
 
-## Added
+INSERT NEW RELEASES HERE
+
+
+# 2025-01-20: Proposal 134904
+
+http://dashboard.internetcomputer.org/proposals/134904
 
 ## Changed
 
@@ -24,10 +30,5 @@ Such behavior is conservative and not strictly necessary since the subnet
 decentralization is not affected when the new node has all properties
 identical as the old node, which is the case if the IPv6 address is unchanged.
 
-## Deprecated
-
-## Removed
-
-## Fixed
 
-## Security
+END

rs/registry/canister/unreleased_changelog.md

@@ -0,0 +1,20 @@
+# How This File Is Used
+
+In general, upcoming/unreleased behavior changes are described here. For details
+on the process that this file is part of, see
+`rs/nervous_system/changelog_process.md`.
+
+
+# Next Upgrade Proposal
+
+## Added
+
+## Changed
+
+## Deprecated
+
+## Removed
+
+## Fixed
+
+## Security

rs/sns/governance/CHANGELOG.md

@@ -11,4 +11,19 @@ here were moved from the adjacent `unreleased_changelog.md` file.
 INSERT NEW RELEASES HERE
 
 
+# 2025-01-20: Proposal 134906
+
+http://dashboard.internetcomputer.org/proposals/134906
+
+## Added
+
+Enable upgrading SNS-controlled canisters using chunked WASMs. This is implemented as an extension
+of the existing `UpgradeSnsControllerCanister` proposal type with new field `chunked_canister_wasm`.
+This field can be used for specifying an upgrade of an SNS-controlled *target* canister using
+a potentially large WASM module (over 2 MiB) uploaded to some *store* canister, which:
+* must be installed on the same subnet as target.
+* must have SNS Root as one of its controllers.
+* must have enough cycles for performing the upgrade.
+
+
 END

rs/sns/governance/unreleased_changelog.md

@@ -9,14 +9,6 @@ on the process that this file is part of, see
 
 ## Added
 
-Enable upgrading SNS-controlled canisters using chunked WASMs. This is implemented as an extension
-of the existing `UpgradeSnsControllerCanister` proposal type with new field `chunked_canister_wasm`.
-This field can be used for specifying an upgrade of an SNS-controlled *target* canister using
-a potentially large WASM module (over 2 MiB) uploaded to some *store* canister, which:
-* must be installed on the same subnet as target.
-* must have SNS Root as one of its controllers.
-* must have enough cycles for performing the upgrade.
-
 ## Changed
 
 ## Deprecated

rs/sns/root/CHANGELOG.md

@@ -11,4 +11,21 @@ here were moved from the adjacent `unreleased_changelog.md` file.
 INSERT NEW RELEASES HERE
 
 
+# 2025-01-20: Proposal 134905
+
+http://dashboard.internetcomputer.org/proposals/134905
+
+## Added
+
+Enable upgrading SNS-controlled canisters using chunked WASMs. This is implemented as an extension
+of the existing `UpgradeSnsControllerCanister` proposal type with new field `chunked_canister_wasm`.
+This field can be used for specifying an upgrade of an SNS-controlled *target* canister using
+a potentially large WASM module (over 2 MiB) uploaded to some *store* canister, which:
+* must be installed on the same subnet as target.
+* must have SNS Root as one of its controllers.
+* must have enough cycles for performing the upgrade.
+
+You can now set wasm_memory_threshold via proposal.
+
+
 END

rs/sns/swap/CHANGELOG.md

@@ -11,4 +11,11 @@ here were moved from the adjacent `unreleased_changelog.md` file.
 INSERT NEW RELEASES HERE
 
 
+# 2025-01-20: Proposal 134907
+
+http://dashboard.internetcomputer.org/proposals/134907
+
+You can now set wasm_memory_threshold via proposal.
+
+
 END