-
Notifications
You must be signed in to change notification settings - Fork 0
[Epic] Release engineering and supply-chain hardening #32
Copy link
Copy link
Open
5 / 65 of 6 issues completedLabels
P1Significant semantic, completeness, correctness issues.Significant semantic, completeness, correctness issues.component: releaseVersioning, publication, release artifacts, and distributionVersioning, publication, release artifacts, and distributiondiscovered-by-codexIssues discovered via review by codex.Issues discovered via review by codex.domain: compatibilityPlatform, Rust-version, API, or format compatibilityPlatform, Rust-version, API, or format compatibilitydomain: distributionCrates.io, GitHub Releases, Homebrew, and installable artifactsCrates.io, GitHub Releases, Homebrew, and installable artifactsdomain: reliabilityFail-closed, deterministic, and robust operational behaviorFail-closed, deterministic, and robust operational behaviordomain: supply-chainDependencies, workflows, provenance, and publishing trustDependencies, workflows, provenance, and publishing trustepicOrganizing issue that tracks a coherent remediation workstreamOrganizing issue that tracks a coherent remediation workstreamproduction-readinessPart of the audited path from prototype to production-ready usePart of the audited path from prototype to production-ready userelease-blockerMust close before the production-readiness release gate can passMust close before the production-readiness release gate can passtarget: v0.2.0Must be resolved or explicitly waived before the v0.2 production auditMust be resolved or explicitly waived before the v0.2 production auditworkflow:production-readinessIncluded in automatic production-readiness work selectionIncluded in automatic production-readiness work selectionworkflow:production-readiness-gateEpic, audit, publication, or program gate requiring landed prerequisitesEpic, audit, publication, or program gate requiring landed prerequisites
Description
Metadata
Metadata
Assignees
Labels
P1Significant semantic, completeness, correctness issues.Significant semantic, completeness, correctness issues.component: releaseVersioning, publication, release artifacts, and distributionVersioning, publication, release artifacts, and distributiondiscovered-by-codexIssues discovered via review by codex.Issues discovered via review by codex.domain: compatibilityPlatform, Rust-version, API, or format compatibilityPlatform, Rust-version, API, or format compatibilitydomain: distributionCrates.io, GitHub Releases, Homebrew, and installable artifactsCrates.io, GitHub Releases, Homebrew, and installable artifactsdomain: reliabilityFail-closed, deterministic, and robust operational behaviorFail-closed, deterministic, and robust operational behaviordomain: supply-chainDependencies, workflows, provenance, and publishing trustDependencies, workflows, provenance, and publishing trustepicOrganizing issue that tracks a coherent remediation workstreamOrganizing issue that tracks a coherent remediation workstreamproduction-readinessPart of the audited path from prototype to production-ready usePart of the audited path from prototype to production-ready userelease-blockerMust close before the production-readiness release gate can passMust close before the production-readiness release gate can passtarget: v0.2.0Must be resolved or explicitly waived before the v0.2 production auditMust be resolved or explicitly waived before the v0.2 production auditworkflow:production-readinessIncluded in automatic production-readiness work selectionIncluded in automatic production-readiness work selectionworkflow:production-readiness-gateEpic, audit, publication, or program gate requiring landed prerequisitesEpic, audit, publication, or program gate requiring landed prerequisites
Parent
#26
Objective
Create a reproducible and reviewable path from an audited commit to crates.io and GitHub release artifacts. This epic owns MSRV/dependency policy, workflow pinning and least privilege, Cargo package boundaries, quality/release gates, v0.2 identity and licensing clarification, artifact provenance, and repository/tag protections.
Why this blocks release
Current HEAD still declares the already-published
0.1.4, breaks the published public API, and has no tag or GitHub Release. Rust 1.70 is claimed but unsupported. Sensitive workflows execute mutable action tags. Cargo packaging ships unrelated site/internal content, and there is no reproducible publish pipeline or tested binary artifact flow.Workstream order
Completion criteria
Relationships
Non-goals
Do not reuse
0.1.4, retroactively mutate its artifact, or publish while the final production audit is incomplete.