chore: update dependencies #1
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/update-dependencies"
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?
Updates Go module dependencies, the Go toolchain requirement, and release actions.
Verification: go test ./..., go vet ./..., go mod verify, build, and OpenTofu validate. golangci-lint reports existing errcheck and unused issues.
Clean at
988dbd7— no blocking findings.Verified rather than assumed, since a dependency bump is exactly where a bad hash or an unexecutable action hides:
sum.golang.org/lookup), and everyrequirein go.mod has both itsh1and/go.modentries. The otel / go-logr / xxhash / google-uuid lines dropped are content hashes of modules no imported package reaches; nothing in the build list lost a hash.<=the versions selected here (plugin-go 0.31.0, exec 0.26.0, json 0.29.0, sdk 2.40.1, crypto 0.58.0), so the bump is internally consistent and no indirect requirement is under-satisfied.resource.Test,TestCase.ProtoV6ProviderFactories,TestStep,ComposeAggregateTestCheckFunc,TestCheckResourceAttr{,Set}.go1.26.10andgo1.26.0are both real releases (go.dev/dl), so.tool-versionsand thegodirective resolve.code.forgejo.org/actions/{checkout,setup-go}@v7exist, and both declareruns.using: node24— supported by this instance's runner (forgejo-runner v12.7.2), so the release job will resolve them.One thing to know rather than fix: this repo has no CI workflow (0 action runs on the instance), so the tag-triggered release is the first place the action bumps get exercised.
Nothing to fix.
View command line instructions
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.