Overview

Archived changes for previous node releases using new WIP Season version

The archived changes show more than they should because those Git tags include too many change files

Suggest we leave them as-is, and manage archiving change files better going forward.

Plan: To add a manual dispatch Archive Changes workflow

• Select a tag, and whether you want to move, copy, or delete the change files for that release
• This will create a new PR against the origin branch with the change-file changes

🗹 TODO before merging

• Ready

📌 Submission Checklist

• Changes are backward-compatible (or flagged if breaking)
• Pull request description explains why the change is needed
• Self-reviewed the diff
• I have included a change file, or skipped for this reason:
• If the changes introduce a new feature, I have bumped the node minor version
• Update documentation (if relevant)
• Updated AGENTS.md if build commands, architecture, or workflows changed
• No new todos introduced

🧪 Testing Evidence

Please describe any additional testing aside from CI:

• Additional tests are provided (if possible)

🔱 Fork Strategy

• Node Runtime Update
• Node Client Update
• Other:
• N/A

Links