Prepare for prerelease and enhance changelog and contributing badges (#178)

* chore: prepare develop for next prerelease

* fix: Nova's CI/CD test flow installed.

* fix: package.json is no longer used.

* Add changelog link and badge to README

Added a link to the 'Keep a Changelog' website and its badge.

* Add 'Keep a Changelog' badge to CONTRIBUTING.md

Added a badge for 'Keep a Changelog' to the contributing guidelines.

* Update CONTRIBUTING.md with additional badges

Added badges for changelog and code health to CONTRIBUTING.md

* Rearrange badges in CONTRIBUTING.md

Moved CodeScene Average Code Health badge to a new position.

* Update CONTRIBUTING.md with consolidated badges

Consolidate badge links into the contributing section.

* Refactor contributing section with badges

Updated the formatting of the contributing section and added badges for changelog, code coverage, and code health.

* Update README.md badge formatting

Reformatted README.md to improve badge layout.

* #174 fix: detect parent git repositories for nova bump (#176)

Make nova bump and Update-NovaModuleVersion resolve Git history from
 parent repositories, so nested project folders infer the correct
 semantic version instead of falling back to Patch with Commits: 0.

 Add regression coverage for nested project bump inference and update the
 changelog.

 Closes #174

* chore: prepare next prerelease version

* #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

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

Author: stiwicourage

.github/dependabot.yml

@@ -18,6 +18,9 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Fixed
 
+- 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`.
+- 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.
+
 ### Security
 
 ## [2.3.0] - 2026-05-06
@@ -30,7 +33,19 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Render bold text in white across the hosted HTML documentation.
     - Emphasized `<strong>` and `<b>` text now stands out more clearly when scanning docs pages.
 
-## [2.2.0] - 2026-05-06
+### Fixed
+
+- Restore Nova-managed project test runs in CI/CD after `2.2.0` dropped the implicit `Pester` dependency.
+    - CI/CD environments no longer need custom logic to install `Pester` themselves before running project tests.
+    - Published `NovaModuleTools` manifests once again pull in `Pester 5.7.1` implicitly so existing CI/CD test flows
+      keep working without extra installation logic.
+    - `Test-NovaBuild` fails with a clear dependency error when `Pester` is not installed.
+
+## [2.2.0] - 2026-05-06 [YANKED]
+
+This release was yanked because it removed the implicit `Pester` dependency, before Nova's CI/CD test flow installed
+`Pester` explicitly. Projects using `NovaModuleTools 2.2.0` could fail to run tests in CI/CD unless maintainers added
+their own `Pester` installation step. The regression was fixed in `2.3.0`.
 
 ### Changed
 
@@ -85,10 +100,6 @@ Keep stable `Update-NovaModuleVersion` / `% nova bump` releases on the SemVer ma
     - Regular markdown elsewhere under `docs/` no longer breaks the help-generation step.
     - When PlatyPS export does not create the expected help folder, Nova now raises a stable documentation error instead
       of a raw rename-path failure.
-- Fix CI test dependency installation so `Pester 5.7.1` is installed explicitly instead of being pulled in implicitly
-  through the published `NovaModuleTools` manifest.
-    - Published prerelease manifests no longer force `Pester` as an install-time required module.
-    - `Test-NovaBuild` now fails with a clear dependency error when `Pester` is not installed.
 - Fix the repository `run.ps1` quality loop after the CI installer refactor introduced new ScriptAnalyzer warnings.
     - The internal CI installer helper now follows ScriptAnalyzer naming and `ShouldProcess` expectations.
     - `run.ps1` no longer stops in the analyzer step because of those helper warnings.
@@ -369,4 +380,3 @@ Keep stable `Update-NovaModuleVersion` / `% nova bump` releases on the SemVer ma
 [0.0.6]: https://github.com/stiwicourage/NovaModuleTools/compare/Version_0.0.5...Version_0.0.6
 [0.0.5]: https://github.com/stiwicourage/NovaModuleTools/compare/Version_0.0.4...Version_0.0.5
 [0.0.4]: https://github.com/stiwicourage/NovaModuleTools/compare/Version_0.0.3...Version_0.0.4
-

CHANGELOG.md

@@ -1,8 +1,7 @@
 ## Contributing
-
-[![CodeScene Hotspot Code Health](https://codescene.io/projects/78904/status-badges/hotspot-code-health)](https://codescene.io/projects/78904)
+[![KeepAChangelog](https://img.shields.io/badge/changelog-KeepAChangelog-%23E05735)](https://keepachangelog.ps) 
+[![codecov](https://codecov.io/github/stiwicourage/NovaModuleTools/graph/badge.svg?token=BLZP94DZKX)](https://codecov.io/github/stiwicourage/NovaModuleTools) 
 [![CodeScene Average Code Health](https://codescene.io/projects/78904/status-badges/average-code-health)](https://codescene.io/projects/78904)
-[![codecov](https://codecov.io/github/stiwicourage/NovaModuleTools/graph/badge.svg?token=BLZP94DZKX)](https://codecov.io/github/stiwicourage/NovaModuleTools)
 
 **This repository is intentionally opinionated about maintainability, however, we welcome contributions that align with
 our goals. We want to keep the codebase clean, maintainable, and easy to understand for both users and contributors.**

CONTRIBUTING.md

@@ -1,4 +1,7 @@
-# NovaModuleTools | [![CodeScene general](https://codescene.io/images/analyzed-by-codescene-badge.svg)](https://codescene.io/projects/78904) ![WorkFlow Status][WorkFlowStatus]
+# NovaModuleTools
+[![CodeScene general](https://codescene.io/images/analyzed-by-codescene-badge.svg)](https://codescene.io/projects/78904) 
+![WorkFlow Status][WorkFlowStatus]
+[![Keep a Changelog][changelog-badge]][changelog]
 
 NovaModuleTools is an enterprise-focused evolution of ModuleTools for structured PowerShell module development,
 repository automation, and maintainable Nova workflows.
@@ -220,6 +223,9 @@ These switches keep the behavior explicit and opt-in:
 - `Update-NovaModuleVersion -ContinuousIntegration` also falls back to a patch bump when the current `HEAD` already
   matches the latest tag, so release automation can seed the next prerelease line without requiring an extra commit
   first
+- `Update-NovaModuleVersion` and `% nova bump` now stop when Git-based bump inference is unavailable, unless you
+  explicitly opt in to the Patch fallback with `-OverrideWarning` / `--override-warning` / `-o` for a non-git
+  example/template flow
 - `Update-NovaModuleVersion` and `% nova bump` treat stable `0.y.z` versions as the SemVer initial-development phase,
   so breaking-change bumps stay on the `0.y.z` line by planning the next minor version instead of jumping to `1.0.0`
 - `Publish-NovaModule -ContinuousIntegration` restores the built module after publish completes
@@ -671,3 +677,5 @@ This project is licensed under the MIT License. See LICENSE for details.
 
 [PSGalleryLink]: https://www.powershellgallery.com/packages/NovaModuleTools/
 [WorkFlowStatus]: https://img.shields.io/github/actions/workflow/status/stiwicourage/NovaModuleTools/Tests.yml
+[changelog]: https://keepachangelog.com/
+[changelog-badge]: https://img.shields.io/badge/changelog-Keep%20a%20Changelog-%23E05735

README.md

@@ -20,7 +20,7 @@ Updates the project version in `project.json` based on git commit history.
 ### __AllParameterSets
 
 ```text
-PS> Update-NovaModuleVersion [[-Path] <string>] [-Preview] [-ContinuousIntegration] [-WhatIf] [-Confirm] [<CommonParameters>]
+PS> Update-NovaModuleVersion [[-Path] <string>] [-Preview] [-ContinuousIntegration] [-OverrideWarning] [-WhatIf] [-Confirm] [<CommonParameters>]
 ```
 
 ## DESCRIPTION
@@ -49,8 +49,10 @@ reports the detected `Major` label so you can see that the commit set contained
 guidance about manually setting `1.0.0` once the software is stable. With `-Preview`, stable versions still enter the
 next patch preview track instead of applying semantic history inference to the semantic core.
 
-When Git tags exist, only commits since the latest tag are considered. If the folder is not a Git repository, the
-command falls back to a patch bump.
+When Git tags exist, only commits since the latest tag are considered. If Git-based inference is unavailable because the
+project path is not inside a Git repository, the command stops with a clear warning/error instead of silently presenting
+an inferred-looking patch result. Use `-OverrideWarning` only when you intentionally want that Patch fallback, for
+example in example/template flows outside Git.
 
 If the repository exists but has no commits yet, the command stops with: `Cannot bump version because the repository
 has no commits yet. Create an initial commit first.`
@@ -186,6 +188,19 @@ CommitCount: 34
 Shows how stable `0.y.z` bumps still warn that `1.0.0` must be set manually when the API becomes stable, while
 breaking-change commits on that line continue to plan the next minor version instead of jumping straight to `1.0.0`.
 
+### EXAMPLE 10
+
+```text
+PS> Update-NovaModuleVersion -Path ./src/resources/example -OverrideWarning -WhatIf
+
+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.
+
+What if: Performing the operation "Update module version using Patch release label" on target "project.json".
+```
+
+Shows how to opt in explicitly to the Patch fallback when a project lives outside a Git repository and Nova therefore
+cannot infer the semantic label from commit history.
+
 ## PARAMETERS
 
 ### -Path
@@ -259,6 +274,30 @@ AcceptedValues: [ ]
 HelpMessage: ''
 ```
 
+### -OverrideWarning
+
+Allow the version bump to continue with the explicit Patch fallback when Git-based inference is unavailable.
+
+Use this only when you intentionally want to bump a project outside a Git repository, for example in example/template
+flows where no commit history exists.
+
+```yaml
+Type: System.Management.Automation.SwitchParameter
+DefaultValue: False
+SupportsWildcards: false
+Aliases: [ ]
+ParameterSets:
+  - Name: (All)
+    Position: Named
+    IsRequired: false
+    ValueFromPipeline: false
+    ValueFromPipelineByPropertyName: false
+    ValueFromRemainingArguments: false
+DontShow: false
+AcceptedValues: [ ]
+HelpMessage: ''
+```
+
 ### CommonParameters
 
 This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable,
@@ -291,6 +330,9 @@ reflect the new version.
 When `-ContinuousIntegration` is used with a real update, the command re-activates the built `dist/` module first. When
 combined with `-WhatIf`, Nova still previews the bump without changing the loaded module state.
 
+When Git-based inference is unavailable, `Update-NovaModuleVersion` now requires `-OverrideWarning` before it continues
+with the intentional Patch fallback.
+
 ## RELATED LINKS
 
 - https://github.com/stiwicourage/NovaModuleTools/blob/main/docs/NovaModuleTools/en-US/Get-NovaProjectInfo.md

docs/NovaModuleTools/en-US/Update-NovaModuleVersion.md

@@ -476,10 +476,13 @@ <h3><code>Update-NovaModuleVersion</code> / <code>% nova bump</code></h3>
                         <ul class="plain-list">
                             <li><strong>Best for:</strong> Git-driven semantic version updates</li>
                             <li><strong>Key parameters:</strong> <code>-Path</code>, <code>-Preview</code>,
-                                <code>-ContinuousIntegration</code>, or the CLI form <code>--preview</code> /
-                                <code>-p</code> and <code>--continuous-integration</code> / <code>-i</code></li>
-                            <li><strong>Notable behavior:</strong> falls back to a patch bump when the folder is not a
-                                Git repository, but throws when the repository exists and has no commits yet
+                                <code>-ContinuousIntegration</code>, <code>-OverrideWarning</code>, or the CLI form
+                                <code>--preview</code> / <code>-p</code>, <code>--continuous-integration</code> /
+                                <code>-i</code>, and <code>--override-warning</code> / <code>-o</code></li>
+                            <li><strong>Notable behavior:</strong> stops when Git-based inference is unavailable, unless
+                                you explicitly opt in to the Patch fallback with <code>-OverrideWarning</code> /
+                                <code>--override-warning</code> / <code>-o</code>; it still throws when the repository
+                                exists and has no commits yet
                             </li>
                             <li><strong>Major-zero rule:</strong> stable <code>0.y.z</code> projects keep
                                 breaking-change
@@ -504,10 +507,12 @@ <h3><code>Update-NovaModuleVersion</code> / <code>% nova bump</code></h3>
                             </div>
                             <div class="surface-example__surface" data-command-surface="powershell">
                                 <pre><code>PS&gt; Update-NovaModuleVersion -Preview -WhatIf
+PS&gt; Update-NovaModuleVersion -Path ./src/resources/example -OverrideWarning -WhatIf
 PS&gt; Update-NovaModuleVersion -ContinuousIntegration</code></pre>
                             </div>
                             <div class="surface-example__surface" data-command-surface="command-line" hidden>
                                 <pre><code>% nova bump --preview --what-if
+% nova bump --override-warning --what-if
 % nova bump --continuous-integration
 % nova bump --preview --confirm</code></pre>
                             </div>

docs/commands.html

@@ -177,9 +177,12 @@ <h3>How Nova chooses the bump label</h3>
                 <pre><code>0.0.1 + Patch -> 0.0.2
 0.1.0 + Minor -> 0.2.0
 0.1.0 + Major -> 0.2.0</code></pre>
-                <p>When Git tags exist, Nova uses commits since the latest tag. When the folder is not a Git repository,
-                    Nova falls back to a patch bump. When the repository exists but has no commits yet, Nova stops with
-                    a clear error.</p>
+                <p>When Git tags exist, Nova uses commits since the latest tag. When Git-based inference is unavailable
+                    because the project path is not inside a Git repository, Nova stops instead of silently presenting a
+                    normal-looking patch result. Use <code>-OverrideWarning</code> or the CLI form <code>% nova bump
+                        --override-warning</code> / <code>% nova bump -o</code> only when you intentionally want that
+                    Patch fallback for an example/template flow outside Git. When the repository exists but has no
+                    commits yet, Nova still stops with a clear error.</p>
                 <p>Nova treats prerelease versions as previews of a specific semantic version target. That means a bump
                     does not blindly carry prerelease labels such as <code>preview7</code> into the next major, minor,
                     or
@@ -215,11 +218,13 @@ <h3>How Nova chooses the bump label</h3>
                     <div class="surface-example__surface" data-command-surface="powershell">
                         <pre><code>PS&gt; Update-NovaModuleVersion -WhatIf
 PS&gt; Update-NovaModuleVersion -Preview -WhatIf
+PS&gt; Update-NovaModuleVersion -Path ./src/resources/example -OverrideWarning -WhatIf
 PS&gt; Update-NovaModuleVersion -ContinuousIntegration</code></pre>
                     </div>
                     <div class="surface-example__surface" data-command-surface="command-line" hidden>
                         <pre><code>% nova bump --what-if
 % nova bump --preview --what-if
+% nova bump --override-warning --what-if
 % nova bump --continuous-integration
 % nova bump --confirm</code></pre>
                     </div>

docs/versioning-and-updates.html

@@ -1,7 +1,7 @@
 {
   "ProjectName": "NovaModuleTools",
   "Description": "NovaModuleTools is an enterprise-focused evolution of ModuleTools, designed for large-scale PowerShell projects with a strong emphasis on structure, maintainability, and automated CI/CD pipelines.",
-  "Version": "2.3.0",
+  "Version": "2.3.1-preview01",
   "Preamble": [
     "Set-StrictMode -Version Latest",
     "$ErrorActionPreference = 'Stop'"

project.json

@@ -9,5 +9,7 @@ function ConvertFrom-NovaBumpCliArgument {
         '-p' = 'Preview'
         '--continuous-integration' = 'ContinuousIntegration'
         '-i' = 'ContinuousIntegration'
+        '--override-warning' = 'OverrideWarning'
+        '-o' = 'OverrideWarning'
     }
 }

src/private/cli/ConvertFromNovaBumpCliArgument.ps1

@@ -68,6 +68,7 @@ function Get-NovaCliLegacyOptionReplacement {
         '-installed' = "'--installed' or '-i'"
         '-local' = "'--local' or '-l'"
         '-moduledirectorypath' = "'--path' or '-p'"
+        '-overridewarning' = "'--override-warning' or '-o'"
         '-packagepath' = "'--path' or '-p'"
         '-packagetype' = "'--type' or '-t'"
         '-path' = "'--path' or '-p'"