Deduplicate equivalent CI job and PR/main checks while retaining release-toolchain coverage

Aperta
  • Qualcosa non va?
#340 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@kikashy ci sta già lavorando.

Dal 28/10/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

Audited 2026-10-28 at 57c854abb9ace8a91013a75ab688bd70d063797c: workflow definitions. This is a static workflow/manifest inventory, not a claim of measured savings or proven execution equivalence.

Findings

  • ci.yml runs vet/tests in the OS/Go matrix and again through the manifest check job. Establish whether the Ubuntu stable leg and check job resolve identical Go/runtime/flags before assigning a single owner.
  • PR and main execution can overlap; review verified tree-equivalent reuse through the shared contract without losing main coverage.
  • Preserve the Go compatibility-floor and macOS/Windows legs. Manifest CGO-disabled/trimpath builds and other matrix builds are not automatically equivalent.
  • #328 was closed intentionally with no code change: release Go 1.26.5 differed from CI, so release vet/tests/conformance had no equivalent producer. Its recorded decision remains valid unless resolved toolchains are aligned. Do not reopen that work solely because commands look alike, or add a per-PR release-toolchain leg merely to save one release run.
  • Preserve dispatch validation-only semantics, provenance/immutable Spec inputs, native archive smoke including ARM64, OCI and MCP publication checks.

Acceptance

  • Adopt the reviewed evidence/coverage contract in Devkit #60, with repository-specific independent review. Tree equality alone must never qualify a result.
  • Inventory check owners and resolved inputs: exact source/tree, trusted event/ref/base relationship, workflow/config/dependency digests, tools/images/OS, flags/environment and selected matrix coverage. Scope-limited PR evidence cannot cover unexecuted main checks.
  • Preserve required status names and fail closed on missing coverage, unexpected skips, incomplete/failed/canceled/newer incompatible attempts, stale or inaccessible evidence. Do not search backward for an older green attempt. Keep a documented bounded fresh-validation route.
  • Preserve distinct native platforms, compatibility floors, race/mutation/integration coverage, mutable advisory checks, commit/history/tag-sensitive checks, packaged-artifact checks, attestation and protected publication.
  • Add focused acceptance/refusal tests, including safeguard-removal controls for admission boundaries. Measure executed-check duplication and timings before/after; do not infer savings from workflow names or static overlap.
  • No automatic/required checks are disabled by this issue. This is next-release maintenance, not a waiver or retrofit to the in-flight Agent v0.11.0 release. Coordinate existing PRs before implementation.

Related image/runtime identity work: #339. Target: v0.39.0, matching the next milestone already chosen for the shared image-policy work.

Lingua principale
Go
Stelle
2
Fork
6
Merge medio
2h 22m
PR unite (30g)
89

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Judgment-Pack/judgment-pack-runtime

Tutte le issue di Judgment-Pack/judgment-pack-runtime

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.