fix(ci): restore reliable master verification

[yordis]

• ARM verification must fail on real subscription regressions instead of retrying against contaminated fixture state.
• Container release channels must derive from fully tested repository-owned images instead of unavailable external aliases.

[cursor]

PR Summary

Medium Risk
Changes release plumbing (what gets pushed to GHCR and when) and removes test retries that could hide flaky subscription regressions on master.

Overview
CI now saves the built eventstore image (not only the test image) as a workflow artifact on master and v* tag pushes, then publishes it to ghcr.io/trogonstack/trogoneventstore after the Ubuntu LTS matrix tests pass. Publication replaces the old scheduled EventStore/Automations retag flow and external test-data dispatches; tags are ci on master, full semver on tags, plus preview or stable / major / minor aliases for release builds. Builds also get OCI source/revision labels, and image artifacts use a 1-day retention.

Stream subscription combination tests batch fixture writes with a single AppendToStreamAsync, drop [Retry(3)] so failures are not masked, and dispose subscriptions with await using.

^{Reviewed by Cursor Bugbot for commit e490d53. Bugbot is set up for automated code reviews on this repo. Configure here.}

[coderabbitai]

Warning

Review limit reached

@yordis, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 1 minute

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 8327679d-2f16-4093-97c2-29e3bea5c91a

📥 Commits

Reviewing files that changed from the base of the PR and between e55aeec and e490d53.

📒 Files selected for processing (4)

• .github/workflows/build-container-reusable.yml
• .github/workflows/build-container-ubuntu-lts.yml
• .github/workflows/tag-docker-images.yml
• src/EventStore.Core.Tests/Services/Transport/Enumerators/Enumerator.StreamSubscription.CombinationTests.cs

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch yordis/fix-main-ci-health

---

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