fix(deps): update opentelemetry-go monorepo - #27
Merged
Conversation
Contributor
Author
|
renovate
Bot
force-pushed
the
renovate/opentelemetry-go-monorepo
branch
2 times, most recently
from
January 24, 2025 07:21
6467e69 to
ba96f11
Compare
renovate
Bot
force-pushed
the
renovate/opentelemetry-go-monorepo
branch
3 times, most recently
from
March 5, 2025 22:35
8cd1d4f to
4be2430
Compare
renovate
Bot
force-pushed
the
renovate/opentelemetry-go-monorepo
branch
from
March 14, 2025 10:56
4be2430 to
943ce88
Compare
renovate
Bot
force-pushed
the
renovate/opentelemetry-go-monorepo
branch
from
April 16, 2025 15:10
943ce88 to
a332563
Compare
renovate
Bot
force-pushed
the
renovate/opentelemetry-go-monorepo
branch
2 times, most recently
from
April 28, 2025 13:05
28dc23f to
a46d5a8
Compare
renovate
Bot
force-pushed
the
renovate/opentelemetry-go-monorepo
branch
2 times, most recently
from
May 6, 2025 13:18
432f871 to
df78386
Compare
renovate
Bot
force-pushed
the
renovate/opentelemetry-go-monorepo
branch
5 times, most recently
from
May 25, 2025 21:55
563faec to
41e51b4
Compare
renovate
Bot
force-pushed
the
renovate/opentelemetry-go-monorepo
branch
2 times, most recently
from
June 13, 2025 21:04
05c0f61 to
09400ea
Compare
renovate
Bot
force-pushed
the
renovate/opentelemetry-go-monorepo
branch
2 times, most recently
from
June 25, 2025 08:17
f9f1fba to
ad43e0c
Compare
renovate
Bot
force-pushed
the
renovate/opentelemetry-go-monorepo
branch
5 times, most recently
from
July 10, 2025 10:30
17fe00c to
d451885
Compare
renovate
Bot
force-pushed
the
renovate/opentelemetry-go-monorepo
branch
4 times, most recently
from
July 12, 2025 21:00
22c13a2 to
436999e
Compare
renovate
Bot
force-pushed
the
renovate/opentelemetry-go-monorepo
branch
from
October 29, 2025 05:01
b1340c3 to
3019f72
Compare
renovate
Bot
force-pushed
the
renovate/opentelemetry-go-monorepo
branch
from
October 29, 2025 10:15
3019f72 to
5f80bd9
Compare
renovate
Bot
force-pushed
the
renovate/opentelemetry-go-monorepo
branch
from
November 29, 2025 16:59
5f80bd9 to
f61d7df
Compare
renovate
Bot
force-pushed
the
renovate/opentelemetry-go-monorepo
branch
from
December 8, 2025 20:18
f61d7df to
2fcfbd2
Compare
renovate
Bot
force-pushed
the
renovate/opentelemetry-go-monorepo
branch
from
December 13, 2025 13:45
2fcfbd2 to
3729d6d
Compare
renovate
Bot
force-pushed
the
renovate/opentelemetry-go-monorepo
branch
from
December 13, 2025 17:42
3729d6d to
07c6597
Compare
renovate
Bot
force-pushed
the
renovate/opentelemetry-go-monorepo
branch
from
December 15, 2025 17:07
07c6597 to
b95211f
Compare
renovate
Bot
force-pushed
the
renovate/opentelemetry-go-monorepo
branch
from
December 21, 2025 08:18
b95211f to
fae059a
Compare
renovate
Bot
force-pushed
the
renovate/opentelemetry-go-monorepo
branch
from
December 23, 2025 09:09
fae059a to
ec92df1
Compare
renovate
Bot
force-pushed
the
renovate/opentelemetry-go-monorepo
branch
from
December 23, 2025 12:59
ec92df1 to
1dae649
Compare
renovate
Bot
force-pushed
the
renovate/opentelemetry-go-monorepo
branch
from
February 2, 2026 21:13
1dae649 to
2453379
Compare
renovate
Bot
force-pushed
the
renovate/opentelemetry-go-monorepo
branch
from
February 12, 2026 11:36
2453379 to
6e91fe5
Compare
renovate
Bot
force-pushed
the
renovate/opentelemetry-go-monorepo
branch
from
February 17, 2026 09:23
6e91fe5 to
88ff23c
Compare
Contributor
Author
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
Renovate raised the whole opentelemetry-go monorepo, but the PR was broken in
two independent ways.
The reported one: the artifacts step failed, so no go.sum was updated and the
branch would have landed with go.mod and go.sum disagreeing across 28 modules.
`dagger functions` passed anyway, because `dagger develop` regenerates go.sum
inside the container -- CI green was never evidence the committed tree was
consistent.
The second is why this could not simply be rebased. Renovate also raised four
`replace` directives from v0.16.0 to v0.22.0:
replace go.opentelemetry.io/otel/log => go.opentelemetry.io/otel/log v0.22.0
replace go.opentelemetry.io/otel/sdk/log => ... v0.22.0
replace .../otlplog/otlploggrpc => ... v0.22.0
replace .../otlplog/otlploghttp => ... v0.22.0
Those are not stale versions. They are a deliberate pin written by the Dagger
SDK codegen, and github.com/dagger/otel-go v1.43.0 is built against them:
otel-go@v1.43.0/logging.go:47:63: undefined: log.KeyValue
otel-go@v1.43.0/transform.go:872:51: undefined: log.Value
v0.22.0 removed those types, so the bump fails to compile in every module that
imports the generated client -- which is all of them. Renovate cannot
distinguish a deliberate `replace` pin from an outdated dependency.
Isolated the two halves rather than assuming: with the core at v1.46.0 and the
replace directives left at v0.16.0, the tree builds. So the core bump is kept
and the pins are restored.
`renovate.json` now disables updates for those four packages, with the reason
recorded inline, so this PR does not get recreated.
Reapplied on top of #72 and #306 rather than rebased: those two touched the
same `require` blocks in all 28 go.mod files, and resolving 28 conflicts in
generated files by hand is not something to trust. The upstream change is
three direct requires plus four replace lines, so it was reapplied mechanically
and everything else regenerated. Verified gookit/validate v1.6.0 (#72) and
gqlparser v2.5.37 (#306) both survive.
Verified: `go mod tidy`, `go build` and `go vet` pass in all 28 modules.
`dagger functions` spot-checked on kcl, go, ansible, hugo and docker. `dagger
develop` on kcl leaves otel at v1.46.0 and the replaces at v0.16.0, so the fix
survives regeneration.
Note for the govulncheck backlog: grpc stays at v1.79.3 (indirect), so
GO-2026-6061 is not addressed here.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01A4HsKKvk5TF1vypsJPqV76
|
🎉 This PR is included in version 0.128.4 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This was referenced Sep 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.44.0→v1.46.0v1.43.0→v1.46.0v0.16.0→v0.22.0v0.16.0→v0.22.0v0.16.0→v0.22.0v1.43.0→v1.46.0v0.16.0→v0.22.0v1.44.0→v1.46.0v1.43.0→v1.46.0Release Notes
open-telemetry/opentelemetry-go (go.opentelemetry.io/otel)
v1.46.0Compare Source
v1.45.0Compare Source
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.