Repository navigation
ci: validate docs package version against module manifest - #63
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Documentation builds could succeed with a package.json version that differs from the PowerShell module version. Validate package.json's version against ModuleVersion before building documentation in CI and the publishing workflow, and document the requirement to keep them in sync.
Validation
npm run docs:buildpassed. Executed the validation blocks from both workflows against the repository and isolated fixtures: matching versions pass; mismatched versions, a missing version, and invalid JSON fail.git diff --checkpassed. Actionlint passed with the existing unknown ubuntu-26.04 runner-label warning excluded. Pester was not run because module behavior is unchanged.Checklist