fix: configure autolabeler and improve release-drafter workflow

[j-d-ha]

Summary

Fix Release Drafter autolabeler configuration and improve workflow to properly label PRs and generate changelogs.

Changes

Autolabeler Configuration

• Added autolabeler section to .github/release-drafter.yml
• Maps PR titles to labels using regex patterns matching conventional commits format
• Patterns: feat:, fix:, docs:, refactor:, test:, chore:, ci:
• Also detects BREAKING CHANGE: in PR body for breaking-change label
• Improved regex patterns for reliability: /type(\([^)]*\))?:/i

Version Resolution

• Added default: patch to version-resolver
• Ensures PRs without specific labels still increment patch version
• Prevents version resolution from failing

Workflow Configuration

• Restored pull_request trigger for autolabeler to work on new PRs
• Proper event types: opened, reopened, synchronize
• Correct permissions: contents: write, pull-requests: write
• Autolabeler enabled (disable-autolabeler: false)

How It Works Now

1. When a new PR is opened, autolabeler checks the title against patterns
2. If title matches conventional commits format, label is automatically applied
3. On push to main, Release Drafter creates/updates draft release
4. Labeled PRs are categorized and appear in correct changelog section
5. Version is calculated based on labels with patch as fallback

Testing

After merge, the autolabeler will work on all new PRs. Existing merged PRs without labels will not appear in the changelog unless manually labeled.

Next Steps

After merge:

1. Manually trigger bump-version workflow to create initial git tag
2. This establishes the reference point for future releases
3. Subsequent releases will automatically track changes since last tag

Checklist

• Autolabeler configuration added with proper regex patterns
• Version resolver has default fallback
• Workflow triggers on push and pull_request events
• Permissions correctly configured
• Configuration follows official Release Drafter documentation

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

@@           Coverage Diff           @@
##             main     #110   +/-   ##
=======================================
  Coverage   50.12%   50.12%           
=======================================
  Files          52       52           
  Lines        1640     1640           
  Branches      204      204           
=======================================
  Hits          822      822           
  Misses        765      765           
  Partials       53       53           

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3b5020f...542db91. Read the comment docs.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.