Repository navigation
chore(release): cut 1.1.2 - #1619
Merged
Merged
Conversation
Every site that tracks the packaged version moves together: pyproject's [project].version, the docs version_number kept in sync with it, the README badge, the compatibility matrix row, and the three copy-paste `pip install hyperloom-inference-optimizer==` pins, which would otherwise keep installing 1.1.1 after 1.1.2 ships. HYPERLOOM_WHEEL_TAG moves with it, which requires the v1.1.2 GitHub release to carry the rocm-profiler-hotfix-libs.tar.gz asset the bare-metal installer downloads from that tag. Co-authored-by: Cursor <cursoragent@cursor.com>
The Unreleased section becomes the 1.1.2 section with an introduction, a "Before upgrading from 1.1.1" guide and highlights, and an empty Unreleased heading is kept for the next cycle. The upgrade guide names what an operator has to act on: the removed --conc-sweep-timeout-sec and --recipe-kb-strict-fingerprint options, the retired robustness-agent script and supervisor/robustness variables, the LLM_GATEWAY_KEY -> OPENAI_API_KEY rename, the dropped InferenceX local-copy variables and MAGPIE_PATCH_STRICT, the ROCm 10 images and bare-metal vLLM routes, and the SBD V6 and kernel summary field changes, which keep no alias. User-facing PRs merged without an entry get one under "Other changes". Two entries that described fixes to the robustness monitor are dropped or trimmed, since the monitor itself is retired in this release. Co-authored-by: Cursor <cursoragent@cursor.com>
The Slurm example registry still pointed its two vLLM rows at vllm/vllm-openai-rocm:v0.29.0 after the docker route moved to the ROCm 10 rocm/vllm image. The minimum-requirements row still listed ROCm 7.2.x alone, and the install guide and compatibility page still called TheRock's pip-packaged ROCm an untested layout, although it is the layout the rocm10 images are built from. The Python 3.12 requirement and the glibc floor apply to the ROCm 7.2.x vLLM wheel only, and the setup skill described the isolated vLLM option as always bringing its own torch, which the ROCm 10 source build does not. Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
…erride The note said the vLLM image's entrypoint is `vllm serve`, which was true of vllm/vllm-openai-rocm but not of rocm/vllm. Every image in the table now has no ENTRYPOINT and a `/bin/bash` CMD, which exits at once in a detached container, so the `--entrypoint tail` override is still needed for that reason. Co-authored-by: Cursor <cursoragent@cursor.com>
KERNEL entry runs out of band since #1605 and the phase is held until the hook returns. In this walkthrough the hook launched geak_runner.py as a real subprocess, and KERNEL only reached a terminal geak_result once that process failed, so whether eleven ticks reached CLOSE depended on how fast the runner exited on the CI host. The runner path is made unresolvable, which takes the existing runner_not_found branch: GEAK records a terminal result in-process and the phase winds down to SWEEP without starting anything. The test now also pins that branch, so a routing change cannot quietly bring the subprocess back. Co-authored-by: Cursor <cursoragent@cursor.com>
chaojhou
approved these changes
Sep 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cuts release 1.1.2 (54 PRs merged since
v1.1.1).Version bump: every site that tracks the packaged version moves together:
pyproject.toml[project].version1.1.1→1.1.2docs/conf.pyversion_numberREADME.mdversion badge1.1.1→1.1.2docs/compatibility.rstmatrix rowdocs/install/install.md,examples/README.md,hyperloom-setup/SKILL.mdpip install hyperloom-inference-optimizer==pinsinstall_baremetal.shHYPERLOOM_WHEEL_TAGv1.1.1→v1.1.2Release notes:
CHANGELOG.mdwas retired in #1589, sodocs/release-notes.mdis the only document to cut.## Unreleasedbecomes## Hyperloom 1.1.2 release, and an empty## Unreleasedstays for the next cycle. The new section has:Edits to inherited entries:
--resume-fromentry loses itsrobustness_monitor.shsentence. refactor: retire robustness supervision and simplify benchmark watchdogs #1547 retires that monitor in this same release./procmatch,HL_ORPHAN_MIN_AGE_S).ROCm 10 / image switch coverage: #1549, #1593 and #1605 left sites that still described the pre-ROCm 10 stack:
assets/slurm/models.tsvvllm/vllm-openai-rocm:v0.29.0to therocm/vllm:rocm10.0.0_..._vllm_0.27.0image the docker route usesdocs/compatibility.rstminimum requirements7.2.x→7.2.x, 10.0docs/compatibility.rst,docs/install/install.mdrocm10images are built from (install_baremetal.shROCM_SDK_INDEX_URL)docs/install/install.mdbare-metal requirementshyperloom-setup/SKILL.mdvllm (isolated)option covers both routes, and the glibc floor note is scoped to the wheel route;install_vllm_frameworkreturns intoinstall_vllm_from_sourcebeforeassert_vllm_glibc_compatibledocs/reference/environment-variables.md,docs/install/slurm.mdROCPC_VENV(#1549) andHL_ORPHAN_MIN_AGE_S(#1581) rowsdocs/compatibility.rstentrypoint notevllm serve; the--entrypoint tailoverride is kept for the real reasonThe image configs, read from the Docker Hub registry:
vllm/vllm-openai-rocm:v0.29.0(old)["vllm", "serve"]rocm/vllm:rocm10.0.0_..._vllm_0.27.0["/bin/bash"]lmsysorg/sglang-rocm:v0.5.20-rocm10-mi30x-20260920["/bin/bash"]rocm/atom-dev:v0.1.7-rc0["/bin/bash"]The
models.tsvswap also repairs the sbatch docker branch for the vLLM rows. It runsdocker run ... "${IMAGE}" bash "$INCONTAINER"without--entrypoint, which the old image turned intovllm serve bash .... The pyxis branch never used the image entrypoint..github/scripts/forge-ci-e2e-dispatch.shkeeps its own CI image default.Compatibility surfaces in this release
--conc-sweep-timeout-sec(#1547),--recipe-kb-strict-fingerprint(#1542). Both exitunrecognized argumentsnow.robustness-agent,tools/robustness_monitor.sh.example(#1547)HYPERLOOM_SUPERVISOR,HYPERLOOM_SUPERVISOR_ENFORCE,HYPERLOOM_SUPERVISOR_TICK_STALL_SEC,ROBUSTNESS_AGENT_ROOT,ROBUSTNESS_LLM_RCA_DISABLED(#1547);INFERENCE_OPTIMIZER_DISABLE_LOCAL_INFERENCEX,INFERENCE_OPTIMIZER_LOCAL_INFERENCEX_ROOT(#1456);MAGPIE_PATCH_STRICT(#1592)LLM_GATEWAY_KEYas the only OpenAI-side credential →OPENAI_API_KEY(#1541)recover-session --confirm-stopped TASK_ID --confirmation-reason TEXT(#1547),forge-loop --kernel-backend assembly(#1426),--applyback/--no-applyback(#1596)baseline_throughput/optimized_throughput→baseline_value/optimized_value, failure rowsphase→stage;kernel_optimization_summary.jsonschema_version2;sweep_failedstop reasonLATEST_STATE_SCHEMA_VERSIONis6in bothv1.1.1and this tree--max-minutes-enablement-pctis also removed, but it was added and removed within this release, so it is not in the upgrade guide.CI flake fix:
test_optimize_loop_walkthrough.py::test_both_arms_dry_walks_the_rest_of_the_chainfailed on py3.10 shard 1 ('KERNEL_AGENT' == 'CLOSE', teardown logged_on_phase_entered hook was cancelled). Since #1605 the KERNEL entry hook runs out of band and holds the phase until it returns. In this test the hook startedgeak_runner.pyas a real subprocess, and KERNEL only reached a terminalgeak_resultonce that process failed. Whether 11 ticks reached CLOSE therefore depended on the CI host. The test now makes_kernel_agent_tool_pathunresolvable, so GEAK takes the existingrunner_not_foundbranch in-process, and it asserts that branch. Delaying thegeak_runner.pyspawn by 30s fails the pre-fix test with the CI assertion and leaves the fixed test passing in 6.6s.None.
No code change. Verified by running:
pytest -n 4 src/kernelforge/tests/test_rename_completeness.py src/hyperloom/inference_optimizer/tests/test_baremetal_doc_version_consistency.py src/hyperloom/inference_optimizer/tests/test_scaffold_smoke.py src/hyperloom/inference_optimizer/tests/test_pre_release_gate_orchestration.py src/hyperloom/inference_optimizer/tests/test_preflight_serving_framework.py src/hyperloom/inference_optimizer/tests/test_multi_node_scripts.py: 198 passed.Every removed option, console script and environment variable named in the upgrade guide was checked present at
v1.1.1and absent from this tree.Size/complexity triggers crossed: split, or why the shape is right
Six commits. The first two are eight one-line version bumps plus
docs/release-notes.md, the same shape as #1519. The ROCm 10 coverage commit (4 files), the env-var doc commit (2 files) and the entrypoint note (1 file) are docs and a sample registry only; the last commit is a one-test fix.N/A.
Installs pin
1.1.2, and the bare-metal installer downloads its hotfix asset from thev1.1.2release. The release notes carry the 1.1.1 → 1.1.2 upgrade guide.The PR itself is not breaking. The release it cuts carries the removals listed above, and each has a "what to do" row in the upgrade guide.
Yes, the 1.1.2 release cut.
N/A.
Before merging
The
v1.1.2GitHub release must carry therocm-profiler-hotfix-libs.tar.gzasset, becauseHYPERLOOM_WHEEL_TAGnow points the bare-metal installer at that tag. Same requirement as v1.1.1.Test plan
vllm-openai-rocmreference in docs, examples, skills or packaged assets.v1.1.1.LATEST_STATE_SCHEMA_VERSIONunchanged (6).pyproject.tomlversion bump against base selects the FULL run.