Commit f6ec1b8
committed
fix(ci): replace sed version bump with npm version
The publish workflow bumped the package version with a greedy sed that
matched every "version": "..." entry in package.json, corrupting
scripts.version (which the prepare-release lifecycle invokes via run-s).
Use npm version, which is JSON-aware and only touches the top-level field,
and restore the corrupted scripts.version back to "standard-version". A
post-bump assertion fails the release if scripts.version is ever clobbered
again.
For the repo's bare-semver release tags the bump is equivalent; npm version
additionally strips a stray leading "v" and validates semver (failing fast)
where the old sed wrote the tag verbatim. Flags: --no-git-tag-version (no CI
commit/tag), --allow-same-version (tolerate re-runs), --ignore-scripts (don't
fire the version lifecycle in CI).1 parent ee5f42e commit f6ec1b8
2 files changed
Lines changed: 9 additions & 4 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
83 | 83 | | |
84 | 84 | | |
85 | 85 | | |
86 | | - | |
87 | | - | |
88 | | - | |
| 86 | + | |
| 87 | + | |
| 88 | + | |
| 89 | + | |
| 90 | + | |
| 91 | + | |
| 92 | + | |
| 93 | + | |
89 | 94 | | |
90 | 95 | | |
91 | 96 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
47 | 47 | | |
48 | 48 | | |
49 | 49 | | |
50 | | - | |
| 50 | + | |
51 | 51 | | |
52 | 52 | | |
53 | 53 | | |
| |||
0 commit comments