ci: add build smoke and release install smoke tests - #10
Merged
Conversation
Add release-smoke.yml workflow that triggers on GitHub release publication. Installs fspeek via go install from golang:1.26.2-trixie container, then runs smoke tests (version format and no-url exit behavior) to validate released versions work correctly out of the box.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.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
1 participant
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
CI Smoke Tests
smokejob toci.yml— builds from source and verifies--versionprints a recognizable version string, and that running with no--urlexits non-zero with usage output.Release Smoke
release-smoke.ymlworkflow triggered onrelease: published— enters agolang:1.26.2-trixiecontainer, installs viago install github.com/steadyfall/fspeek/cmd/fspeek@<tag>, and runs the same two checks to confirm the released module is installable and functional end-to-end.Pre-landing hardening (adversarial review)
github.ref_namenow assigned toTAGenv var before shell expansion (trust boundary fix)dev— a release binary must print a real version stringTest Coverage
Diff is CI configuration only — no new application code paths to audit.
Tests: 12 test files (unchanged)
Pre-Landing Review
Pre-Landing Review: 3 auto-fixed, 1 user decision (fixed). No issues remaining.
AUTO-FIXED:
release-smoke.yml:15—${{ github.ref_name }}directly in shell → assign toTAGenv var firstrelease-smoke.yml:23,ci.yml:56— binary invoked twice; now captures output on first runrelease-smoke.yml:21— removeddev|from release version regex (user decision A)Design Review
No frontend files changed — design review skipped.
Eval Results
No prompt-related files changed — evals skipped.
Plan Completion
No plan file detected.
Verification Results
No dev server / no plan file — skipped.
TODOS
No TODO items completed in this PR.
Test plan
go build ./cmd/fspeek)🤖 Generated with Claude Code