Repository navigation
feat(codereview): automatically validate packages for manual testing - #6
Merged
Merged
Conversation
wasdfra
approved these changes
Nov 13, 2026
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.
Automatically build a code-reviewer package on pull requests targeting
mainand pushes tomain, and make the final package available for manual testing only after its validation pipeline succeeds.Package-CodeReview: restore/build/test the .NET solution, build Windows/Linux/Intel macOS x64 bundles, and pack one npm.tgz.codereview-<version>artifact is uploaded only after every platform job succeeds; the one-dayunvalidated-codereview-<version>artifact is internal job-transfer output.cmf-codereview/npm/package.jsonon every run and stamp the .NET executable automatically. Artifact names and checks follow that version. This PR leaves the existing package version unchanged; future release bumps are separate changes to the npm manifest.manifest.jsonso multiple builds of the same version can be distinguished. Keep the final artifact for 30 days.Integration testing in a consuming project's PR pipeline, publication and npm tag changes are manual. The workflow has no RepoFlow publishing jobs, release switches, approval environments or registry secrets, and creates no Git tags or GitHub releases.
Validation: 13 package-helper tests pass, including version stamping, archive validation and smoke-result verification across multiple stable and prerelease versions. The preceding workflow revision passed all 279 .NET tests and native package installation/scan checks on Windows, Linux and Intel macOS; the updated PR automatically reruns those checks. Bash syntax and Actionlint checks passed for the unchanged workflow. Local NuGet restore used cached packages and reported vulnerability-feed connectivity warnings.