Bulk dependency updates (Renovate) #8
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/renovate-update-bulk"
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?
Consolidates 6 open Renovate PRs into one branch, applied and verified in order (Go deps, then Dockerfile bumps, then CI-only bumps):
Incorporated:
feat(deps): update module github.com/prometheus/client_golang v1.23.2 -> v1.24.1feat(deps): update opentelemetry-go monorepo v1.43.0 -> v1.46.0(had a go.mod/go.sum conflict with #3, resolved by combining both bumps; followed bygo mod tidyto reconcile go.sum, committed separately)feat(container): update image docker.io/library/golang 1.25 -> 1.27(builder stage)feat(container): update image docker.io/library/alpine 3.20 -> 3.24(final stage) -- verified both Dockerfile base images landed correctly without clobbering each otherci(github-action)!: Update action actions/checkout v4.4.0 -> v7.0.1(MAJOR)ci(github-action)!: Update action actions/setup-go v4.3.0 -> v7.0.0(MAJOR)Left out: none -- all 6 open Renovate PRs are incorporated.
Verification performed:
go build ./...andgo vet ./...clean after the prometheus/otel dependency bumps, and again after all commits landedgo mod tidyrun to reconcile go.sum after combining the two dependency bumps (dropped one now-unneeded indirect entry).forgejo/workflows/*.ymlstill parse as valid YAML after the actions/checkout and actions/setup-go major bumps, and that all action references consistently point to the new major versionsgo build ./...,go vet ./...,go test ./...all pass (this module has no CGO dependencies, so noCGO_ENABLED=1was needed)Once merged, the original #1, #2, #3, #4, #6, #7 branches/PRs can be closed.
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.