Skip to content

Gather requirements for release after v1.12.2 #718

Description

@mparrett

Tracking issue to scope the next cut after v1.12.2 (2026-07-20), modeled on #275 / #545. About 55 commits have landed on main since that tag (through #628, f3ca5f9b, 2026-08-11), with another ~20 open PRs in flight. Freeze scope here, draft the upgrade notes, run the pre-release checks, and list blockers before we tag.

#545 still tracks the v1.12.0 cut that already shipped (v1.12.0–v1.12.2). Close or retarget it so release tracking has one live home.

Scope snapshot

Range v1.12.2..main @ f3ca5f9b: 55 merged PRs (~54k insertions / ~8k deletions across ~237 files). Headline arcs:

Behavior changes to note for the release

Consumer- and embedder-facing; confirm wording before the tag:

Known open items that touch the cut

Already filed; decide accept / fix / defer before tagging:

Issue Why it matters for the cut
#700 Bytecode invoke ~1.7× costlier since #645; explains residual reduce / some / etc. cost after #686
#663 Startup ~5 ms → ~9 ms unnoticed; ratchet not in the everyday loop
#705 Perf gate can report green through a regression (budget, filter, soft-else)
#704 Generated-primitive guards can pass when their premise breaks
#660 / #678 Silent AOT fallback; 6/16 gold-aot fixtures Tier-2 under strict
#607 lower-vm embedded fallback rejected (capability mask 0x1 vs 0x0); Gloat regression
#636 Self tail call lowers to a Go call (stack growth once AOT), constant-space on VM
#681 (PR) Phase-1 backend parity / strict-mode audit: makes the #660/#678 frontier visible in CI

In-flight PRs worth naming in scope freeze (not a full queue): #681, #706, #649, #675, #692, #501/#502, #624, #641, #683, #713.

Downstream dependencies

Pre-release checklist

Open questions

Add other release-worthy items or blockers below.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    Status
    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions