chore: Release workflow

[Alon Yeshurun (ayeshurun)]

📥 Pull Request

✨ Description of new changes

Summary

Enhances the create-release.yml workflow with optional commit targeting, rich error messages via GITHUB_STEP_SUMMARY, and upfront workflow information display. Uses heredoc syntax for cleaner, more maintainable code.

Changes

Optional Commit Targeting

• New input parameter: commit_sha (optional) - allows tagging specific commits instead of always using HEAD
• Validation: Verifies commit exists in repository using git rev-parse --verify
• Backward compatible: Defaults to HEAD when not provided

Rich Error Messages

All error scenarios now write formatted messages to GITHUB_STEP_SUMMARY using heredoc syntax:

• Invalid commit SHA: Shows troubleshooting steps and verification methods
• Missing release notes: Displays expected path, lists available changelog files, suggests changie batch command
• Release creation failure: Lists common issues (existing tag, permissions, network) with actionable next steps

Workflow Transparency

• Information display: Shows version and target commit at workflow start
• Success feedback: Displays tag, commit SHA, and direct link to created release
• Variable logging: Outputs all resolved variables for traceability

Technical Updates

• Checkout with fetch-depth: 0 for full git history access
• Target commit passed to gh release create --target flag
• Enhanced variable resolution (both target and actual SHA)
• Heredoc syntax: Refactored all GITHUB_STEP_SUMMARY writes to use cat >> $GITHUB_STEP_SUMMARY << EOF instead of multiple echo commands for cleaner, more maintainable code

Example Usage

# Default behavior (unchanged)
version: v1.3.0
commit_sha: # empty - tags HEAD

# New capability
version: v1.3.0
commit_sha: abc123def  # tags specific commit

Workflow Step Summary Examples

✅ Successful Release

# 🚀 Create Release Workflow

## ℹ️ Workflow Information
- **Version:** v1.3.0
- **Target Commit:** Latest commit on current branch (HEAD)

## 🏗️ Creating Release
Creating release with the following details:
- **Tag:** `v1.3.0`
- **Target Commit:** `7c573b0a1b2c3d4e5f6789abcdef0123456789ab`
- **Notes File:** `.changes/v1.3.0.md`

## ✅ Release Created Successfully!
🎉 **Release `v1.3.0` has been created!**

### 📋 Release Details:
- **Tag:** `v1.3.0`
- **Commit:** `7c573b0a1b2c3d4e5f6789abcdef0123456789ab`
- **Release URL:** [View Release](https://github.com/ayeshurun/fabric-cli/releases/tag/v1.3.0)

❌ Error: Invalid Commit SHA

## ❌ Error: Invalid Commit SHA

The provided commit SHA `invalidsha123` is not valid or does not exist in this repository.

### 📝 Troubleshooting
- Verify the commit SHA exists in the repository
- Ensure you are using the full commit SHA (or at least 7 characters)
- Check that the commit is in the current branch history

❌ Error: Missing Release Notes

## ❌ Error: Release Notes File Not Found

The release notes file was not found at the expected location:
.changes/v2.0.0.md

### 📝 What to do:
1. Ensure you have created the changelog file for version `v2.0.0`
2. The file should be located at: `.changes/v2.0.0.md`
3. You can use `changie batch <version>` to generate the changelog file

### 📂 Available changelog files:
header.tpl.md, v0.1.10.md, v1.0.0.md, v1.2.0.md

All messages appear in the Summary section at the top of the workflow run page, providing immediate visibility without needing to dig through step logs.

Context

Addresses user request for better error visibility and control over which commit gets tagged during release creation. Implementation uses modern shell heredoc syntax for improved code readability and maintainability.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[FEATURE] Enhance Create release workflow</issue_title>
<issue_description>### Use Case / Problem

i want to enhance the create-release.yml workflow, so the error message will be clear using the GITHUB_STEP_SUMMARY. in addition add some info to the user triggers it before he triggers, that it will create a tag on the latest commit, no control. add input parameter as optional so user can add the commit hash id and the tag will be created in this commit.

Proposed Solution

i want to enhance the create-release.yml workflow, so the error message will be clear using the GITHUB_STEP_SUMMARY. in addition add some info to the user triggers it before he triggers, that it will create a tag on the latest commit, no control. add input parameter as optional so user can add the commit hash id and the tag will be created in this commit.

Alternatives Considered

No response

Impact Assessment

• This would help me personally
• This would help my team/organization
• This would help the broader fabric-cli community
• This aligns with Microsoft Fabric roadmap items

Implementation Attestation

• I understand this feature should maintain backward compatibility with existing commands
• I confirm this feature request does not introduce performance regressions for existing workflows
• I acknowledge that new features must follow fabric-cli's established patterns and conventions

Implementation Notes

No response</issue_description>

Comments on the Issue (you are Copilot in this section)