ci: disable Firecracker workflows and release artifacts - #7346
Merged
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Contributor
Contributor
There was a problem hiding this comment.
Pull request overview
Removes automated Firecracker preview validation and release artifacts, leaving Firecracker testing as an explicit local-only process.
Changes:
- Deletes the dedicated Firecracker integration workflow.
- Removes Firecracker artifact build, staging, and publication from releases.
- Updates Firecracker and Cloud Hypervisor documentation for the local-only validation model.
Show a summary per file
| File | Description |
|---|---|
.github/workflows/test-firecracker.yml |
Removes Firecracker artifact and live-KVM CI jobs. |
.github/workflows/release.yml |
Stops building and publishing Firecracker preview assets. |
docs/releasing.md |
Documents that releases no longer include Firecracker artifacts. |
docs/INTEGRATION-TESTS.md |
Describes Firecracker validation as local-only. |
docs/firecracker-integration.md |
Revises artifact and automation guidance. |
docs/cloud-hypervisor-foundation.md |
Updates comparisons with Firecracker CI. |
docs/awf-config-spec.md |
Documents locally built Firecracker test artifacts. |
Review details
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Suppressed comments (1)
docs/firecracker-integration.md:903
- The new statement that Actions no longer invokes Firecracker validation conflicts with this guide's remaining claims that CI supports GitHub-hosted Ubuntu at lines 17-19, 252-257, and 1084. The same stale CI-support claim also remains in
docs/architecture.mdanddocs/compatibility.md. Recast those as requirements for the retained local validation scripts; otherwise the documentation still advertises CI coverage that this PR removes.
The dedicated Firecracker Actions workflow is disabled. Artifact build,
verification, host preflight, and live smoke scripts remain in the repository
for explicit local use, but GitHub Actions does not invoke them.
- Files reviewed: 7/7 changed files
- Comments generated: 4
- Review effort level: Balanced
Comment on lines
+361
to
364
| Automated Firecracker artifact builds and release publication are disabled. | ||
| The reproducible artifact set can still be built explicitly with | ||
| `guest/firecracker/build-test-artifacts.sh`; its output includes | ||
| `release/firecracker-test-x86_64/awf-firecracker-test-x86_64.tar.gz`. |
Comment on lines
+397
to
+401
| based on the retained | ||
| [Firecracker test conventions](./firecracker-integration.md#part-14--ci-workflow) | ||
| but adapted for this backend's GitHub-hosted-only support statement and | ||
| jailer-free launcher. | ||
| jailer-free launcher. The corresponding Firecracker Actions workflow is | ||
| disabled. |
Comment on lines
+317
to
+319
| The `firecracker-test-x86_64` x86_64 test/preview artifacts can be built | ||
| explicitly from the repository, but are not built or published by GitHub | ||
| Actions. They are not production defaults and are never auto-downloaded. See |
Comment on lines
+202
to
+204
| The live smoke/security suite verifies all five SHA-256 digests before running. | ||
| Its preflight requires usable KVM and fails closed if `/dev/kvm` or another | ||
| required host capability is unavailable. |
Contributor
✅ Coverage Check PassedOverall Coverage
📁 Per-file Coverage Changes (1 files)
Coverage comparison generated by |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Validation
.github/workflows/release.ymlwithjs-yaml