A breaking refactor, twelve days after launch
UCP 2026-01-23
What you need to do
If you built against v2026-01-11, read the GitHub diff for this release directly. The upstream notes are not detailed enough to tell you whether you are affected, so verify rather than assume.
What changed
A short release with one significant change: a refactor marked as breaking by its own commit, landing twelve days after the initial version.
The upstream notes are thin here. They record that the release happened and that it breaks compatibility, but not what specifically moved. If you integrated against the 11 January version, compare against the diff rather than trusting the summary.
This one is worth remembering as a pattern rather than for its contents. A specification this young will break things, and it will not always explain itself well when it does. That is the argument for checking your integration on a schedule rather than after you happen to read a release note.
## What's Changed * refactor!: updates for 2026-01-23 release by @wry-ry in https://github.com/Universal-Commerce-Protocol/ucp/pull/115 * fix: Regenerate package-lock with public registry urls by @kcthota in https://github.com/Universal-Commerce-Protocol/ucp/pull/108 ## New Contributors * @kcthota made their first contribution in https://github.com/Universal-Commerce-Protocol/ucp/pull/108 **Full Changelog**: https://github.com/Universal-Commerce-Protocol/ucp/compare/v2026-01-11...v2026-01-23