Skip to content
This repository was archived by the owner on Jul 22, 2026. It is now read-only.

Release gate: v0.3-dev → v0.3.x - #315

Open
github-actions[bot] wants to merge 6 commits into
v0.3.xfrom
v0.3-dev
Open

Release gate: v0.3-dev → v0.3.x#315
github-actions[bot] wants to merge 6 commits into
v0.3.xfrom
v0.3-dev

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Standing release-gate PR. v0.3-dev accumulates incremental v0.3 work; this PR merges into the release-ready v0.3.x branch only once the cross-repo E2E pipeline is green. Comment /run-e2e v0.3 to fire it (genlayerlabs/genlayer-e2e). It may stay red while the v0.3 train is in progress.

github-actions Bot and others added 2 commits June 18, 2026 22:21
#313)

all.nix builds gen-00 (frozen v0.2.x runners). Their runners/cpython/deps/
zlib.nix hardcodes www.zlib.net/zlib-1.3.1.tar.gz (now 404 — zlib.net moved
1.3.1 to /fossils/) with no mirror. The head recipe produces the SAME
genvm-zlib-src output (same name + sha256, via dependency-urls.json) but with
a mirror, so nix realizes one of two same-output .drvs non-deterministically:
pick head and the dead URL falls back to the GCS mirror; pick the frozen one
and it 404s with no fallback -> ~50% of from-source runners-all builds fail.
Rewrite the frozen URL to the genvm-artifacts GCS mirror (head's own fallback,
which we control) before import so BOTH .drvs are resilient. fetchzip is
sha256-addressed, so the output path and all downstream runner hashes are
preserved.

Preserve file modes and rewrite only zlib.nix's contents: the frozen trees
ship executable build scripts (numpy's deps/stub-clang.py, 0755) and a blanket
cp --no-preserve=mode strips the exec bit, making the numpy configure phase die
with exit 126.

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@CLAassistant

CLAassistant commented Jun 19, 2026

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 3 committers have signed the CLA.

✅ kp2pml30
❌ github-actions[bot]
❌ dohernandez
You have signed the CLA already but the status is still pending? Let us recheck it.

kp2pml30 added 4 commits June 25, 2026 21:51
Rework how PRs into v<X>-dev are tested and merged.

Markers (presence-checked labels): `rtm` (ready-to-merge) and
`run-full-tests`; either one runs full tests. queue.yaml now runs the
cheap `initial` checks (pre-commit + 0-behind) on every push, runs the
heavy test jobs only when a marker is set, and fails validate-end when no
marker is present so the gate stays red until full tests have run.

Replace all /genvm-* slash commands with an auto-posted PR action panel
(branch_pr_checklist.yaml) whose checkboxes — Force/Rerun full tests,
Merge — are handled by branch_pr_actions.yaml + pr-action-panel.py. Any
human may tick; the box unticks itself. "Force/Rerun full tests" re-applies
the run-full-tests label; "Merge" calls the now-reusable
branch_merge_into_dev.yaml (workflow_call). Authority is enforced by the
merge gates, not by who ticks.

Also: retarget comment aliases main from v<X>-dev.
The "Force"/"Rerun full tests" boxes set the `run-full-tests` label with
the bot's GITHUB_TOKEN, but GitHub suppresses the resulting `labeled`
event (recursive-run guard), so queue.yaml never fired and the buttons
silently did nothing.

Trigger queue.yaml directly via `workflow_dispatch` instead, which DOES
run when fired by GITHUB_TOKEN. The handler dispatches on the PR head
branch so the run's head_sha equals the PR head and the Merge gate counts
it. Force still sets the sticky label (future pushes auto-run) and now
also dispatches once on the enabling edit; Rerun just dispatches.

- queue.yaml: add `workflow_dispatch`, run on it, mark its run-name
- branch_pr_actions.yaml: grant `actions: write` to dispatch
- pr-action-panel.py: replace label-toggle with `gh workflow run`
- genvm-merge-into-dev.py: count workflow_dispatch runs on the head sha
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants