publish-release

name	publish-release
description	Orchestrate ShareX.ImageEditor release flow in strict order: run-maintenance first, update-changelog second (optional if no CHANGELOG), verify build, bump/commit/push/tag, monitor GitHub Actions every 2 minutes, ensure standard release notes, then set pre-release by default (use explicit opt-out for stable). On failures, inspect logs, fix root cause, and retry with the next patch release.

ShareX.ImageEditor Release Bump Tag

Overview

Use this skill to run release steps in strict order:

• Step 1: Execute maintenance chores first (git pull --recurse-submodules and git submodule update --init --recursive)
• Step 2: Run .ai/skills/update-changelog/SKILL.md second (optional if no CHANGELOG.md exists)
• Step 3: Verify build, then execute bump/commit/push/tag automation
• Step 4: Monitor the tag-triggered release workflow every 2 minutes
• Step 5: If failure occurs, inspect logs, fix issues, and retry with the next patch version
• Step 6: Ensure standard release notes block is present on the GitHub release
• Step 7: Set the successful release as pre-release by default (opt out only when intentionally publishing stable)

Step 3 performs:

• Pre-check: Run dotnet build ShareX.ImageEditor.sln; do not proceed if build fails.
• Prompts for x/y/z bump type (major/minor/patch) unless specified.
• Updates every tracked Directory.Build.props file that defines <Version>.
• Stages all current repo changes.
• Commits with version-prefixed message.
• Pushes current branch and creates/pushes annotated tag vX.Y.Z.

Step 4-5 performs:

• Find tag run for Release Build.