Skip to content

Retire the zap, zerolog and clog logger modules - #108

Merged
duynhne merged 1 commit into
mainfrom
chore/retire-zap-loggers
Sep 24, 2026
Merged

duynhne merged 1 commit into
mainfrom
chore/retire-zap-loggers

Conversation

@duynhne

@duynhne duynhne commented Sep 24, 2026

Copy link
Copy Markdown
Contributor

What

RFC-0031 Task 1.1b. The fleet finished moving to logger/slogx in Phase 3 (user v2.3.0 … checkout v0.11.0; no service go.mod requires logger/zapx any more), so the three backend modules have no consumer:

  • logger/zapx (last tag v0.36.1), logger/zerolog and logger/clog (last tag v0.36.2 each) are removed from the tree. Published tags keep resolving through the module proxy.
  • README / AGENTS: 15 → 12 modules, examples point at logger/slogx, a "Retired" note under the module table.
  • Migration docs marked historical; label and comments updated.

No code in any remaining module imported them (no cross-module deps), so nothing else changes.

🤖 Generated with Claude Code

https://claude.ai/code/session_018N7ME8TyWS33cbpWV3v8E8

Every service now logs through logger/slogx, so the three backend
modules have no consumer. Their published tags still resolve through
the module proxy; nothing new is released from them. The repo drops
from 15 to 12 modules.
@sonarqubecloud

Copy link
Copy Markdown

@duynhne
duynhne merged commit 79bf141 into main Sep 24, 2026
11 checks passed
@duynhne
duynhne deleted the chore/retire-zap-loggers branch September 24, 2026 06:02
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