chore(deps): add dependabot.yml covering cargo, gomod, npm, github-actions#20
chore(deps): add dependabot.yml covering cargo, gomod, npm, github-actions#20KooshaPari merged 1 commit intomainfrom
Conversation
|
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 · |
|
CodeAnt AI finished reviewing your PR. |
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Overview
Other Observations (not in diff)
Files Reviewed (1 file)
Reviewed by step-3.5-flash · 198,350 tokens |
There was a problem hiding this comment.
Code Review
This pull request introduces a comprehensive Dependabot configuration file to automate dependency updates for various ecosystems, including Cargo, Go modules, npm, and GitHub Actions, across multiple directories in the repository. I have no feedback to provide.
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>
The CI workflow invoked cargo fmt / clippy / test on every push and PR, but this repository is Go (two modules: backend/byteport, backend/nvms) with no Cargo.toml. All three jobs failed in 18-46s with "could not find Cargo.toml" regardless of PR content, blocking PRs #20 and #25 and any other contribution. Replace with a Go-native workflow: - go vet per module (currently clean for both modules) - go build per module (currently clean for both modules) - go fmt as an advisory check (continue-on-error; 30+ pre-existing unformatted files are out of scope for this unblock and should be addressed separately) Refs velocity audit #157 finding: pre-existing breakage on default branch masquerading as per-PR failures. Co-authored-by: Forge <forge@phenotype.dev>
…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>
…tions Bootstraps Dependabot coverage per worklogs/DEPENDENCIES.md audit. Declared ecosystems: cargo (tauri), gomod (byteport + bytebridge + nvms x4), npm (frontend/web + .github/frontend), github-actions (root). No pip — repo has no Python manifests.
5e77c9a to
56900b6
Compare
|
CodeAnt AI is running Incremental review Thanks for using CodeAnt! 🎉We're free for open-source projects. if you're enjoying it, help us grow by sharing. Share on X · |
|
CodeAnt AI Incremental review completed. |
|



User description
Summary
Bootstraps Dependabot coverage for BytePort per the
worklogs/DEPENDENCIES.mdcoverage audit.Declared ecosystems:
cargo—frontend/web/src-taurigomod—backend/byteport,backend/bytebridge/ByteBridge,backend/nvms(+Builder,Demonstrator,Provisionersubdirs)npm—frontend/web,.github/frontendgithub-actions— rootWeekly schedule, grouped updates per ecosystem. No
pip— repo has no Python manifests.Context: GitHub currently reports 85 vulnerabilities on main — merging this gives Dependabot authority to open grouped update PRs against them.
Test plan
Note
Low Risk
Config-only change that just enables automated dependency update PRs; main risk is increased PR volume and grouped updates affecting multiple dependencies at once.
Overview
Bootstraps/expands
.github/dependabot.ymlto enable weekly Dependabot updates across multiple project areas:cargo(Tauri frontend), severalgomodmodules (BytePort/ByteBridge and NVMS subprojects),npm(web frontend and.github/frontend), andgithub-actions.Updates are grouped per ecosystem (wildcard patterns) and scheduled on different weekdays with per-area
open-pull-requests-limitsettings to control update volume.Reviewed by Cursor Bugbot for commit 56900b6. Bugbot is set up for automated code reviews on this repo. Configure here.
CodeAnt-AI Description
Expand Dependabot coverage across the repo
What Changed
Impact
✅ Broader dependency update coverage✅ Fewer Dependabot PRs at once✅ More predictable weekly update reviews🔄 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:
This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.
Example
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:
This helps CodeAnt AI learn and adapt to your team's coding style and standards.
Example
Retrigger review
Ask CodeAnt AI to review the PR again, by typing:
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.