[rawframe-release]

🤖 I have created a release beep boop

1.2.1 (2026-11-04)

This release makes a static shape that a host moves into a sleeping body touch it on the next step, and makes m2World_Restore refuse contact pairs the broadphase never makes. No golden line moves, and the snapshot and journal formats keep their versions.

Changed

• Results: no golden line moves (#319). Only a pair that a host call moves out of date gets a new manifold: a static shape moved into a sleeping body it already held a pair with. A pair whose shapes did not really move computes the same manifold as before.

Fixed

• A static shape that a host moves into a sleeping body touches it (#319). The step copies a pair's manifold forward without computing it when both bodies are static or asleep. m2Body_SetTransform and geometry setters such as m2Shape_SetPolygon move a static shape without waking a sleeper it does not touch, so when the two already held a pair, its old manifold stayed. A static wall teleported or widened into a sleeping box reported no contact points, no touching flag and no begin event, and moving the wall again did not wake the box. A pair with a moved shape now gets a fresh manifold, the one the same wall moved in from far away gets.
• m2World_Restore refuses a pair the broadphase never makes (#315): two shapes a mask or a negative group keeps apart, two sensors, two segments, a static shape with a kinematic one, two static shapes with a sensor among them, or the shapes of two bodies a joint without connected collision joins. The step kept such a pair until one of its shapes left its fat box, so the restored world pushed apart shapes the host keeps apart and reported a sensor inside another sensor. Two overlapping boxes pinned without connected collision ended 0.667 m apart after 30 steps with such a pair, instead of 0.6 m. A pair with a moved shape is still accepted, and so is a pair whose shapes drifted apart within their fat boxes.

---

This PR was generated with Release Please. See documentation.

[siracozmen01]

Curation review at 73b723f: ready. Read, not run.

• Files. 73b723f changes only CHANGELOG.md. At the repository root it is the only entry whose sha differs from 7e0ac26, and every directory tree is the same. 7e0ac26 is release-please's bump: the manifest and M2_VERSION_PATCH to 1.2.1.
• Patch. 1.2.1 is a correct patch at 1.x. Since v1.2.0 (#307) main merged #309 (docs), #311 (ci), #313 (test), #315 (fix) and #319 (fix). That is no feat and no !, and release-please's own entry listed exactly #315 and #319 under Fixed.
• Body and changelog. Every line of the body's entry is a line of the curated CHANGELOG.md. The diff adds the entry as the body gives it.
• Claims. Each one traces to the PR bodies:
  • Summary, and Changed: "no golden line moves", stale pairs only, same manifold for a pair that did not really move. Both bodies say no golden line moves and the snapshot and tape bytes are unchanged. #319's Change gives the stale-pair-only and same-manifold sentences. A patch with a "Results: no golden line moves" line follows 1.0.1's precedent.
  • Fixed, #319: the frozen copy, the setters that wake no sleeper, the missing contact points, touching flag and begin event, no wake on a second move, and the fresh manifold matching a wall from far away. All of it is #319's Problem and Change.
  • Fixed, #315: the list of pairs (masks, a negative group, two sensors, two segments, static with kinematic, two statics with a sensor, a joint without connected collision) matches #315's Problem and its eight refusals. The fat-box persistence, the push and the sensor overlap, 0.667 m against 0.6 m after 30 steps, and the moved-shape and within-margin pairs still accepted are also #315's.

The title and body have no column-0 name( line. This assumes, as the manager reports, that main b0565b4's release run is green and that v1.2.1 does not exist yet.

[rawframe-release]

🤖 Created releases:

• v1.2.1

🌻