Question 1

What is semantic versioning and what does the caret mean?

Accepted Answer

Semantic versioning encodes intent in a three-part number. The major version increments on a breaking change, the minor on a backwards-compatible addition, and the patch on a backwards-compatible fix. The point is that a consumer can tell from the number alone whether an upgrade is safe.

Dependency ranges build on that. A caret allows updates that do not change the leftmost non-zero part, so it accepts minor and patch updates but not a major one. A tilde is narrower, typically allowing only patch updates. An exact version accepts nothing.

The caret is the default that package managers write, which means most projects are configured to accept new minor versions automatically. That is a deliberate trade: you receive fixes without intervention, and you depend on every maintainer classifying their changes correctly.

One rule surprises people. Below version one, the caret behaves more conservatively, allowing only patch updates, because the specification treats pre-one releases as unstable where anything may change. A dependency on a zero-point version is therefore pinned more tightly than the same range on a stable one.

The practical protection against a mistaken release is the lockfile. It records the exact resolved versions, so installs are reproducible regardless of what the ranges permit. This is why the lockfile belongs in version control and why continuous integration should install from it strictly rather than re-resolving.

The honest caveat is that semantic versioning is a convention rather than a guarantee. Breaking changes ship in minor releases by accident regularly. It is a useful signal and not a substitute for a test suite.

Question 2

What is API versioning, and how do you avoid breaking clients?

Accepted Answer

Managing change in an interface other people depend on — where the governing constraint is that once an API is published, you no longer control when consumers update, and in many cases they never

Question 3

What is the difference between PUT and PATCH?

Accepted Answer

PUT replaces a resource entirely with the representation you send. PATCH applies a partial modification. The distinction determines what happens to fields you do not mention, and that is where most

Question 4

What is the difference between npm install and npm ci?

Accepted Answer

The two commands serve different purposes, and the distinction matters most in continuous integration, where reproducibility is the whole point. Installing resolves the version ranges written in your

Question 5

Why does documentation always go out of date?

Accepted Answer

Because documentation and the code it describes are coupled in meaning but decoupled in enforcement — nothing breaks when they diverge, so they diverge. The core mechanism. Code has a merciless

Question 6

What is the difference between rolling back and rolling forward?

Accepted Answer

Reverting to the previous version versus fixing forward with a new release — and which is appropriate depends on factors that are worth deciding before an incident rather than during one. Rollback.

Question 7

What is a build artifact, and why does reproducibility matter?

Accepted Answer

An artifact is the packaged output of a build — a compiled binary, a container image, a library archive — and reproducibility means that building the same source produces an identical artifact, every

Related Questions