# Release Notes

> Create release notes for a new netlab release

- Skill: `ipspace/release-notes` (Agent Skill)
- Install (CLI): `npx skillmds@latest add ipspace/release-notes`
- Raw SKILL.md: https://api.skillmd.com/api/skills/ipspace/release-notes/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: ipspace (https://skillmd.com/u/ipspace)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/ipspace/release-notes

---

# Creating release notes

* Use docs/release/release.template as a template
* Use other files in the docs/release folder as guidance
* Create release notes from commits after the last `release_xx.xx` tag
* Categorize commits without the explicit category (usually 'Doc' or 'Fix') in the title into one of the categories based on their content and impact.
* Try to identify breaking changes.
* Remove PR references from all sections except bug and documentation fixes (older release notes/templates may still show the previous style; follow this rule going forward).
* Remove the "Doc: " or "Fix: " part of the commit title

# IMPORTANT

* DO NOT make up cross-reference anchors. Use only anchors already defined in the documentation files. Tell the user if you think something is crucial enough to warrant a new anchor.
* DO NOT modify files outside the ‘docs’ directory. For example, DO NOT change the `netsim/__init__.py` file.

