fix: ensure sequential release execution with failure gating

[nexus49]

Summary

• gh workflow run is fire-and-forget — it returns immediately without waiting for the triggered run
• This change records a timestamp before triggering, polls for the newly created run ID, then uses gh run watch --exit-status to block until completion
• If portal-ui-lib release fails, portal-server-lib is never triggered

Context

Review finding #3 from PR #226 — the PR description claimed sequential execution with failure gating, but both repos were triggered in parallel with no waiting.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 00d6f828-a24a-4920-8688-4ed4de0f06e5

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/release-sequential-execution

---

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.}