Chrome 154 reached stable on September 22, and the headline change is a frame-sizing CSS property on <iframe>. Set frame-sizing: content-height on the iframe in the embedding page, and the element sizes itself to the embedded document's layout overflow instead of scrolling.
The embedded document has to opt in. It declares <meta name="responsive-embedded-sizing" content="allow-origins=*"> in its head, so the capability is not applied to a document that did not ask for it.
If you maintain an embed widget, a docs site with live examples, or a third-party checkout, this deletes the pattern you almost certainly have: measure the child, postMessage the height to the parent, patch the iframe style, and chase the resize events that slack behind the content. That loop is where most embedding bugs live.
Your action depends on which side of the frame you own. If you publish an embeddable document, adding the meta tag makes every Chrome 154 embedder size you correctly with no work on their end. If you consume embeds, the property only helps once the publisher opts in, so keep your postMessage fallback for now.