Skip to content

#238 fix: update Get-NovaProjectInfo and Update-NovaModuleTool comman…#239

Merged
stiwicourage merged 1 commit into
developfrom
bug/238-get-novaprojectinfo--installed-currently-returns-the-installed-novamoduletools-module-version
May 25, 2026
Merged

#238 fix: update Get-NovaProjectInfo and Update-NovaModuleTool comman…#239
stiwicourage merged 1 commit into
developfrom
bug/238-get-novaprojectinfo--installed-currently-returns-the-installed-novamoduletools-module-version

Conversation

@stiwicourage

Copy link
Copy Markdown
Owner

Summary

  • Aligned the PowerShell version-reporting surface with the existing CLI split by changing Get-NovaProjectInfo -Installed to mean the installed current project/module version and adding Get-NovaProjectInfo -InstalledNovaVersion for the installed NovaModuleTools version.
  • Updated the self-update next-step guidance plus README, command help, website docs, changelog, and release notes so the new PowerShell contract is documented consistently.
  • Link pending.

Affected area

  • nova CLI or command routing
  • Public PowerShell cmdlet behavior
  • Scaffolding or project.json handling
  • Build, test, analyzer, coverage, or CI helper flow
  • Package, raw upload, or package metadata workflow
  • Publish, release, or GitHub Actions automation
  • Self-update or notification preference behavior
  • Contributor documentation (README.md, CONTRIBUTING.md, repository workflow docs)
  • End-user docs (docs/*.html)
  • Command help (docs/NovaModuleTools/en-US/*.md)
  • src/resources/example/
  • Dependency or manifest changes (project.json, workflow dependencies, release tooling)
  • Security-sensitive change
  • Documentation-only change
  • Agentic Copilot Workflow + scaffold mirror + scaffold-sync guardrail test.
  • Other

Review guidance

  • Start with src/public/GetNovaProjectInfo.ps1, then check the PowerShell-only follow-on guidance in src/private/update/InvokeNovaModuleSelfUpdateWorkflow.ps1.
  • Primary changed areas: src/public/, src/private/update/, tests/public/, tests/private/update/, tests/ArchitectureGuardrails.Tests.ps1, docs/NovaModuleTools/en-US/, README.md, CHANGELOG.md, and RELEASE_NOTE.md.
  • This is a PowerShell behavior change, but it intentionally aligns the cmdlet surface with the already-established CLI semantics. CLI behavior is unchanged. project.json remains 3.1.1-preview, so the staged change currently targets the prerelease line and would roll into the next stable release unless superseded.

Validation

  • Invoke-NovaBuild
  • Test-NovaBuild
  • ./scripts/build/Invoke-ScriptAnalyzerCI.ps1
  • ./scripts/build/ci/Invoke-NovaModuleToolsCI.ps1
  • Targeted Nova workflow validated (% nova build, % nova test, % nova merge, % nova deploy, % nova publish, % nova release, % nova update, % nova notification, or % nova init as relevant)
  • Docs/example only; executable validation not needed

Validation notes:

pwsh -NoLogo -NoProfile -File ./run.ps1
- passed
- includes repository quality loop and reported no ScriptAnalyzer findings

pwsh -NoLogo -NoProfile -Command "Test-NovaBuild"
- passed

pwsh -NoLogo -NoProfile -Command "Invoke-NovaBuild | Out-Null; Import-Module ./dist/NovaModuleTools/NovaModuleTools.psd1 -Force; Import-Module Microsoft.PowerShell.PlatyPS -Force; Update-MarkdownCommandHelp -Path ./docs/NovaModuleTools/en-US/Get-NovaProjectInfo.md -NoBackup | Out-Null; Test-MarkdownCommandHelp -Path ./docs/NovaModuleTools/en-US/Get-NovaProjectInfo.md"
- passed

CodeScene pre-commit safeguard: passed
CodeScene change-set analysis vs main: passed

Documentation and release follow-up

  • README.md reviewed and updated if contributor workflow, architecture, CI, release, or automation changed
  • CONTRIBUTING.md reviewed and updated if contribution expectations or review guidance changed
  • CHANGELOG.md reviewed and updated if the change matters to users, maintainers, or contributors
  • RELEASE_NOTE.md reviewed and updated if the change affects public cmdlet usage, CLI usage, configuration semantics, or migration expectations
  • docs/NovaModuleTools/en-US/ help updated if a public command or CLI behavior changed
  • docs/*.html updated if end-user workflows or examples changed
  • src/resources/example/ reviewed and updated if the real-world project layout, package model, or upload workflow changed
  • No documentation, changelog, release-note, or example updates were needed

Maintainability, compatibility, and risk

  • Code Health / maintainability impact considered
  • No breaking change
  • Breaking change
  • Security-sensitive change
  • CI, workflow, or release-pipeline impact
  • Dependency-review impact

Risk, rollout, or rollback notes:

Compatibility impact:
- PowerShell behavior change: scripts/users that previously used `Get-NovaProjectInfo -Installed` to inspect NovaModuleTools itself must switch to `Get-NovaProjectInfo -InstalledNovaVersion`.

Migration note:
- PowerShell now maps to three views:
  - `Get-NovaProjectInfo -Version` -> project.json version
  - `Get-NovaProjectInfo -Installed` -> installed current project/module version
  - `Get-NovaProjectInfo -InstalledNovaVersion` -> installed NovaModuleTools version

Release impact:
- No publish or branch-release automation semantics changed.
- Changelog and release notes are release-ready under `Unreleased -> Changed`.
- This affects both prerelease and future stable consumers because it changes public cmdlet semantics, but it does not alter stable-vs-prerelease publishing logic.

Important

Do not use a public pull request to disclose a vulnerability before coordinated handling.
Use the private reporting path in SECURITY.md for new security issues.

…ds to enhance version retrieval and user guidance
@github-actions

Copy link
Copy Markdown
Contributor

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

@codescene-delta-analysis codescene-delta-analysis Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Gates Passed
6 Quality Gates Passed

See analysis details in CodeScene

Quality Gate Profile: Pay Down Tech Debt
Install CodeScene MCP: safeguard and uplift AI-generated code. Catch issues early with our IDE extension and CLI tool.

@codescene-delta-analysis codescene-delta-analysis Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Coverage Gates Passed
Overall Coverage: 99.8% (required = 95%)
New & Changed Code Coverage: 100% (required = 99%)

Review details by gate
  • Overall Coverage

    • Pass/Fail Reason:
      The overall coverage gate was checked for all code and meets the goal: 99.8% covered >= threshold = 95%
    • Action:
      You have 292 files with a sum of 3746 covered and 6 uncovered lines of code.
  • New & Changed Code Coverage

    • Pass/Fail Reason:
      New or changed code meets coverage goal: 100% covered >= threshold = 99%
    • Action:
      You modified 2 files, and covered 3 added/modified lines of code.

@stiwicourage
stiwicourage merged commit 94bf7c9 into develop May 25, 2026
14 checks passed
@stiwicourage
stiwicourage deleted the bug/238-get-novaprojectinfo--installed-currently-returns-the-installed-novamoduletools-module-version branch June 17, 2026 20:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Get-NovaProjectInfo -Installed currently returns the installed NovaModuleTools module version

1 participant