fix(ci): replace broken Rust workflow with Go tooling (audit #161)

[KooshaPari]

User description

Summary

• CI workflow (.github/workflows/ci.yaml) was invoking cargo fmt / clippy / test on a Go repo with no Cargo.toml, failing in 18-46s on every push/PR including chore(deps): add dependabot.yml covering cargo, gomod, npm, github-actions #20 and chore(deps): bump 10 npm packages (23 HIGH CVE fixes) #25.
• Replaces it with a Go-native workflow: go vet + go build per module (both backend/byteport Go 1.23.1 and backend/nvms Go 1.22.2), with gofmt as an advisory (non-blocking) check.
• go vet and go build verified locally clean for both modules on the current default branch.
• 30+ files are not gofmt-clean on default; that pre-existing debt is intentionally out of scope here to keep this unblock narrowly focused. Advisory fmt job will surface them without blocking merges.

Test plan

• CI on this PR: Go Vet (backend/byteport) green
• CI on this PR: Go Vet (backend/nvms) green
• CI on this PR: Go Build (backend/byteport) green
• CI on this PR: Go Build (backend/nvms) green
• CI on this PR: Go Fmt (advisory) reports unformatted files but does not block
• After merge: rebase chore(deps): add dependabot.yml covering cargo, gomod, npm, github-actions #20 and chore(deps): bump 10 npm packages (23 HIGH CVE fixes) #25 and verify Go jobs pass (those PRs touch no Go code)

Refs velocity audit #157 finding: CI failures on #20 and #25 were pre-existing default-branch breakage, not per-PR regressions.

---

Note

Low Risk
Low risk: changes are confined to the GitHub Actions workflow, swapping failing Rust jobs for standard Go checks; main risk is CI behavior/coverage changes rather than runtime code impact.

Overview
Replaces the CI workflow’s Rust-based checks (cargo fmt/clippy/test) with Go-native validation across the two Go modules (backend/byteport, backend/nvms).

Adds matrixed go vet ./... and go build ./... jobs using each module’s go.mod for version selection and caching, and introduces a non-blocking gofmt -l advisory job that surfaces formatting drift without blocking merges.

^{Reviewed by Cursor Bugbot for commit dc907a9. Bugbot is set up for automated code reviews on this repo. Configure here.}

---

CodeAnt-AI Description

Replace broken Rust CI checks with Go validation

What Changed

• CI now runs Go vet and Go build for both Go modules instead of failing Rust commands that did not match this repository
• Formatting is checked as an advisory step, so unformatted files are reported without blocking merges
• The workflow now targets each module separately, keeping CI coverage aligned with the codebase

Impact

✅ Fewer false CI failures
✅ Unblocked pull requests in the Go repo
✅ Clearer formatting warnings without blocking merges

🔄 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.

[gemini-code-assist]

Warning

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

[codeant-ai]

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 finished reviewing your PR.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud