Repository navigation
Commit dac4d01
committed
chore(release): derive the tag from the version the way tags are published
The script emitted `v${VERSION}`, so a 1.3.0 release printed `v1.3.0` while
every published tag is v1.0, v1.1, v1.2. CONTRIBUTING.md repeated the same
`v1.1.0` form, so the script and the docs agreed with each other and disagreed
with the repository.
The tag now drops a `.0` patch and keeps anything else: 1.3.0 → v1.3 (matching
v1.0/v1.1/v1.2 exactly), 1.2.1 → v1.2.1 so a fix release stays distinct from
the minor it patches, and a pre-release suffix is never stripped.
Also corrects the header comment: the script prints the release steps, it does
not create the tag itself.1 parent 1292181 commit dac4d01
2 files changed
Lines changed: 11 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
82 | 82 | | |
83 | 83 | | |
84 | 84 | | |
85 | | - | |
| 85 | + | |
| 86 | + | |
| 87 | + | |
86 | 88 | | |
87 | 89 | | |
88 | 90 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | 1 | | |
2 | 2 | | |
3 | | - | |
| 3 | + | |
| 4 | + | |
4 | 5 | | |
5 | 6 | | |
6 | 7 | | |
7 | | - | |
8 | 8 | | |
9 | 9 | | |
| 10 | + | |
| 11 | + | |
| 12 | + | |
| 13 | + | |
| 14 | + | |
| 15 | + | |
10 | 16 | | |
11 | 17 | | |
12 | 18 | | |
| |||
0 commit comments