# Semantic versioning reference — no upload

> A SemVer reference: major/minor/patch rules and npm-style version ranges (^, ~, x) explained. Runs in your browser, nothing fetched.

Understand semantic versioning — what major, minor, and patch bumps mean — and how npm-style ranges like ^, ~, and x resolve. The reference ships built in, so nothing is fetched.

SemVer is the contract that makes dependency management predictable: a version number tells consumers whether an update is safe. Knowing the range operators prevents both accidental breakage and needlessly pinned dependencies.

Generate a matching LICENSE and README badges for your package with the other dev generators.

## How to

1. **Read the rules.** See when to bump major, minor, or patch.
2. **Check a range.** Understand what ^1.2.0 or ~1.2.0 allows.
3. **Apply it.** Version your package or set a dependency range.

## FAQ

### What does ^1.2.3 allow?

The caret allows updates that don't change the leftmost non-zero version — so ^1.2.3 permits 1.x.x but not 2.0.0, keeping compatible updates.

### When should I bump the major version?

On any breaking change to your public API. Minor is for backward-compatible features; patch is for backward-compatible bug fixes.

### Is anything fetched?

No. The list ships with the tool and works offline.


## Related tools

- [README badge](https://www.safepaper.app/dev/badge-gen)
- [LICENSE](https://www.safepaper.app/dev/license-gen)
- [.gitignore](https://www.safepaper.app/dev/gitignore)
- [Date tokens](https://www.safepaper.app/dev/date-format-tokens)

---

Canonical HTML: https://www.safepaper.app/dev/semver-rules
Markdown: https://www.safepaper.app/dev/semver-rules.md

There is no upload endpoint — your files are processed in this browser tab. Open your network tab and check.