Changelogs for NNS backend 2026-08-21

[daniel-wong-dfinity-org-twin]

Proposals:

• SNS-WASM: 143658
• Registry: 143659
• Governance 143660

[github-actions]

This pull request changes code owned by the Governance team. Therefore, make sure that
you have considered the following (for Governance-owned code):

1. Update unreleased_changelog.md (if there are behavior changes, even if they are
   non-breaking).

2. Are there BREAKING changes?

3. Is a data migration needed?

4. Security review?

How to Satisfy This Automatic Review

1. Go to the bottom of the pull request page.

2. Look for where it says this bot is requesting changes.

3. Click the three dots to the right.

4. Select "Dismiss review".

5. In the text entry box, respond to each of the numbered items in the previous
   section, declare one of the following:

• Done.

• $REASON_WHY_NO_NEED. E.g. for unreleased_changelog.md, "No
  canister behavior changes.", or for item 2, "Existing APIs
  behave as before.".

Brief Guide to "Externally Visible" Changes

"Externally visible behavior change" is very often due to some NEW canister API.

Changes to EXISTING APIs are more likely to be "breaking".

If these changes are breaking, make sure that clients know how to migrate, how to
maintain their continuity of operations.

If your changes are behind a feature flag, then, do NOT add entrie(s) to
unreleased_changelog.md in this PR! But rather, add entrie(s) later, in the PR
that enables these changes in production.

Reference(s)

For a more comprehensive checklist, see here.

GOVERNANCE_CHECKLIST_REMINDER_DEDUP

[zeropath-ai]

✅ No security or compliance issues detected. Reviewed everything up to a383926.

Security Overview

• 🔎 Scanned files: 5 changed file(s)
• 🔗 Scan Link: https://zeropath.com/app/repositories/f975f1a5-0a47-4a3b-b7f0-a55609e90390?scanId=f1f5a4ad-67bb-43da-9ca7-e9b814c6411d&codeScanTypes=PrScan&tab=issues

Detected Code Changes

Change Type	Relevant files
Addition/Release Notes	► rs/nns/governance/CHANGELOG.md       Add 2026-08-21: Proposal 143660 and 2026-08-14: Proposal 143577 details ► rs/nns/sns-wasm/CHANGELOG.md       Add 2026-08-21: Proposal 143658 details and 2026-08-14: Proposal 143578 details
Addition/Release Notes	► rs/nns/sns-wasm/unreleased_changelog.md       Remove legacy entry under Fixed (as part of unreleased changes)
Addition/Release Notes	► rs/registry/canister/CHANGELOG.md       Add 2026-08-21: Proposal 143659 details and 2026-08-14: Proposal 143579 details
Addition/Release Notes	► rs/registry/canister/unreleased_changelog.md       Remove legacy Fixed/Added entries under unreleased changelog

[claude]

Review: minor nit — non-blocking

This is a straightforward changelog-publishing PR: it moves three already-written entries (from rs/nns/governance/unreleased_changelog.md, rs/nns/sns-wasm/unreleased_changelog.md, and rs/registry/canister/unreleased_changelog.md) into dated sections of their respective CHANGELOG.md files under proposals 143658/143659/143660. I checked each entry against the actual code it describes (insert_sns_specific_upgrade_path_entry in rs/nns/sns-wasm/src/sns_wasm.rs, the SEV/guest_launch_measurements invariant, deploy_guestos_to_all_subnet_nodes's new blank-replica_version_id handling in do_deploy_guestos_to_all_subnet_nodes.rs, and the relaxed UpdateStandardEngineReplicaVersion validation) and each description matches the code. The unreleased_changelog.md removals are clean — section headers are preserved and only the moved text is deleted.

One small inconsistency: the new governance entry links https://dashboard.internetcomputer.org/proposal/143660, while every other entry in that file (including the one right below it) and in the sns-wasm/registry CHANGELOG.md files uses http://. Both schemes resolve fine, so this isn't a bug, just worth aligning for consistency in a future edit.

No correctness bugs found, and there's no code here to simplify (pure Markdown changes).

Verdict: approve, with the above as a minor non-blocking suggestion.

---

Generated by Claude Code