Skip to content

Release 2026-08-28 (i4 7597afdd) - #222

Closed
yy-code-nv wants to merge 1 commit into
mainfrom
release/2026-08-28-7597afdd
Closed

Release 2026-08-28 (i4 7597afdd)#222
yy-code-nv wants to merge 1 commit into
mainfrom
release/2026-08-28-7597afdd

Conversation

@yy-code-nv

Copy link
Copy Markdown
Collaborator

Forward release from imaginaire4 main 7597afdd01 onto cosmos-framework main
e66f6bc, generated by packages/cosmos-framework-release/release.sh.

Gate results: exit 0 — 0 SOURCE BREAKs, 0 DEST BREAKs, 26 DEST WARNs.

What this unblocks

This is the release that clears the two DEST BREAK collisions acknowledged in
#220. Both files were authored here in #217 (FP8 mixed-precision diffusion steps)
and backported into imaginaire4 as bfd655d67b; #220 recorded the destination
pairs, and this ships them.

It also advances _source_commit from 25433d97 — which predated that backport —
to 7597afdd01, which contains it. That matters for the backport gate: with the
old anchor the two adopted files reconstructed as absent from the baseline and
surfaced as add/add CONFLICTs (exit 3), even though nothing needed porting.
Verified against this tree, backport.py --check now exits 0 with nothing to
port, so COSMOS_FRAMEWORK_BACKPORT_CHECK can be re-enabled once this lands.

Content notes

  • mixed_precision.py — the released form is AST-identical to the current
    file; the diff is only line wrapping from imaginaire4's 120-col formatter.
  • step_callback_test.py — additionally gains import pytest and
    pytestmark = [pytest.mark.L0, pytest.mark.CPU], which imaginaire4's conftest
    requires (it skips unmarked tests) and we do not use. Inert here: no markers are
    declared in pyproject.toml and --strict-markers is off.

New files

model/tokenizer/task_types.py, model/generator/mot/action_io_projector{,_test}.py,
model/generator/mot/flex_attention_utils.py, data/generator/token_mix_control.py,
data/generator/augmentors/transfer_control_transform_test.py,
utils/generator/method_timer.py, and the reasoner
packing_mbs_advisor / true_packing pair.

task_types.py in particular resolves a SOURCE BREAK that had been blocking
releases from imaginaire4 main.

Forward release from imaginaire4 main 7597afdd01 onto cosmos-framework main
e66f6bc. Generated by packages/cosmos-framework-release/release.sh: exit 0, with
0 SOURCE BREAKs and 0 DEST BREAKs.

This is the release that clears the two DEST BREAK collisions #220 acknowledged.
Both files were authored here in #217 and backported into imaginaire4 as
bfd655d67b; #220 recorded the destination pairs, and this ships them.

It also advances _source_commit from 25433d97 (which predated that backport) to
7597afdd01 (which contains it). That matters for the backport gate: with the old
anchor the two adopted files reconstructed as absent from the baseline and
reported as add/add CONFLICTs. Verified against this tree, the check now exits 0
with nothing to port, so COSMOS_FRAMEWORK_BACKPORT_CHECK can be re-enabled once
this lands.

New in this release: task_types.py, action_io_projector{,_test}.py,
flex_attention_utils.py, token_mix_control.py, transfer_control_transform_test.py,
method_timer.py, and the reasoner packing_mbs_advisor / true_packing pair.
@yy-code-nv yy-code-nv closed this Aug 28, 2026
@yy-code-nv
yy-code-nv deleted the release/2026-08-28-7597afdd branch August 28, 2026 09:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant