Skip to content

chore(ci): add Go CI workflow and smoke test#18

Merged
KooshaPari merged 1 commit intomainfrom
chore/ci-test-floor
Apr 24, 2026
Merged

chore(ci): add Go CI workflow and smoke test#18
KooshaPari merged 1 commit intomainfrom
chore/ci-test-floor

Conversation

@KooshaPari
Copy link
Copy Markdown
Owner

@KooshaPari KooshaPari commented Apr 24, 2026

User description

Summary

  • Add Go CI workflow (build + test + vet) on ubuntu-latest for backend/byteport
  • Add TestSmoke to ensure the test harness has something to run
  • Skip macOS/Windows runners per GitHub Actions billing policy

Part of Tier-2 audit task #63: establish minimum CI/test floor.

Test plan

  • go build ./... succeeds in backend/byteport
  • go test ./... runs TestSmoke
  • CI green on ubuntu-latest

Note

Low Risk
Low risk: adds a GitHub Actions workflow and a trivial smoke test, with no production code or runtime behavior changes.

Overview
Adds a new GitHub Actions Go CI workflow that runs go build, go test, and go vet on ubuntu-latest for backend/byteport (Go 1.23, with module cache keyed by go.sum).

Introduces a minimal TestSmoke in backend/byteport/smoke_test.go to ensure the Go test harness executes in CI.

Reviewed by Cursor Bugbot for commit 41cebeb. Bugbot is set up for automated code reviews on this repo. Configure here.


CodeAnt-AI Description

Add a Go CI check for builds, tests, and vetting

What Changed

  • Adds a GitHub Actions workflow that runs Go build, tests, and vet on Linux for the backend/byteport app on push and pull request
  • Adds a minimal smoke test so the Go test run always has a real test to execute
  • Limits the new CI job to the main branches and Linux runners

Impact

✅ Earlier detection of broken builds
✅ Fewer empty test runs in CI
✅ Faster feedback on backend changes

🔄 Retrigger CodeAnt AI Review

Details

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

Establishes the minimum Tier-2 CI floor: Linux ubuntu-latest runner
executes go build, go test, and go vet against backend/byteport.
Adds a single smoke test so the test harness has something to run.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@gemini-code-assist
Copy link
Copy Markdown

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

@codeant-ai
Copy link
Copy Markdown

codeant-ai Bot commented Apr 24, 2026

CodeAnt AI is reviewing your PR.


Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

@codeant-ai codeant-ai Bot added the size:M This PR changes 30-99 lines, ignoring generated files label Apr 24, 2026
@codeant-ai
Copy link
Copy Markdown

codeant-ai Bot commented Apr 24, 2026

CodeAnt AI finished reviewing your PR.

- uses: actions/setup-go@v5
with:
go-version: '1.23'
cache-dependency-path: backend/byteport/go.sum
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SUGGESTION: Consider using go-version: '1.23' to match the exact version in go.mod (1.23.1) for better reproducibility

@kilo-code-bot
Copy link
Copy Markdown

kilo-code-bot Bot commented Apr 24, 2026

Code Review Summary

Status: 1 Issues Found | Recommendation: Address before merge

Overview

Severity Count
CRITICAL 0
WARNING 0
SUGGESTION 1
Issue Details (click to expand)

SUGGESTION

File Line Issue
23 Consider using go-version: '1.23' to match the exact version in go.mod (1.23.1) for better reproducibility
Files Reviewed (2 files)
    • 1 issues
    • 0 issues

Reviewed by nemotron-3-super-120b-a12b-20230311:free · 315,755 tokens

KooshaPari pushed a commit that referenced this pull request Apr 24, 2026
Supersedes 0.31.0 bump. 0.35.0 is the first patched version covering
both the critical GHSA-v778-237x-gjrc and the high-severity
GHSA-hcg3-q754-cr77 advisories across all 4 go.mod manifests:

- backend/byteport/go.mod
- backend/nvms/go.mod
- backend/nvms/Demonstrator/go.mod
- backend/nvms/Provisioner/go.mod

Resolves Dependabot alerts:
  CRIT: #16, #20, #22, #24 (GHSA-v778-237x-gjrc)
  HIGH: #18, #21, #23, #25 (GHSA-hcg3-q754-cr77)

Verified via go build ./... in each module.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
KooshaPari added a commit that referenced this pull request Apr 24, 2026
…fixes) (#19)

* chore(deps): bump golang.org/x/crypto to 0.31.0 (4 CRIT CVE fixes)

Fixes 4 CRITICAL Dependabot alerts (< 0.31.0) across the 4 backend
Go modules. Transitively upgrades golang.org/x/sys to 0.28.0 and
golang.org/x/text to 0.21.0 via go mod tidy.

Modules updated:
- backend/byteport: v0.29.0 -> v0.31.0 (direct)
- backend/nvms: v0.28.0 -> v0.31.0 (indirect)
- backend/nvms/Demonstrator: v0.28.0 -> v0.31.0 (indirect)
- backend/nvms/Provisioner: v0.28.0 -> v0.31.0 (indirect)

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* chore(deps): bump golang.org/x/crypto to 0.35.0 (4 CRIT + 4 HIGH CVEs)

Supersedes 0.31.0 bump. 0.35.0 is the first patched version covering
both the critical GHSA-v778-237x-gjrc and the high-severity
GHSA-hcg3-q754-cr77 advisories across all 4 go.mod manifests:

- backend/byteport/go.mod
- backend/nvms/go.mod
- backend/nvms/Demonstrator/go.mod
- backend/nvms/Provisioner/go.mod

Resolves Dependabot alerts:
  CRIT: #16, #20, #22, #24 (GHSA-v778-237x-gjrc)
  HIGH: #18, #21, #23, #25 (GHSA-hcg3-q754-cr77)

Verified via go build ./... in each module.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Forge <forge@phenotype.dev>
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@KooshaPari KooshaPari merged commit 6693572 into main Apr 24, 2026
7 of 11 checks passed
@KooshaPari KooshaPari deleted the chore/ci-test-floor branch April 24, 2026 22:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:M This PR changes 30-99 lines, ignoring generated files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant