Repository navigation
docs(release): require the latest log tag in every otel release - #54
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
What
Adds a release-order rule to
RELEASE.md: releaseerrors→log→otel, and everyotel/vX.Y.Zraisesotel/go.mod'sgithub.com/jgolang/logrequirement 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.1andgo-errorsinto users' graphs, although log v1.7.4 dropped them.Tests
Docs only; no code changed, so no tests.
🤖 Generated with Claude Code