[stiwicourage]

Summary

• Hvad ændrer sig? develop er 12 commits foran main (33 filer, +1602/−74):
  • Nye GitHub Actions-workflows: Publish.yml, Tests.yml, codeql.yml, dependency-review.yml og powershell.yml.
  • Fem lokale composite actions: check-coverage, create-annotated-tag, create-verified-commit, ensure-psresource-repository og update-git-ref.
  • CI-scripts: Invoke-NovaModuleToolsCI.ps1, Invoke-CodeSceneAnalysis.ps1, Repair-CodeSceneJaCoCoCoverage.ps1, og Install-CiPowerShellModules.ps1 med ejet, isoleret modulmappe.
  • Unit-coverage er slået til (Pester.CodeCoverage.Enabled: true, mål 90 %).
  • PSAvoidUsingWriteHost er undtaget i ScriptAnalyzer-indstillingerne.
  • Rettelse: den isolerede modulmappe videregives nu mellem workflow-trin, så Invoke-NovaBuild findes i Publish.yml.
  • Dokumentation og tests er opdateret.
  • Versionen er 0.1.0-preview01 (før 0.1.0-preview).
• Hvorfor? Opsætning af en sikker CI/CD- og publiceringskæde til PSGallery, med coverage-gates og CodeScene-analyse. Publish-kørslerne fejlede, fordi modulstien og de lokale actions manglede.
• Link: Publish-fejl: https://github.com/stiwicourage/PSModuleUpdate/actions/runs/40088728832 og https://github.com/stiwicourage/PSModuleUpdate/actions/runs/40089372252

Affected area

• Public PowerShell cmdlet behavior
• Scaffolding or project layout
• Build, test, analyzer, or CI behavior
• Release, changelog, or versioning flow
• Contributor documentation
• End-user documentation
• Command help
• Other

Review guidance

• Start med .github/workflows/Publish.yml og .github/actions/create-verified-commit. De ændrer main og develop og opretter tags.
• scripts/build/ci/Install-CiPowerShellModules.ps1 og Invoke-NovaModuleToolsCI.ps1 styrer, hvor modulerne installeres, og hvad der køres.
• Tests: tests/repository/CiWorkflow.Tests.ps1, RunTestsDependencies.Tests.ps1 og Invoke-NovaModuleToolsCI.Tests.ps1.
• Afvejning: PSAvoidUsingWriteHost er undtaget, fordi værtsoutput er tilsigtet. Andre analyzer-fund blokerer stadig.
• Kendt begrænsning: Publish.yml ryder ikke den midlertidige modulmappe op, i modsætning til Tests.yml.
• Ikke afprøvet: release-, tag- og push-trinnene i Publish.yml er ikke kørt på GitHub efter rettelserne.

Validation

• Invoke-NovaBuild
• Test-NovaBuild
• Targeted validation for the changed path
• Full repository quality loop
• Docs-only change; executable validation not needed

Validation notes:

Invoke-Pester tests/repository -Output Minimal
Tests Passed: 56, Failed: 0, Skipped: 3
(kørt på develop med de seneste CI-rettelser; build, Test-NovaBuild og fuld quality loop er ikke kørt)

Documentation and release follow-up

• README.md reviewed and updated if needed
• CONTRIBUTING.md reviewed and updated if needed
• CHANGELOG.md reviewed and updated if needed
• RELEASE_NOTE.md reviewed and updated if needed
• Command help updated if needed
• End-user docs updated if needed
• No documentation or release-note updates were needed

Maintainability, compatibility, and risk

• Maintainability impact considered
• No breaking change
• Breaking change
• CI or release impact

Risk, rollout, or rollback notes:

Ingen ændring af den offentlige cmdlet-adfærd.
Når PR'en merges til main, kører Publish.yml og kan udgive til PSGallery, oprette release-commit og tag samt nulstille develop.
Kræver secret PSGALLERY_API i repo'et.
Rollback: revert merge-commit'et; et allerede udgivet PSGallery-modul kan ikke trækkes tilbage.

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

[codescene-access]

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-access]

Code Coverage Gates Passed
Overall Coverage: 96.5% (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: 96.5% covered >= threshold = 95%
  • Action:
    You have 143 files with a sum of 832 covered and 30 uncovered lines of code.

• New & Changed Code Coverage

  • Pass/Fail Reason:
    No executable lines of code changed. (The change touched 0 files).