Has anyone else noticed a change in how myriad-pro and chaparral-pro are rendering recently?

We've been investigating an issue on our production site where several UI elements (navigation, buttons, accordion titles, CTA bar) started appearing visually heavier/thicker — almost as if the font weight bumped up — without any changes on our end.

After digging into it, we compared our archived Typekit CSS (kit ID: lfg5klq, snapshot from January 30, 2026) against the currently served CSS and found the following:

• The font declarations (family names, weights, styles) are identical
• However, ALL underlying font asset IDs have changed across both families and all weights
• The font files moved from version 27 (/27/ in the CDN URL path) to version 31 (/31/)
• The kit shows a re-publish date of March 30, 2026

Before → After asset IDs:

• myriad-pro 700: 0001709e → 7735d918
• myriad-pro 400: 0001709a → 7735d919
• myriad-pro 600: 0001709c → 7735d91b
• chaparral-pro 400: 3b9aee4e → 7735d8ad
• chaparral-pro 600: 3b9aee4f → 7735d8bb

This strongly suggests Adobe pushed an update to the font binaries themselves (v27 → v31), which changed the glyph metrics — resulting in text appearing bolder or larger even though nothing in our kit configuration changed.

A few questions for the community and hopefully Adobe staff:

1. Has anyone else experienced this with myriad-pro or chaparral-pro recently?
2. Is there any changelog or release notes for font binary updates on Adobe Fonts? We couldn't find any public documentation on this.
3. Is there a way to pin a kit to a specific font version, or revert to the v27 binaries?

This is a significant issue for teams relying on Adobe Fonts for production web projects — a silent update to font metrics can cause unexpected visual regressions with no way to detect or prevent it. Would love to hear if others have run into this and how you handled it.

Thanks!