You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#175 fix: require explicit override for no-git bump fallback (#177)
Stop `nova bump` and `Update-NovaModuleVersion` from silently presenting
`Patch | Commits: 0` when Git-based bump inference is unavailable.
Add `-OverrideWarning` / `--override-warning` / `-o` as the explicit opt-in
for intentional non-git Patch fallback flows, add regression coverage, and
update bump docs and changelog.
Closes#175
Copy file name to clipboardExpand all lines: CHANGELOG.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,6 +19,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
19
19
### Fixed
20
20
21
21
- Fixed `nova bump` and `Update-NovaModuleVersion` so nested project folders now reuse parent Git repository history for bump inference instead of silently falling back to `Patch`.
22
+
- Fixed `nova bump` and `Update-NovaModuleVersion` so non-git bump flows now stop with a clear override-warning requirement instead of silently presenting `Patch | Commits: 0` as if it were an inferred result.
WARNING: Cannot infer the version bump label from Git history because no Git repository was found for this project path. Use -OverrideWarning to continue intentionally with a Patch fallback.
197
+
198
+
What if: Performing the operation "Update module version using Patch release label" on target "project.json".
199
+
```
200
+
201
+
Shows how to opt in explicitly to the Patch fallback when a project lives outside a Git repository and Nova therefore
202
+
cannot infer the semantic label from commit history.
203
+
189
204
## PARAMETERS
190
205
191
206
### -Path
@@ -259,6 +274,30 @@ AcceptedValues: [ ]
259
274
HelpMessage: ''
260
275
```
261
276
277
+
### -OverrideWarning
278
+
279
+
Allow the version bump to continue with the explicit Patch fallback when Git-based inference is unavailable.
280
+
281
+
Use this only when you intentionally want to bump a project outside a Git repository, for example in example/template
return'Cannot infer the version bump label from Git history because no Git repository was found for this project path. Use -OverrideWarning / --override-warning / -o to continue intentionally with a Patch fallback, for example in example or template flows.'
Copy file name to clipboardExpand all lines: src/resources/cli/help/bump.psd1
+11Lines changed: 11 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -7,6 +7,7 @@
7
7
'When the current stable version is 0.y.z, Nova keeps breaking-change bumps on the initial-development line and plans the next minor version instead of jumping to 1.0.0.',
8
8
'Set 1.0.0 manually once the software is stable. After that, nova bump can increment major versions normally.',
9
9
'Use --preview when you want an explicit prerelease iteration instead of the next stable semantic version.',
10
+
'When Git-based bump inference is unavailable, nova bump stops unless you opt in to the Patch fallback with --override-warning.',
10
11
'For more information, documentation, and examples, visit:',
Description='Re-import the built dist module before the version bump workflow starts so later CI steps keep using the correct built module state.'
44
+
},
45
+
@{
46
+
Short='-o'
47
+
Long='--override-warning'
48
+
Placeholder=''
49
+
Description='Allow an intentional Patch fallback when Git-based bump inference is unavailable, for example in example or template flows outside a Git repository.'
0 commit comments