breaking[1]: propTypes stop being checked
A component that declares propTypes keeps compiling and keeps running. Nothing warns, and nothing is checked any more.
Understand before you upgrade.
React 19.0.0 shipped 13 breaking changes across 271 lines of release notes. One of them makes propTypes do nothing, silently, and it is on line 47.
Verdict follows the releases of the technologies in your stack and gives each one a single verdict: whether it asks something of you, what breaks, and how to migrate. Every claim points at the line of the release notes it was read from, so you can check it in one click instead of trusting it.
react 19.0.0lines 46 to 49 of 271
- * Errors in render are not re-thrown: Errors that are not caught by an Error Boundary are now reported to window.reportError.
- * Removed: `propTypes`: Using `propTypes` will now be silently ignored. If required, we recommend migrating to TypeScript or another type-checking solution.
- * Removed: `defaultProps` for functions: ES6 default parameters can be used in place.
- * Removed: `contextTypes` and `getChildContext`: Legacy Context for class components has been removed.
warning: action required
13 breaking8 notable271 lines read
One release, four stages
The same release the first screen quotes, read the way the app reads it: what the project published, the line the verdict rests on, the verdict itself, and where it goes next.
React 19.0.0featurednotes from GitHub Releases, 271 lines
source
271 lines, kept exactly as published and numbered so a claim can name one of them. The 13 breaking changes are listed in a single section, and the first screen shows lines 46 to 49.
cite
Using `propTypes` will now be silently ignored.
Nothing is paraphrased. The verdict quotes this line, points back at it, and would be wrong in a way you could see if the line said something else.
verdict
help
help: migrate to TypeScript props, or to another type-checking solution. release-notes:47
All 13 breaking changes are listed the same way on the release page, each with its own cited line and its own help line.
And when the notes are not that kind
Most releases do not publish 271 lines. What Verdict does with the thin ones is the same discipline, which is why it is on this page and not in a FAQ.
- Vite 6.0.0a changelog of 28 lines, where the two breaking ones are marked by a single
!and sit between achoreand aperf. read them apart - TypeScript 5.7.2a release whose body is a link to a blog post. There is nothing here to judge, so Verdict says exactly that and points at where the real notes live. see that state
note: not enough notes to judge
This is the sentence Verdict prints instead of a verdict when the notes only point elsewhere. “I found no breaking changes” and “there are no breaking changes” are different claims, and the second one is never printed in place of the first.
Four words on every release
Significance is a shape beside the version, never a hue: colour on this product means severity and nothing else. A release is not urgent because it is red, it is urgent because its notes say so, on a line you can read.
- featured
- The release where a technology changes direction: a new major where SemVer holds, a new minor for the projects that ship their real changes there. These open your dashboard, and they are the ones the page verdict counts.
- notable
- New work, no change of direction: a new minor under SemVer, an odd-numbered Node major. Worth reading, rarely urgent.
- digest
- What the rule treats as routine, patches first. They never interrupt: you read them grouped by ISO week, in one pass.
- preview
- A beta or a release candidate. Only the first preview of a new major is summarized, and canaries, nightlies and alphas are not releases here at all.
Follow the 10 technologies that decide your week.
The free plan follows up to 10 technologies from a curated catalog of 37. Sign-in is GitHub, and the release pages stay readable without it.
note: it does not open pull requests
Dependabot and Renovate do that well, and they tell you a version moved. A newsletter tells you a release was interesting. Verdict answers the question those leave open: does this release ask something of me, and where does it say so. It reads only the release notes, it never guesses, and when the notes say nothing it says nothing.