Discover · microsoft.com

Do AI coding agents care about SemVer?

Microsoft for Developers microsoft.com

Semantic versioning tells developers how risky an upgrade is. A patch fixes bugs, a minor release adds features without breaking anything and a major release breaks things, so you know how closely to look before you upgrade. On paper, that signal is redundant when an AI coding agent does the upgrade. The agent has no muscle memory tied to the old API. It can read the new code and run the tests, so why would it care what the version number says? We suspected it wouldn’t, and that SemVer had become something only people need.

Two models proved us wrong. Across two experiments and almost 1,000 runs, the version number alone changed what they did with byte-identical code. Given an upgrade that broke the app, Claude Sonnet 5.5 ran the tests or read the new code in 2 of 10 runs when the upgrade was labeled a patch, and in all 10 when it was labeled a major release. Other models checked every upgrade, whatever the label said. Some agents still read SemVer, and for them, a patch label is a reason to check less.

More ways to use this
Open on another device
Scan this QR code to open the same public page

Scan to open this page. Your saved notes and account access are not included.

Download QR code

Open the page link

In the piece

Keep going

Each of these is read from what this estate already kept: the feed a piece came through, the publisher behind it, the credits and topics the publisher printed. None of it is a recommendation, an identity or a record kept anywhere else.

More like this

Also from Microsoft for Developers

  1. Your best AX fixes are hiding in agent trajectoriesWaldek Mastykarz microsoft.com
  2. Does ‘eval’ in the workspace path change what your agent does?Waldek Mastykarz microsoft.com
  3. Publish Visual Studio Marketplace extensions securely with Trusted PublishingLynn Dai microsoft.com
  4. PostgreSQL Like A Pro: Build, query, and troubleshoot without leaving VS CodeCynthia Zanoni microsoft.com
  5. Can a local git remote replace GitHub in your agent eval?Waldek Mastykarz microsoft.com
  6. Introducing the Agent Experience (AX) Practitioner PlaybookWaldek Mastykarz microsoft.com