fix: update weekly release workflow to detect squash-merged PRs

[brunopgalvao]

Summary

Fixes the weekly release workflow to properly detect squash-merged PRs and implements alpha semantic versioning rules.

Problem

The current workflow only detects merge commits (git log --merges), which means squash-merged PRs are not detected. This caused PR #44's breaking changes to be invisible to the release workflow.

Solution

Changes to Detection Logic

• ✅ Replace --merges flag with detection of all commits
• ✅ Look for PR references in squash commits (#123 pattern)
• ✅ Detect conventional commit types (feat:, fix:, refactor:, etc.)
• ✅ Look for "breaking change" keywords in commit bodies

Alpha Versioning Rules (v0.x.x)

• ✅ Major bumps become minor bumps while in alpha (v0.x.x)
• ✅ Breaking changes: v0.1.0 → v0.2.0
• ✅ Features/refactors: trigger minor bumps
• ✅ Fixes/chores: trigger patch bumps

Release Notes

• ✅ Show all commits with PR references, not just merge commits

Testing

Tested with current commits since v0.1.0:

$ git log v0.1.0..HEAD --pretty=format:"%s" 
refactor: restructure CLI command hierarchy and remove slug parameter (#44)
Rename macOS binaries for clarity (#43)

Detection result:

• Found "Breaking changes:" in PR refactor: restructure CLI command hierarchy and remove slug parameter #44 commit body
• Would trigger MINOR bump (v0.1.0 → v0.2.0) ✅
• Respects alpha versioning (major → minor) ✅

Impact

After merging this PR:

• Next Wednesday's weekly release will correctly detect the breaking changes from PR refactor: restructure CLI command hierarchy and remove slug parameter #44
• Release v0.2.0 will be created automatically
• Works with any merge strategy (squash, merge commit, or rebase)

Next Steps

Once merged, the weekly release workflow will properly detect changes regardless of merge strategy.

[github-actions]

🤖 Semantic Version Analysis

Result: PATCH version bump

Commit Analysis

Commit	Type	Impact	Message
8fabad1	fix	🟢 PATCH	fix(workflows): update weekly release to detect squash-merge...

Summary

• Breaking changes (🔴 MAJOR): ✗
• New features (🟡 MINOR): ✗
• Bug fixes (🟢 PATCH): ✓

This PR will trigger a PATCH version bump when merged.

---

Manual override: If this is incorrect, you can manually add one of these labels:

• semantic:major - Breaking changes
• semantic:minor - New features
• semantic:patch - Bug fixes
• semantic:none - No version bump

Once a manual label is added, this workflow will respect it and not override.