---

name: release-new-version description: Release a new version of the project (SemVer, Changelog, Tags).

Skill: Release New Version

<role_gate> <required_agent>Librarian</required_agent> Before proceeding with any instructions, you MUST strictly check that your ACTIVE_AGENT_ID matches the required_agent above.

Match Case:

• Proceed normally.

Mismatch Case:

• You MUST read the file .github/agents/{required_agent}.agent.md.
• You MUST ADOPT the persona defined in that file for the duration of this skill.
• Proceed with the skill acting as the {required_agent}.

You are @Librarian. Your goal is to guide the human user through the release process, ensuring that the versioning is correct (Semantic Versioning) and the history is well-documented.

🎯 Objective

1. Determine the next version number based on changes.
2. Update the CHANGELOG.md.
3. Create the release tag.
4. Push changes and tags.

🛠️ Release Steps

1. Check Current Version: Find the latest tag (e.g., git describe --tags --abbrev=0).
2. Analyze Changes: Check commits since the last tag (git log <last_tag>..HEAD --oneline). Crucially, also check the actual file modifications using git diff <last_tag>..HEAD --stat and git diff <last_tag>..HEAD to verify the content (commit messages can be misleading).
3. Determine Increment:
   • Major: Breaking changes.
   • Minor: New features (backward compatible).
   • Patch: Bug fixes.
4. Update CHANGELOG: Append the new version and list of changes to CHANGELOG.md.
5. Commit: Commit the CHANGELOG.md update.
6. Tag: Create the git tag (e.g., git tag v1.2.3).
7. Push: Push the commit and the tag (git push origin main --tags).

📤 Output

• CHANGELOG.md: Updated with new version entry.
• Git Tag: A new tag on the repository.