Skip to content

replay sequence: testify dependency update - #2

Open
jadoonf wants to merge 2 commits into
rb/14204from
rc/14204
Open

replay sequence: testify dependency update#2
jadoonf wants to merge 2 commits into
rb/14204from
rc/14204

Conversation

@jadoonf

Copy link
Copy Markdown

Two-stage fork-only replay of cli#14204. The first run establishes a same-PR pre-change runtime profile; the next commit removes the temporary marker and applies only the original upstream go.mod/go.sum patch. The final reviewed diff will contain only the dependency update. No upstream writes.

@garnet-runtime-review

garnet-runtime-reviewBot commented Aug 22, 2026

Copy link
Copy Markdown

Execution Profiles recorded for 1 job, triggered by a396425

1 job changed +1 destination · compared with 25c8e4f
recorded at the kernel by Garnet · 2026-08-22 04:53 UTC

+1 · Garnet Dependency Replay / go-modules ↗
@@ 25c8e4f (previous) vs a396425 (current) @@
Runner.Worker
└─ MainThread
├─ sh
│ └─ go
│ ├─ ○ proxy.golang[.]org
│ ├─ ○ storage.googleapis[.]com
+ │ └─ ○ sum.golang[.]org
├─ ○ api.github[.]com
├─ ○ github[.]com
└─ ○ release-assets.githubusercontent[.]com
systemd (runner background · +3)
├─ hosted-compute-
+ │ ├─ ○ 140.82.113.24+ │ ├─ ○ 140.82.114.24+ │ ├─ ○ glb-2a3c35-public-internal.githubapp[.]com (github infra)
│ └─ ○ localhost (dns resolver)
└─ systemd-network
└─ ○ ip6-allrouters

View this job's Execution Profile in Garnet →


💡 How to read this
Runner.Worker ← process on a path
└─ npm
└─ node← process that acted
└─ ○ npmjs[.]org ← observed action

follow a path downward to see what ran and what it did — each path to an observed action is an execution chain

names on the path = processes · ○ = observed action · (…) = context

+ only in the current record · − only in the previous record · runner background = the runner's infrastructure, not your workflow

@jadoonfjadoonf added the garnet-gate Run the strict Garnet runtime evidence gate label Aug 22, 2026

@github-actionsgithub-actionsBot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Garnet runtime evidence gate: HOLD

The recorded workload changed. Strict policy requires human review for every workload destination delta.
This decision consumed the exact-head Garnet Runtime Review before evaluating the gate.

EvidenceValue
PR heada39642519deefda2804d6d335f1e4bb6763a6fa2
Compared with25c8e4f4c6e026a57d6e3873d484b7b5b6f1868b
Recorded jobs1
Changed jobs1
Workload destinations+1 / -0
Process chains23
Total destinations11
Runner background+3 / -0 (non-gating)

Recorded workload diff

@@ 25c8e4f (previous) vs a396425 (current) @@
Runner.Worker
└─ MainThread
├─ sh
│ └─ go
│ ├─ ○ proxy.golang[.]org
│ ├─ ○ storage.googleapis[.]com
+ │ └─ ○ sum.golang[.]org
├─ ○ api.github[.]com
├─ ○ github[.]com
└─ ○ release-assets.githubusercontent[.]com
systemd (runner background · +3)
├─ hosted-compute-
+ │ ├─ ○ 140.82.113.24+ │ ├─ ○ 140.82.114.24+ │ ├─ ○ glb-2a3c35-public-internal.githubapp[.]com (github infra)
│ └─ ○ localhost (dns resolver)
└─ systemd-network
└─ ○ ip6-allrouters

Gate policy

  • Fail closed when exact-head evidence or a same-PR comparison is missing.
  • CLEAR only when the recorded workload has no changed job and no added, removed, or vanished workload destination.
  • Ignore runner-background rotation for the decision.
  • HOLD every workload delta for a human; this gate does not infer that a new CDN, registry, or checksum endpoint is safe.
    Policy result is bound to commit a39642519deefda2804d6d335f1e4bb6763a6fa2.

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

garnet-gateRun the strict Garnet runtime evidence gate

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@jadoonf