Semantic Versioning

You might say

AI asks me to upgrade a dependency from 18 to 19. Should I just do it?

A versioning convention where major.minor.patch numbers express the impact of a changeVersion identifiers like "react": "^18.3.1" convey clear risk levels: patch numbers mean backwards-compatible fixes, minor numbers introduce features, and major bumps warn of breaking architectural changes. Checking which segment shifts helps you evaluate upgrade hazards before blindly bumping numbers across breaking releases.

Know first

npm

SemVer

Click a segment to see what changing it means for risk

package.json

{
  "dependencies": {
    "react": "^18.3.1"
  }
}

^18.3.1: minor and patch updates are allowed; it never jumps to 19 by itself

18.3.118.3.2

Low risk

Usually a fix that does not change existing usage. Run a check after upgrading.

Semantic versioning announces a change's impact with three segments: the last fixes, the middle adds features, the first may break.

What each segment communicates

Patch: usually a fix: A change in the last segment is mostly a fix and stays compatible; the risk is lowest, but still run a check afterward.

Minor: usually new features: A change in the middle segment adds features without breaking existing usage; check whether the new features affect you.

Major: possibly incompatible: A change in the first segment may remove or alter existing behavior; read the release notes before upgrading and verify each part afterward.

Quick checkChoose the best answer

The project pins react at ^18.3.1, and AI suggests changing it to 19.0.0 because newer is better. What is the more careful approach?

Never upgrade and lock every dependency at its lowest versionRead the 19 release notes for breaking changes and assess the impact before upgradingAlways use the newest version because newer is always better

You can say this to an AI Agent

The project pins react at ^18.3.1. First read the 19.0.0 release notes and list the changes that affect this project, then decide whether to upgrade. If you upgrade, check every page for errors afterward and do not upgrade other dependencies along the way.

Learn next

1npm→2Build→

Recommended tool

Web fine-tuning tool · Selector Pro

Select page elements for precise AI edits

Click a button, text, or card, note the change, then copy its exact location to AI.

Open Selector Pro website