ci: Fix auto-release

[mtrezza]

Summary by CodeRabbit

Release Notes

• Chores
  • Improved release workflow authentication with secure credential storage for GitHub operations.
  • Enhanced release trigger patterns to support greater flexibility in tag-based release detection.
  • Updated release labeling configuration for improved release organization and metadata handling.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[parse-github-assistant]

🚀 Thanks for opening this pull request!

[coderabbitai]

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

These changes adjust the CI/CD release automation configuration across three files. The release-automated workflow removes tag-based triggers while adding Git credential setup for semantic-release. The release-publish workflow broadens tag-filter patterns from strict version formats to wildcards. The release.config.js adds conditional release naming based on package type.

Changes

Cohort / File(s)	Change Summary
Release workflow trigger adjustments .github/workflows/release-automated.yml	Removed tag-based triggers (dart- and flutter- version patterns); retained branch-based triggers.
Release publish trigger expansion .github/workflows/release-publish.yml	Changed tag filters from precise semantic version patterns (dart-[0-9]+.[0-9]+.[0-9]+*) to broader wildcards (dart-*, flutter-*).
Git credential configuration .github/workflows/release-automated.yml	Added steps to enable credential helper store and persist credentials to ~/.git-credentials using secrets.RELEASE_GITHUB_TOKEN.
Release naming configuration release.config.js	Added releaseName option to @semantic-release/github plugin; conditionally formats release name as ${packageName}-${nextRelease.version} for non-root packages or ${nextRelease.version} for root.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Git credential setup steps are straightforward; verify token secret is properly configured
• Tag filter wildcard changes reduce specificity; confirm this broadening is intentional and won't trigger unrelated releases
• Release naming logic is minimal; review conditional package-name logic for correctness

Possibly related PRs

• ci: Fix auto-release #1078: Modifies release-automated.yml and changes semantic-release invocation and credential handling configuration.
• ci: Fix auto-release #1080: Updates release.config.js to modify semantic-release configuration (prepareCmd path for non-root packages).
• ci: Fix auto-release #1071: Adjusts tag-based triggers and tag-handling logic in release-publish.yml.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a8f941c and 5448dae.

📒 Files selected for processing (3)

• .github/workflows/release-automated.yml (1 hunks)
• .github/workflows/release-publish.yml (1 hunks)
• release.config.js (1 hunks)

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 43.46%. Comparing base (a8f941c) to head (5448dae).
⚠️ Report is 3 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #1085   +/-   ##
=======================================
  Coverage   43.46%   43.46%           
=======================================
  Files          61       61           
  Lines        3587     3587           
=======================================
  Hits         1559     1559           
  Misses       2028     2028           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

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