ci: Fix auto-release

[mtrezza]

Summary by CodeRabbit

• Chores
  • Updated automated release workflow to handle edge cases more gracefully, allowing the release process to continue in certain scenarios where no changes require release. Improved overall release automation reliability.

_{✏️ 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

The changes modify semantic-release automation to treat exit code 69 as non-fatal. The release configuration now exits with code 69 instead of 1 when no package changes exist, and the workflow steps capture this code and only fail on non-zero codes other than 69.

Changes

Cohort / File(s)	Summary
Workflow exit code handling .github/workflows/release-automated.yml	Wraps dart and flutter package semantic-release steps in multi-line shell blocks that capture the exit code and conditionally exit with the code only if it is non-zero and not 69, treating 69 as a non-fatal signal.
Release gate configuration release.config.js	Changes the non-root verifyConditionsCmd to exit with code 69 instead of 1 when no changes exist in the package.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Focus on verifying the shell logic correctly captures and conditionally exits with the exit code.
• Confirm that exit code 69 semantics align between the workflow and release configuration.
• Verify no unintended side effects from treating 69 as non-fatal in the workflow progression.

Possibly related PRs

• ci: Fix auto-release #1073: Introduced the original exit code 1 behavior in verifyConditionsCmd; this PR changes it to 69 and adjusts workflow handling accordingly.
• ci: Fix auto-release #1074: Also modifies verifyConditionsCmd logic in release.config.js for detecting package changes.

✨ 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 8687cb8 and 8c274e9.

📒 Files selected for processing (2)

• .github/workflows/release-automated.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 (2d53dd1) to head (8c274e9).
⚠️ Report is 4 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #1075   +/-   ##
=======================================
  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.

[parseplatformorg]

🎉 This change has been released in version 9.4.0