Repository navigation
Add published Action and npm smoke workflow - #7
Merged
Merged
Conversation
Adds .github/workflows/published-action-smoke.yml, run on dispatch and weekly. It checks out the fixture at the v0 tag and runs the Action from stackql/mcp-wringer@v0 and the CLI from the npm registry on Linux x64 and arm64, macOS and Windows: a clean run must report zero findings and a defective run must fail at the high threshold. It also checks that npm latest matches the tag's package version, since npm and the Action must be released from the same commit. The README's npx verification step now says to run it from outside the checkout. Inside the checkout, npx matches the repository's own package name and looks for a bin link that does not exist, which is what produced "'mcp-wringer' is not recognized" during the 0.1.0 release verification; the published package itself was fine. Also records the first consumer, the StackQL repository's pull request gate, and logs three ideas from that integration: a diagnostic when a run stops at durationMs before reaching cases, accepting a UTF-8 BOM in config files, and a spec input on the Action. Verified: both npm CLI commands behave as the workflow expects against the local fixture (exit 0 clean, exit 1 with crash.process-exit defective) from outside the checkout on Windows. actionlint 1.6.23 reports only its outdated runner label list for ubuntu-24.04-arm. Not verified: the workflow itself has not run yet; it needs the v0 tag and is dispatched after merge. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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
Adds a workflow that exercises the published artifacts the way a consumer does, and fixes a misleading verification step in the README.
Published Action smoke workflow
.github/workflows/published-action-smoke.yml, run onworkflow_dispatchand weekly:actionjob: checks out the fixture at thev0tag and runsstackql/mcp-wringer@v0on ubuntu-latest, ubuntu-24.04-arm, macos-latest and windows-latest. A clean run must report zero findings; a defective run (exit-on-decode-error) must fail atfail_on: high. Reusesscripts/assert-action-output.mjs.npmjob: same matrix, runsnpx @stackql/mcp-wringer@latestfrom the registry against the same fixture (exit 0 clean, exit 1 defective), and checks that npmlatestequals the tag'spackage.jsonversion.The self-test workflow covers the checked-out source; this one covers what users install.
README fix
During the 0.1.0 release the
npx ... --helpverification failed with'mcp-wringer' is not recognized. Root cause: it was run inside the repository checkout, wherenpxmatches the checkout's own package name and looks for anode_modules/.binlink that does not exist. The published package was fine (npm installin a scratch project andnpxfrom another directory both work). The README now says to run the command from outside the checkout, and the smoke workflow does the same.Docs
v0tag.docs/dev/ideas.md: three items from the StackQL CI integration (diagnostic when a run stops atdurationMsbeforecases; accept a UTF-8 BOM in config files; aspecinput on the Action).Verification
ubuntu-24.04-arm; the repo does not run actionlint.v0tag, which exists, and is dispatched after merge.