ci(release): qualify supported self-hosted platforms - #1616
Conversation
|
Warning Review limit reachedNext included review available in 14 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (16)
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (4)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe release workflow now qualifies native Ubuntu 24.04 ChangesSupported host qualification
Estimated code review effort: 3 (Moderate) | ~25 minutes Merge Risk: ⚪ Minimal · up to This change narrows the documented supported host matrix and adds release qualification gates; no actionable merge-blocking risk remains after normal checks and review. Sequence Diagram(s)sequenceDiagram
participant ReleaseWorkflow
participant HostSmoke
participant DockerCompose
participant HTTPSIngress
participant PublishRelease
ReleaseWorkflow->>HostSmoke: Run amd64 and arm64 smoke tests
HostSmoke->>DockerCompose: Start stack and wait for readiness
HostSmoke->>HTTPSIngress: Curl HTTPS endpoint
HostSmoke-->>PublishRelease: Provide host-smoke JSON records
PublishRelease->>PublishRelease: Validate both records
PublishRelease-->>ReleaseWorkflow: Publish release when validation passes
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Full details: Linked Issues checkExplanation The pull request satisfies issue Full details: Out of Scope Changes checkExplanation The workflow, documentation, release-management guidance, and policy tests directly support the supported-host matrix and release qualification objectives. No unrelated application, container, migration, or environment-variable changes are present. Full details: Docstring CoverageExplanation No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 1 files. (3 skipped: 3 unsupported.) ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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. Comment |
📚 Documentation Preview
|
🧩 Storybook Preview
|
Draft releases are visible only to tokens with push access, so the supported-host smoke jobs' contents: read token could not download the still-draft release lock via prepare-release-lock.ts, failing every release before publication. Grant contents: write, matching the publish-release job's existing draft-asset download, and pin the permission in the deployment policy test. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Description
Define the supported self-hosted matrix as native Ubuntu 24.04 on
amd64andarm64, then make every release prove both cells before publication. Each smoke job verifies the signed release lock, boots the documented Compose topology, checks HTTPS ingress, and publishes a release- and commit-bound status record; the publish job rejects missing, duplicate, unhealthy, or failed-service evidence.This keeps the support promise deliberately narrow and gives operators durable qualification evidence instead of making the first ARM64 installation an unplanned test.
The generated web client is also refreshed with the repository's pinned generator because the API drift gate detected stale generated imports. The OpenAPI contract is unchanged.
Fixes #1605
How to test
bun run formatbun run checkbun run verifyChecklist