Repository navigation
chore(release): merge release/v1.1.5 into main - #2272
Merged
Merged
Conversation
…nitial-roofline hold (#2175) (#2185) * fix(orchestrator): refuse a skip_to_close the session's own facts contradict A skip_to_close ends the run on the agent's word and is booked as global_converged whenever budget is left. Session d11ccead closed at cycle 0 with a measured baseline and 9.3 h of budget left, and release qualification read that close as PASSED. The intent router now denies the hint (rule skip_to_close_contradicted) when a baseline is measured and the remaining budget still funds another cycle, so a live skip_to_close can only earn baseline_failed or time_exhausted. GPU work that keeps failing after the baseline still ends the run, through the sweep. compute_next_phase is unchanged: recorded decisions replay as they were made, and a hint already pending still closes the run. Part of #2167. * fix(orchestrator): tighten the skip_to_close refusal Drop the unread now_unix parameter, build the denial before recording it, and keep the PHASE CONTRACT rewording to the lines it replaces. * fix(orchestrator): show the agent the initial-roofline hold in the Phase block While PRELUDE or ENABLEMENT waits for the initial roofline it enqueued, the `=== Phase ===` block now carries a `hold` line: the roofline it waits for, how long the wait can still last, that no hint advances the phase, that `remaining_sec` is the phase's share rather than the session's, and that a `send_message` observation is the expected answer each tick. The PHASE CONTRACT no longer says `baseline_tput > 0` alone exits PRELUDE, and orchestration.md stops reading that share as urgency under a hold. One helper reads the hold's two inputs for both phase predicates and for the block, so the line the agent is shown and the exit decision cannot disagree. Part of #2167. --------- (cherry picked from commit e7b8bc7) Co-authored-by: Cursor <cursoragent@cursor.com>
* chore(release): cut 1.1.5 Move every site that tracks the packaged version to 1.1.5 and write the 1.1.5 section of docs/release-notes.md from the PRs merged between the 1.1.4 branch point (60b5770) and the 1.1.5 branch point (9da8788), plus #2185. The Unreleased entry moves into that section, and #2186, merged to main after the cut, is listed as a known issue. Co-authored-by: Cursor <cursoragent@cursor.com> * docs(release): correct the Magpie version, list the R9700 and quote the forge-loop refusal The component matrix names the Magpie release the 1.1.5 pin carries (0.3.0), the support matrix lists the Radeon AI PRO R9700 that 1.1.5 adds, and the upgrade note quotes the message forge-loop --resume prints for a 1.1.4 checkpoint. Co-authored-by: Cursor <cursoragent@cursor.com> --------- Co-authored-by: Cursor <cursoragent@cursor.com>
Code metrics gate: PASSEDJudged: the 9 files this change touches. Files it does not touch never fail it; anything found there is listed under Outside this change for information.
47 findings in files this change does not touchOutside this change (informational): 47
...and 22 more; the job log lists every row.
Thresholds and sources: |
chaojhou
approved these changes
Oct 28, 2026
chaojhou
approved these changes
Oct 28, 2026
chaojhou
left a comment
chaojhou
left a comment
Collaborator
There was a problem hiding this comment.
PR #2272 -- chore(release): merge release/v1.1.5 into main
What it does: merges release/v1.1.5 back into main, so main carries the 1.1.5 version bump, the 1.1.5 release notes and the compatibility-matrix fixes (R9700 row, Magpie 0.3.0), and the v1.1.5 tag becomes an ancestor of main. Against the merge base 21aa9d4 the PR changes only the eight version sites, docs/compatibility.rst and docs/release-notes.md.
Blocking issues: none
LGTM
Merged with "Create a merge commit" as the description asks: a squash would drop the release branch as a parent, and v1.1.5 would stop being reachable from main.
Checked: git diff 21aa9d4ce..81d8c2326 (README badge, docs/conf.py, pyproject.toml, install docs, examples/README.md, hyperloom-setup SKILL.md, HYPERLOOM_WHEEL_TAG default in install_baremetal.sh, compatibility.rst, release-notes.md); docs/release-notes.md from "## Hyperloom 1.1.5 release" down is byte-identical to the v1.1.5 tag, and its "## Unreleased" section equals current main's; no 1.1.4 version site remains (the two remaining hits are history in upgrade.md and the sphinx theme pin); v1.1.5 is an ancestor of the head | Ran: git merge-tree against current main (clean); gh pr checks (35 pass, 7 skipped) | Head: 81d8c23
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.
Merges
release/v1.1.5back intomainafter the v1.1.5 release, somaincarries the 1.1.5 version bump, release notes and compatibility-matrix fixes, and thev1.1.5tag becomes an ancestor ofmain.The release branch has two commits
mainlacks:docs/compatibility.rst): taken. Indocs/release-notes.md,## Unreleasedkeeps the four entriesmainmerged after the cut (SGLang 0.5.22,optimize --session-dir,hyperloom hosted run, GEAK processes after KERNEL_AGENT) and drops the accuracy-eval entry, which the 1.1.5 section now carries (Remove the accuracy eval opt-out #1984); everything from## Hyperloom 1.1.5 releasedown equals the released file.main's SGLang 0.5.22 image rows in the matrix are kept.main's version; fix(orchestrator): refuse a contradicted skip_to_close and show the initial-roofline hold #2175 is already onmain.Please merge with "Create a merge commit", not squash: squashing drops the release branch as a parent, and
v1.1.5stops being reachable frommain.main; CI runs the release and doc version tests. Checked thatgit diff origin/mainis limited to the eight version sites,docs/compatibility.rstanddocs/release-notes.md, that no1.1.4package pin remains outside the release notes, that the Magpie pin onmainis still6a1ee26f(Magpie 0.3.0), and thatv1.1.5is an ancestor of the merge commit.mainreports version 1.1.5 and its install pins andHYPERLOOM_WHEEL_TAGdefault point at the published v1.1.5 release.main.