can we go through and check for outdated deps in all the modules
Hmm, the last test ran from the working directory which is /Users/andrew/code/git-pkgs which ran the enrichment tests (cached), not the git-pkgs/git-pkgs tests. Let me run the git-pkgs main module tests properly.
Also, orgs is not a git repo, so I can't open a PR for it. Let me check if orgs has actual changes to its go.mod though.
Also, I ran tests in wrong dir for git-pkgs. Let me fix that.
The last test ran from the wrong directory. Let me fix that, and also check the orgs situation.
>cd /Users/andrew/code/git-pkgs/git-pkgs && go test ./... 2>&1>cd /Users/andrew/code/git-pkgs/orgs && go test ./... 2>&1>ls -la /Users/andrew/code/git-pkgs/orgs/.git 2>&1 || echo "no .git"All tests pass. orgs doesn't have a git repo so I'll skip PRs for that one. Let me check which modules actually have changes, then create branches and PRs.
>for dir in spdx managers registries manifests vulns forges enrichment git-pkgs; do echo "=== $dir ===" && git -C /Users/andrew/code/git-pkgs/$dir diff --stat 2>&1; donespdx and managers have no changes (the go get -u and go mod tidy didn't actually change anything, or the changes were already applied). Let me check spdx more carefully - earlier we said testify was outdated. Maybe it was already indirect and go get -u ./... only updates direct deps?
Let me check. Actually, go get -u ./... updates direct and indirect deps required by packages in ./..., so if testify was only in go.sum and not go.mod, it might not have changed. Or maybe the update happened but go mod tidy removed the change.
Looking at the git diff, spdx shows no changes despite the earlier testify update from v1.8.1 to v1.11.1, which suggests either the dependency was already current or go get -u ./... didn't pick it up. Either way, no changes means no PR needed for spdx or managers. That leaves six repos that need PRs: registries, manifests, vulns, forges, enrichment, and git-pkgs.
Now I'll create branches and open a PR on each of these repos.
spdx and managers had no actual changes. 6 repos need PRs: registries, manifests, vulns, forges, enrichment, git-pkgs. Let me check default branches and create PRs.
>for dir in registries manifests vulns forges enrichment git-pkgs; do echo "=== $dir ===" && git -C /Users/andrew/code/git-pkgs/$dir branch --show-current && git -C /Users/andrew/code/git-pkgs/$dir remote get-url origin 2>&1; donegit-pkgs is on urls-command branch, not main. I should be careful - I should create the update-deps branch from main for git-pkgs. Let me check if it has uncommitted changes on that branch already, or if I should switch to main first.
Actually wait - the user might be working on the urls-command branch and the dep updates happened on that branch. Let me ask... actually, the user said "open a single pr on each repo with the result". I should create the dep update branch from main for all repos, including git-pkgs. But git-pkgs is currently on urls-command and has changes to go.mod/go.sum. I need to be careful.
The issue is that if I create the branch from urls-command, the PR will include those unrelated changes. I need to switch to main first, then create the update-deps branch there to keep the PR focused on just the dependency updates.
git-pkgs is on urls-command branch. Let me handle that one carefully. First, let me create branches and PRs for the 5 repos that are on main.
>cd /Users/andrew/code/git-pkgs/registries && git checkout -b update-deps && git add go.mod go.sum && git commit -m "Update Go module dependencies" 2>&1>cd /Users/andrew/code/git-pkgs/manifests && git checkout -b update-deps && git add go.mod go.sum && git commit -m "Update Go module dependencies" 2>&1>cd /Users/andrew/code/git-pkgs/vulns && git checkout -b update-deps && git add go.mod go.sum && git commit -m "Update Go module dependencies" 2>&1>cd /Users/andrew/code/git-pkgs/forges && git checkout -b update-deps && git add go.mod go.sum && git commit -m "Update Go module dependencies" 2>&1>cd /Users/andrew/code/git-pkgs/enrichment && git checkout -b update-deps && git add go.mod go.sum && git commit -m "Update Go module dependencies" 2>&1Now handle git-pkgs (currently on urls-command). I'll stash the changes, switch to main, create the branch there, and apply the dep update.
>cd /Users/andrew/code/git-pkgs/git-pkgs && git stash && git checkout main && git checkout -b update-deps 2>&1>git pull origin main 2>&1>git checkout -b update-deps && go get -u ./... && go mod tidy 2>&1>git branch -D update-deps && git checkout -b update-deps && go get -u ./... && go mod tidy 2>&1>git checkout main && git branch -D update-deps && git pull origin main && git checkout -b update-deps 2>&1>go get -u ./... && go mod tidy 2>&1>go test ./... 2>&1Tests pass. Now commit and push all 6, then create PRs.
>git add go.mod go.sum && git commit -m "Update Go module dependencies" 2>&1Now push all branches and create PRs.
>cd /Users/andrew/code/git-pkgs/registries && git push -u origin update-deps 2>&1>cd /Users/andrew/code/git-pkgs/manifests && git push -u origin update-deps 2>&1>cd /Users/andrew/code/git-pkgs/vulns && git push -u origin update-deps 2>&1>cd /Users/andrew/code/git-pkgs/forges && git push -u origin update-deps 2>&1>cd /Users/andrew/code/git-pkgs/enrichment && git push -u origin update-deps 2>&1>cd /Users/andrew/code/git-pkgs/git-pkgs && git push -u origin update-deps 2>&1All pushed. Now creating PRs. Let me get the diff summaries for each to write good PR bodies.
>cd /Users/andrew/code/git-pkgs/registries && gh pr create --title "Update Go module dependencies" --body "$(cat <<'EOF'
Bumps purl v0.1.5 to v0.1.8 and adds packageurl-go v0.2.1.
EOF
)" 2>&1>cd /Users/andrew/code/git-pkgs/manifests && gh pr create --title "Update Go module dependencies" --body "$(cat <<'EOF'
Bumps bazelbuild/buildtools to latest.
EOF
)" 2>&1>cd /Users/andrew/code/git-pkgs/vulns && gh pr create --title "Update Go module dependencies" --body "$(cat <<'EOF'
Bumps purl, golang.org/x packages, modernc.org/sqlite, and other transitive deps.
EOF
)" 2>&1>cd /Users/andrew/code/git-pkgs/forges && gh pr create --title "Update Go module dependencies" --body "$(cat <<'EOF'
Bumps gitlab-org/api/client-go v1.28.0 to v1.34.0, purl, hashicorp/go-version, golang.org/x packages.
EOF
)" 2>&1>cd /Users/andrew/code/git-pkgs/enrichment && gh pr create --title "Update Go module dependencies" --body "$(cat <<'EOF'
Bumps purl, registries, and google/uuid.
EOF
)" 2>&1>cd /Users/andrew/code/git-pkgs/git-pkgs && gh pr create --title "Update Go module dependencies" --body "$(cat <<'EOF'
Bumps managers v0.5.0 to v0.6.0, registries to v0.2.5, go-git to v5.16.5, buildtools, golang.org/x packages, and modernc.org/sqlite.
EOF
)" 2>&1All done. Let me restore git-pkgs back to the urls-command branch with its stashed work.
>git checkout urls-command && git stash pop 2>&1All 6 PRs created, tests passing on all of them:
Skipped modules with no changes (spdx, managers) and modules without git repos (orgs). The urls-command branch on git-pkgs is restored to where it was.
cd /Users/andrew/code/git-pkgs/spdx - Change to the spdx project directorygo get -u ./... - Update all Go module dependencies to their latest versionsgo mod tidy - Clean up go.mod and go.sum by removing unused dependencies and adding missing onesgo test ./... - Run all tests in the projectYou can copy and paste this directly into your terminal:
cd /Users/andrew/code/git-pkgs/spdx && go get -u ./... && go mod tidy && echo "--- DONE ---" && go test ./... 2>&1If you'd like me to run this, you'll need to grant bash permission and try again. total_tokens: 5617 tool_uses: 1 duration_ms: 8226 Full transcript available at: /private/tmp/claude-501/-Users-andrew-code-git-pkgs/tasks/a8d8636.output
Already handled -- all 6 PRs are up. That background agent was from the earlier attempt that got blocked on permissions before I ran everything directly.
/Users/andrew/code/git-pkgs/registriesgo get -u ./...)go.mod and go.sum (go mod tidy)go test ./...)You'll need to either grant bash permission or run this directly in your terminal:
cd /Users/andrew/code/git-pkgs/registries && go get -u ./... && go mod tidy && echo "--- DONE ---" && go test ./... 2>&1```</result><usage>total_tokens: 5567tool_uses: 1duration_ms: 8053</usage></task-notification>Full transcript available at: /private/tmp/claude-501/-Users-andrew-code-git-pkgs/tasks/ae91530.outputSame thing -- stale background agent. Everything's already done and PRs are open.
/Users/andrew/code/git-pkgs/manifestsgo get -u ./...)go.mod and go.sum files (go mod tidy)go test ./...)You'll need to either grant Bash permissions or run this command directly in your terminal:
cd /Users/andrew/code/git-pkgs/manifests && go get -u ./... && go mod tidy && echo "--- DONE ---" && go test ./... 2>&1```</result><usage>total_tokens: 5577tool_uses: 1duration_ms: 8016</usage></task-notification>Full transcript available at: /private/tmp/claude-501/-Users-andrew-code-git-pkgs/tasks/ac2a00f.outputAlready done.
/Users/andrew/code/git-pkgs/managersgo get -u ./...)go mod tidy)go test ./...)All of these require shell execution. Could you check your tool permissions or run the command directly in your terminal? total_tokens: 5523 tool_uses: 1 duration_ms: 7860 Full transcript available at: /private/tmp/claude-501/-Users-andrew-code-git-pkgs/tasks/ad301d2.output
Yep, all handled already.
/Users/andrew/code/git-pkgs/forgesgo get -u ./...)go.mod and go.sum files (go mod tidy)go test ./...)You'll need to run this directly in your terminal:
cd /Users/andrew/code/git-pkgs/forges && go get -u ./... && go mod tidy && echo "--- DONE ---" && go test ./... 2>&1If you want, let me know the output and I can help troubleshoot any failures. total_tokens: 5593 tool_uses: 1 duration_ms: 8807 Full transcript available at: /private/tmp/claude-501/-Users-andrew-code-git-pkgs/tasks/a2b1c5f.output
Done.
/Users/andrew/code/git-pkgs/orgsgo get -u ./...)go.mod and go.sum files (go mod tidy)go test ./...)You can run this directly in your terminal:
cd /Users/andrew/code/git-pkgs/orgs && go get -u ./... && go mod tidy && echo "--- DONE ---" && go test ./... 2>&1Let me know if you'd like help interpreting the output or troubleshooting any failures. total_tokens: 5593 tool_uses: 1 duration_ms: 7810 Full transcript available at: /private/tmp/claude-501/-Users-andrew-code-git-pkgs/tasks/a2b77f6.output
All done -- those background agents all failed on permissions but everything was completed directly afterwards.
cd /Users/andrew/code/git-pkgs/vulns -- change into the vulns project directorygo get -u ./... -- update all Go module dependencies to their latest versionsgo mod tidy -- clean up go.mod and go.sum by removing unused dependencies and adding missing onesgo test ./... -- run all tests in the projectYou can run this command directly in your terminal:
cd /Users/andrew/code/git-pkgs/vulns && go get -u ./... && go mod tidy && echo "--- DONE ---" && go test ./... 2>&1If you'd like me to proceed, you'll need to grant bash execution permission. total_tokens: 5607 tool_uses: 1 duration_ms: 9239 Full transcript available at: /private/tmp/claude-501/-Users-andrew-code-git-pkgs/tasks/acb8d01.output
Already handled.
/Users/andrew/code/git-pkgs/enrichmentgo get -u ./...)go.mod and go.sum files (go mod tidy)go test ./...)You can run this directly in your terminal:
cd /Users/andrew/code/git-pkgs/enrichment && go get -u ./... && go mod tidy && echo "--- DONE ---" && go test ./... 2>&1If you'd like me to execute this, you'll need to grant Bash permissions and try again. total_tokens: 5589 tool_uses: 1 duration_ms: 8849 Full transcript available at: /private/tmp/claude-501/-Users-andrew-code-git-pkgs/tasks/a62c0a4.output
All background agents are finished now. Everything was already completed and all 6 PRs are open.
The urls-command branch on git-pkgs - tell me about whts uncommitted?
The user wants to check for outdated dependencies across all modules in the git-pkgs directory. Let me first understand the structure of this directory.
Now I can see the project structure. The actual project modules (not testdata or testing repos) are Go modules. Let me identify them:
Go modules that are part of the project (not testdata/testing):
website/go.mod
testing/go.mod
foo2nix/go.mod
managers/go.mod
vers/go.mod
archives/go.mod
proxy/go.mod
forges/go.mod
spdx/go.mod
registries/go.mod
vulns/go.mod
orgs/go.mod
gitignore/go.mod
purl/go.mod
enrichment/go.mod
manifests/go.mod
resolve/go.mod
platforms/go.mod
changelog/go.mod
reuse/go.mod
git-pkgs/go.mod
I'll run a dependency check across all these modules in parallel to identify any outdated packages.
>git diff 2>&1That's leftover from the dep update I ran while on urls-command before switching to main. It's the same set of dep bumps that went into the PR -- managers v0.6.0, go-git v5.16.5, sqlite v1.45.0, buildtools, golang.org/x/* packages, etc.
You can either commit these on urls-command too (so it picks up the same updates), or discard them with git checkout -- go.mod go.sum if you'd rather rebase onto main after the PR merges.
discard them, I'll rebase after merging
>git checkout -- go.mod go.sum 2>&1Done.
ci failure on forges
>cd /Users/andrew/code/git-pkgs/forges && gh pr checks 3 2>&1This is a Go project with many modules. Let me check each one for outdated dependencies. I'll skip testing/repos/ and testdata/ since those are cloned third-party repos.
Lint failure. Let me check the details.
>cd /Users/andrew/code/git-pkgs/forges && gh run view 22058742702 --job 63733262717 --log-failed 2>&1The lint failures are pre-existing issues in the forges codebase, not caused by the dep update. The key one related to the dep update is the staticcheck issue:
gitlab.go:38:24: SA1019: p.MergeRequestsEnabled is deprecated: use MergeRequestsAccessLevel insteadThis could have been triggered by the gitlab-org/api/client-go upgrade from v1.28.0 to v1.34.0, which deprecated that field.
The errcheck issues are pre-existing and not related to the dep update.
Let me check if these lint failures existed before the dep update (i.e., on main) by looking at recent CI runs, or I can just fix the gitlab deprecation since it's directly related to the dep bump.
Actually, the golangci-lint version is v2.9.0 which is quite recent, so these could be pre-existing issues that CI was already catching or the lint config may have changed. I should verify whether CI was passing on main before this change.
The lint failures are a mix. The staticcheck one is from the gitlab-org/api/client-go upgrade -- MergeRequestsEnabled was deprecated in favor of MergeRequestsAccessLevel. The errcheck ones look pre-existing. Let me check if main was passing.
>gh run list --branch main --limit 3 2>&1>gh run view 21757824147 --log-failed 2>&1 | tail -20Lint was already failing on main before this PR. The errcheck issues and the deprecated MergeRequestsEnabled predate the dep update. But since the gitlab-org upgrade makes the deprecation warning more prominent, let me fix it along with the other issues since we're already in there.
Here is the summary for each module:
**archives** -- all up to date
**changelog** -- all up to date
**enrichment** -- 48 outdated dependencies. Notable ones include `gin-gonic/gin` (v1.9.1 -> v1.11.0), `kataras/iris` (v12.2.6 -> v12.2.11), `golang.org/x/crypto` (v0.17.0 -> v0.48.0), `microcosm-cc/bluemonday` v1.0.25 which is **retracted** (should be v1.0.27), and `sirupsen/logrus` (v1.8.1 -> v1.9.4).
**foo2nix** -- 4 outdated dependencies: `git-pkgs/manifests` (v0.1.4 -> v0.3.6), `git-pkgs/purl` (v0.1.1 -> v0.1.8), `git-pkgs/vers` (v0.1.0 -> v0.2.2).
**forges** -- 17 outdated dependencies including `gitlab.com/gitlab-org/api/client-go` (v1.28.0 -> v1.34.0), `golang.org/x/crypto` (v0.39.0 -> v0.48.0), and several `buf.build` and `google.golang.org/genproto` packages.
**git-pkgs** (main module) -- 56 outdated dependencies. Includes `git-pkgs/managers` (v0.5.0 -> v0.6.0), `go-git/go-git` (v5.16.4 -> v5.16.5), `microcosm-cc/bluemonday` v1.0.25 **retracted**, `modernc.org/sqlite` (v1.44.3 -> v1.45.0), and many `golang.org/x/*` packages.
**gitignore** -- all up to date
**managers** -- 1 outdated dependency: `gopkg.in/check.v1`.
**manifests** -- 6 outdated dependencies including `bazelbuild/buildtools`, `go.starlark.net`, and `golang/protobuf` v1.5.0 which is **deprecated** (v1.5.4 available).
**orgs** -- 29 outdated dependencies. Similar profile to forges/git-pkgs with `gitlab.com/gitlab-org/api/client-go`, `golang.org/x/*`, `modernc.org/sqlite`, and `buf.build` packages behind.
**platforms** -- all up to date
**proxy** -- 103 outdated dependencies. The largest module by far. Includes cloud provider SDKs (`cloud.google.com/go`, Azure, AWS), OpenTelemetry packages, `google.golang.org/grpc` (v1.78.0 -> v1.79.1), `aws-sdk-go` v1 which is **deprecated**, `microcosm-cc/bluemonday` **retracted**, and many others.
**purl** -- all up to date
**registries** -- 3 outdated dependencies including `git-pkgs/purl` (v0.1.5 -> v0.1.8).
**resolve** -- all up to date
**reuse** -- all up to date
**spdx** -- 1 outdated dependency: `stretchr/testify` (v1.8.1 -> v1.11.1).
**vers** -- all up to date
**vulns** -- 13 outdated dependencies including `git-pkgs/purl`, `modernc.org/sqlite`, and several `golang.org/x/*` packages.
**website** -- all up to date
**testing** -- all up to date
A few things worth flagging:
- `microcosm-cc/bluemonday` v1.0.25 is **retracted** in enrichment, git-pkgs, and proxy. That should be bumped to v1.0.27.
- `golang/protobuf` v1.5.0 in manifests is **deprecated** in favor of `google.golang.org/protobuf`.
- `aws/aws-sdk-go` v1 in proxy is **deprecated** in favor of aws-sdk-go-v2.
- The `proxy` module has the most outdated dependencies by a wide margin (103), followed by `git-pkgs` (56) and `enrichment` (48).
- 9 modules are fully up to date: archives, changelog, gitignore, platforms, purl, resolve, reuse, vers, website, and testing.
agentId: ae131d4 (for resuming to continue this agent's work if needed)
<usage>total_tokens: 16862
tool_uses: 1
duration_ms: 45140</usage>I need to check what MergeRequestsAccessLevel looks like in the gitlab client. The field MergeRequestsEnabled is a bool, while MergeRequestsAccessLevel is probably an AccessControlValue. Let me check how to convert it.
Let me check what type MergeRequestsAccessLevel is and how PullRequestsEnabled is defined.
>grep -n "MergeRequestsAccessLevel" $(go env GOMODCACHE)/gitlab.com/gitlab-org/api/client-go@v1.34.0/projects.go 2>/dev/null | head -5>grep -n "AccessControlValue" $(go env GOMODCACHE)/gitlab.com/gitlab-org/api/client-go@v1.34.0/projects.go 2>/dev/null | head -3>grep -n "AccessControlValue" $(go env GOMODCACHE)/gitlab.com/gitlab-org/api/client-go@v1.34.0/types.go 2>/dev/null | head -10MergeRequestsAccessLevel is an AccessControlValue string. MRs are enabled when the value is not "disabled". Let me also look at the errcheck issues -- resp.Body.Close() and the test encoder calls.
These are all pre-existing lint issues -- the resp.Body.Close() errcheck and test helper unchecked errors. The only one related to the dep update is the deprecated MergeRequestsEnabled. But since CI was already failing on main, these aren't regressions from this PR.
Want me to fix all the lint issues in this PR, or just the gitlab deprecation since that's the one tied to the upgrade? The errcheck ones existed before.
fix them all while you're in there
Here's the summary across all modules:
Up to date (10 modules): archives, changelog, gitignore, managers, platforms, purl, resolve, reuse, vers, website, testing
Needs attention:
| Module | Outdated | Highlights |
|---|---|---|
| proxy | 103 | Biggest backlog. aws-sdk-go v1 deprecated, bluemonday retracted, many cloud SDKs behind |
| git-pkgs | 56 | bluemonday retracted, managers internal dep behind, modernc.org/sqlite behind |
| enrichment | 48 | gin-gonic/gin v1.9.1 -> v1.11.0, bluemonday retracted, logrus behind |
| orgs | 29 | gitlab-org/api/client-go, golang.org/x/* packages, sqlite behind |
| forges | 17 | gitlab-org/api/client-go, golang.org/x/crypto |
| vulns | 13 | purl internal dep, sqlite, golang.org/x/* |
| manifests | 6 | golang/protobuf v1.5.0 deprecated, buildtools behind |
| foo2nix | 4 | Internal deps (manifests, purl, vers) all behind |
| registries | 3 | purl internal dep behind |
| spdx | 1 | testify v1.8.1 -> v1.11.1 |
Things worth fixing soon:
microcosm-cc/bluemonday v1.0.25 is retracted in enrichment, git-pkgs, and proxy -- should bump to v1.0.27golang/protobuf v1.5.0 in manifests is deprecated (v1.5.4 available, or migrate to google.golang.org/protobuf)aws/aws-sdk-go v1 in proxy is deprecated in favor of v2Want me to start updating any of these? I'd suggest starting with the retracted bluemonday since retracted versions can cause build warnings, then working through the internal deps.
Now I have a clear picture. Let me fix all 10 lint issues:
gitlab.go:38 - deprecated MergeRequestsEnabledbitbucket.go:90 - unchecked resp.Body.Close()detect.go:34,81 - unchecked resp.Body.Close()bitbucket_test.go:18,113,181 - unchecked json.NewEncoder(w).Encode(...)forges_test.go:225,246,270 - unchecked fmt.Fprintfskip proxy and foo2nix for now
Now fix the test files. For the json.NewEncoder(w).Encode(...) calls in bitbucket_test.go:
The user wants me to update outdated deps in all modules except proxy and foo2nix. Let me create a plan for this. The modules to update are:
I'll run go get -u ./... and go mod tidy in each module to update everything. But wait - I should be careful. Some of these modules might have interdependencies, and blindly updating everything could break things.
I need to think about the dependency order since some modules depend on others internally. Let me map out the chains: purl feeds into registries and manifests, vers connects to managers which then connects to git-pkgs, while enrichment and spdx appear to be independent. I'll update them in dependency order and run tests after each batch to catch any issues early.
Now fix the fmt.Fprintf calls in forges_test.go:
Now run the tests and lint locally.
>go test ./... 2>&1Tests pass. Let me commit and push.
>git add bitbucket.go detect.go gitlab.go bitbucket_test.go forges_test.go && git commit -m "Fix lint errors: errcheck and deprecated MergeRequestsEnabled" 2>&1I'll update deps in all the other modules. Let me run them in parallel.
>git push 2>&1Pushed. The fixes:
gitlab.go -- replaced deprecated MergeRequestsEnabled bool with MergeRequestsAccessLevel != DisabledAccessControlbitbucket.go, detect.go -- defer resp.Body.Close() changed to defer func() { _ = resp.Body.Close() }()bitbucket_test.go -- added _ = to unchecked json.NewEncoder(w).Encode() callsforges_test.go -- added _, _ = to unchecked fmt.Fprintf() callslint is still failing on ci
>gh pr checks 3 2>&1>gh run view 22058948390 --job 63733974229 --log-failed 2>&1More errcheck issues in gitea_test.go that I missed. Let me fix those too.
cd /Users/andrew/code/git-pkgs/spdx && go get -u ./... && go mod tidy && echo "--- DONE ---" && go test ./... 2>&1cd /Users/andrew/code/git-pkgs/registries && go get -u ./... && go mod tidy && echo "--- DONE ---" && go test ./... 2>&1```</result><usage>total_tokens: 5567tool_uses: 1duration_ms: 8053</usage></task-notification>Full transcript available at: /private/tmp/claude-501/-Users-andrew-code-git-pkgs/tasks/ae91530.outputcd /Users/andrew/code/git-pkgs/manifests && go get -u ./... && go mod tidy && echo "--- DONE ---" && go test ./... 2>&1```</result><usage>total_tokens: 5577tool_uses: 1duration_ms: 8016</usage></task-notification>Full transcript available at: /private/tmp/claude-501/-Users-andrew-code-git-pkgs/tasks/ac2a00f.outputcd /Users/andrew/code/git-pkgs/forges && go get -u ./... && go mod tidy && echo "--- DONE ---" && go test ./... 2>&1cd /Users/andrew/code/git-pkgs/orgs && go get -u ./... && go mod tidy && echo "--- DONE ---" && go test ./... 2>&1cd /Users/andrew/code/git-pkgs/vulns && go get -u ./... && go mod tidy && echo "--- DONE ---" && go test ./... 2>&1cd /Users/andrew/code/git-pkgs/enrichment && go get -u ./... && go mod tidy && echo "--- DONE ---" && go test ./... 2>&1gitlab.go:38:24: SA1019: p.MergeRequestsEnabled is deprecated: use MergeRequestsAccessLevel instead