Commit b4ff9f3 1 parent 987b557 commit b4ff9f3 Copy full SHA for b4ff9f3
File tree 1 file changed +3
-4
lines changed
1 file changed +3
-4
lines changed Original file line number Diff line number Diff line change @@ -195,7 +195,6 @@ The `distance_to_latest_tag` is a special value that is replaced with the number
195
195
Now when you run ` bump-my-version show-bump ` , you can see the new pre-release versioning path.
196
196
197
197
``` console title="Showing the new versioning path with pre_n automation"
198
-
199
198
$ bump-my-version show-bump
200
199
0.1.0 ── bump ─┬─ major ─ 1.0.0-dev0
201
200
├─ minor ─ 0.2.0-dev0
@@ -211,17 +210,17 @@ $ bump-my-version show-bump 1.0.0-rc0
211
210
├─ minor ─ 1.1.0-dev0
212
211
├─ patch ─ 1.0.1-dev0
213
212
╰─ pre_l ─ 1.0.0
214
- ```
213
+ ```
215
214
216
215
The ` pre_n ` path is now missing because it is automated.
217
216
218
217
The full development and release path now is:
219
218
220
219
- ` 1.0.0 `
221
220
- ` bump patch ` → ` 1.0.1-dev0 `
222
- - each commit will increase → ` 1.0.1-dev1 `
221
+ - each commit will increase → ` 1.0.1-dev1 `
223
222
- ` bump pre_l ` → ` 1.0.1-rc0 `
224
- - each commit will increase → ` 1.0.1-rc1 `
223
+ - each commit will increase → ` 1.0.1-rc1 `
225
224
- ` bump pre_l ` → ` 1.0.1 `
226
225
227
226
1 . You must decide on the next version before you start developing.
You can’t perform that action at this time.
0 commit comments