fix: simplify release workflow to avoid multi-line output issues

[tarrencev]

No description provided.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
controller-example-next	🔄 Building (Inspect)	Visit Preview	Jun 24, 2025 3:57pm
keychain	🔄 Building (Inspect)	Visit Preview	Jun 24, 2025 3:57pm
keychain-storybook	🔄 Building (Inspect)	Visit Preview	Jun 24, 2025 3:57pm
profile	✅ Ready (Inspect)	Visit Preview	Jun 24, 2025 3:57pm

[claude]

Claude finished @tarrencev's task —— View job

---

PR Review: Release Workflow Simplification ✅

Completed comprehensive review of the release workflow changes.

Todo List:

• Check for existing reviews on this PR
• Check existing comments to avoid redundancy
• Start a fresh pending review
• Get diff information to understand changes
• Analyze workflow changes for potential issues
• Add inline comments for any identified issues
• Submit review as "COMMENT" type
• Provide final summary

Review Summary:

This PR addresses a real GitHub Actions limitation with multi-line output variables by switching to a file-based approach. The implementation is solid and follows best practices:

✅ Proper fix: Uses --notes-file instead of problematic heredoc output variables
✅ Good error handling: Maintains fallback logic for missing changelog scenarios
✅ Clean implementation: File-based approach is more reliable and secure
✅ Helpful debugging: Adds content size output for troubleshooting

Result: No issues identified - this is a well-implemented fix that should resolve the multi-line output problems mentioned in the PR title.

[claude]

This is a solid fix for multi-line output issues in GitHub Actions workflows. The approach of using file-based changelog handling instead of heredoc output variables is the recommended pattern and addresses real limitations with GitHub Actions output variable handling.

Key improvements:

• Replaces problematic heredoc output variables with file-based approach
• Uses --notes-file instead of --notes for reliable multi-line content handling
• Maintains proper fallback logic for missing changelog scenarios
• Adds helpful debugging output

The implementation is clean and follows GitHub Actions best practices. No issues identified.