The alpha and beta stage 2 workflows were failing with git history errors when trying to detect file changes. The workflows attempted to run git diff --name-only HEAD^ HEAD but failed because GitHub Actions uses a shallow clone by default (fetch-depth: 1), making the parent commit unavailable.

Error Details

Both workflows failed with:

fatal: ambiguous argument 'HEAD^': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'

Changes Made

1. Fixed GitHub Actions Workflows

• Added fetch-depth: 2 to checkout actions in both alpha and beta stage 2 workflows
• This ensures HEAD^ is available for the git diff --name-only HEAD^ HEAD command

2. Enhanced Alpha Support in build.sh

The build.sh script already supported alpha builds for package generation, but the changelog generation logic was incomplete:

• Added alpha tag filtering logic to changelog generation
• Updated stable tag filtering to exclude both beta and alpha tags
• Now properly separates alpha, beta, and stable release streams

3. Updated Test Script

• Enhanced test/test-changelog.sh to support alpha release type testing
• Updated documentation and examples to include alpha testing scenarios
• Added alpha tag listing in the available tags output

Testing

All changes have been tested locally:

• ✅ Git diff commands work with sufficient history
• ✅ Alpha changelog generation functions correctly
• ✅ Beta and stable changelog generation remain unchanged
• ✅ Workflow change detection logic works properly
• ✅ All release types (alpha, beta, stable) fully supported

The fix ensures that both alpha and beta workflows can properly detect file changes and generate appropriate changelogs while maintaining backward compatibility with existing stable and beta functionality.

Fixes #175.

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.