Determine an Aztec network's deployed commit
SkillCloud & infraDetermine which git commit an Aztec network (next-net, devnet, staging) is running now or was running at a past time T, and whether a specific fix or PR is live on it. Use for incident triage ("was the fix deployed when X happened?"), confirming a fix reached a network, or identifying the exact deployed commit.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Determine an Aztec network's deployed commit skill
What this skill tells your AI
The instructions your AI receives, as published by aztec-labs-eng/aztec-node in yarn-project/.claude/skills/network-deployed-version/SKILL.md and read by ahel’s review.
Aztec networks deploy via scheduled GitHub Actions workflows in aztec-labs-eng/aztec-node. The commit a network runs at time T is the headSha of the last successful deploy run at or before T — failed runs leave the previous commit live, so a string of failed nightlies can keep a network on a days-old commit.
Do not infer deployed code from local
origin/main— a network runs the last successful deploy, not the branch tip.
Run the investigation in a subagent
Do not run the gh/gcloud commands below in the main conversation — they flood context with run lists and raw file dumps for what is ultimately a one-line answer. Instead, spawn a general-purpose subagent, hand it the query parameters, and point it at this file. Relay only its condensed answer to the user.
Subagent prompt template (fill in the bracketed parts):
Determine [which commit
next-netwas running at 2026-06-20 14:00 UTC / whether the fix from public PR #23940 is live ondevnetnow / which commitstagingis running now]. The working directory isyarn-project. Read the file.claude/skills/network-deployed-version/SKILL.mdand follow its "Procedure" steps exactly, using the "Network → deploy workflow" table to pick the right workflow id.Return only: the deployed commit (full SHA + short), the deploy run id and the time it finished, whether the target fix/PR is present and the evidence you used to decide, and any relevant caveat. Do not paste raw
gh run listoutput or file contents.
If the optional live cross-check (step 4) is needed, the subagent can itself delegate to the network-logs agent.
Network → deploy workflow
| Network | Workflow | id | Source | Cadence |
|---|---|---|---|---|
| next-net | Deploy Next Net | 333053202 | main (latest nightly tag) | nightly, cron 0 6 * * * UTC (runs typically start/finish ~07:30–08:25 UTC due to GitHub schedule lag) |
| devnet | Devnet Auto-Deploy | 333051823 | v*-devnet-* branch | on push to the devnet branch; that branch is created on demand by "Create Devnet" (id 333054176, workflow_dispatch only) from a chosen nightly tag |
| staging (public) | Deploy to staging public | 333054183 | main → v5.0.0-nightly.<date> tag | nightly, cron 0 6 * * * UTC |
| staging (internal) | Deploy to staging internal | 333056854 | main → v5.0.0-nightly.<date> tag | nightly, cron 0 6 * * * UTC |
For times T before the repo split (August 2026), run history lives in the old repos instead:
AztecProtocol/aztec-packages-privatefor next-net/devnet/staging-internal,AztecProtocol/aztec-packagesfor staging-public. Same procedure, substitute the repo in-R.
Re-confirm ids/branches with gh workflow list -R aztec-labs-eng/aztec-node --all and the YAML under .github/workflows/.
Procedure
The subagent runs these steps against aztec-labs-eng/aztec-node (or the pre-split repo when T predates the split).
-
Find the live commit at time T:
gh run list -R aztec-labs-eng/aztec-node --workflow <id> --limit 20 \ --json databaseId,headSha,conclusion,createdAt \ --jq '.[] | "\(.createdAt) \(.conclusion) \(.headSha[0:12]) run=\(.databaseId)"'Take the most recent line with conclusion
successat/before T; skipfailure/cancelled. Note the full headSha. Confirm it finished before the event you're investigating:gh run view <run-id> -R aztec-labs-eng/aztec-node --json startedAt,updatedAt,conclusion -
Inspect code at that commit (no clone needed):
gh api "repos/aztec-labs-eng/aztec-node/contents/<path>?ref=<sha>" \ -H "Accept: application/vnd.github.raw+json"Read the actual file content at the ref — more reliable than commit-ancestry because fixes get ported across branches/repos with different hashes.
-
Is fix X present? Match by the code change or commit message, not the PR number — PR numbers differ across the pre-split repos (e.g. public #23940 == private port #23975). Do not rely on commit SHA either, these may change when squashing. For an ancestry check instead:
gh api "repos/aztec-labs-eng/aztec-node/compare/<base>...<head>"and read
status(ahead/identical⇒ base contains head). -
(Optional) Live cross-check via GCP Cloud Logging (project
testnet-440309, namespace = the network name, e.g.next-net): grep for the bug's runtime log signature over the last ~24h; its absence while the namespace is actively logging corroborates the fix is live. This is thenetwork-logsagent's domain — delegate to it for a thorough query.
Caveats
- A deploy run's
headShais the source branch tip at deploy-trigger time. Runs often finish in minutes, implying they deploy prebuilt images for that commit rather than building from scratch — if you need byte-level certainty, confirm the deployed image was built from that SHA. - Always check run
conclusion; never assume "the nightly for date D" succeeded. (eg at the time of writing, staging-internal nightlies were failing for several days straight — exactly the case where the live commit is older than the latest run.)
Signals
- GitHub stars
- 23
- Forks
- 4
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
network-deployed-version- Source
- github.com/aztec-labs-eng/aztec-node
github.com/aztec-labs-eng/aztec-node