From dc121135666b59d8fd6197504422d1421fc92e8c Mon Sep 17 00:00:00 2001 From: Josue Giron Date: Sat, 21 Nov 2026 19:50:04 +0000 Subject: [PATCH] docs(release): require the latest log tag in every otel release Co-Authored-By: Claude Opus 5.5 --- RELEASE.md | 1 + 1 file changed, 1 insertion(+) diff --git a/RELEASE.md b/RELEASE.md index 4ff9dd3..09ab415 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -11,4 +11,5 @@ Before tagging a release: Tags: - The root module is tagged `vX.Y.Z`; the `otel` module is tagged `otel/vX.Y.Z`. +- Release in dependency order: `errors`, then `log`, then `otel`. Before every `otel/vX.Y.Z` tag, raise `github.com/jgolang/log` in `otel/go.mod` to the latest `log` tag (its `errors` requirement follows), even when `otel` does not need the new code: otherwise `otel` users keep an older `log` and `errors`, and dependencies those releases dropped, in their module graph. - Do not run `go mod tidy` in `otel/` expecting it to drop `github.com/jgolang/log`: `otel` imports it on purpose so `log/otel` raises `log` past v1.4.x (where `otel` was part of the root module) and avoids an ambiguous import.