Skip to content

docs(release): require the latest log tag in every otel release - #54

Merged
josuegiron merged 1 commit into
masterfrom
docs/release-otel-requires-latest-log
Nov 21, 2026
Merged

josuegiron merged 1 commit into
masterfrom
docs/release-otel-requires-latest-log

Conversation

@josuegiron

Copy link
Copy Markdown
Member

What

Adds a release-order rule to RELEASE.md: release errors → log → otel, and every otel/vX.Y.Z raises otel/go.mod's github.com/jgolang/log requirement to the latest log tag.

Why

The same slip happened twice: otel/v1.6.0 required log v1.5.0 when v1.6.0 was about to ship, and otel/v1.8.0 required log v1.7.1 while v1.7.2 existed (epic-assessment retrospective finding 4; epic-licenses-process-hygiene retrospective finding 3). Today otel/v1.8.0 still pulls errors v0.6.1 and go-errors into users' graphs, although log v1.7.4 dropped them.

Tests

Docs only; no code changed, so no tests.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@josuegiron
josuegiron merged commit ea5f130 into master Nov 21, 2026
2 checks passed
@josuegiron
josuegiron deleted the docs/release-otel-requires-latest-log branch November 21, 2026 19:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant