npm run regen # dumps NexHub's app.openapi(), runs Orval, rebuilds the barrel
The generated hooks are not the public surface. Each domain's hooks.ts re-exports
a curated set under short aliases, so a newly generated endpoint stays unreachable to
consumers until it is aliased there. After a regen, diff src/generated/api/ for new
use* exports and decide which belong.
Webhooks are deliberately never aliased — they are server-to-server receivers, and a React hook for one is only a way to make a mistake.
npm run release # infers the bump from the commits — prefer this
npm run release:breaking # force a breaking release
npm run release:fix # force a patch
⚠️ changelogen downshifts one step on any 0.x version. In bumpVersion it maps
major → minor and minor → patch while the version starts with 0., so on this
package:
| Flag | Actual bump from 0.4.0 |
|---|---|
--major |
0.5.0 |
--minor |
0.4.1 |
--patch |
0.4.1 |
--minor and --patch are therefore the same thing here, which is why those script
names were removed. A feat!: or BREAKING CHANGE: commit already makes plain
npm run release choose major and land on the right number — v0.3.1 was published by
overriding that inference with --minor, and had to be superseded by v0.4.0.