[auto] PR for dependency update #18
No reviewers
Labels
No labels
Kind/Bug
bug
doc
duplicate
enhancement
help wanted
invalid
question
security
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
IUS/goca!18
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "ci"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR was created automatically by Jenkins
Review findings
Blocking: the dependency update is not tidy, so
go test ./...does not run. Go stops withgo: updates to go.mod needed; to update it: go mod tidy.go mod tidy -diffshowsgochanging from1.19to1.21.4and a missinggopkg.in/check.v1 ... /go.modchecksum ingo.sum. Tracked as #19.Blocking/process: Forgejo reports this PR as not mergeable, and the current branch diff against
masteris no longer justgo.mod/go.sumbecause the branch is very stale. Regenerate or rebase the dependency update before another review.Verification:
env GOMODCACHE=/tmp/goca-go-mod GOCACHE=/tmp/goca-go-build CCACHE_DIR=/tmp/goca-ccache go test ./...fails before tests run;env GOMODCACHE=/tmp/goca-go-mod GOCACHE=/tmp/goca-go-build CCACHE_DIR=/tmp/goca-ccache go mod tidy -diffconfirms the required module changes.(co)authored by ai:gpt-5-codex
Opus follow-up: this auto-PR appears superseded by master
The branch needs more than a tidy/rebase — master has already moved past it.
| field |
ci(PR head) |master|| ────────────────── | ─────────────── | ─────────────── |
|
godirective |1.19|1.21.5||
gitgo|v0.15.0|v0.17.0|Master commits that did this work in better form:
322578e7d2— go: update dependencies, especially to gitgo18d0310ffb— go: dependency updateThe Jenkins job that produced this PR last fired against an old base. Cleanest path is to close PR #18 and let the next Jenkins run open a fresh dep update against current master; #19's go-tidy concern then falls out automatically. (Not closing without confirmation.)
(co)authored by ai:claude-opus-4-7
View command line instructions
Manual merge helper
Use this merge commit message when completing the merge manually.
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.