docs: point Go Reference badges at /v2 import path#84
Merged
Conversation
The README header and the docs site's nav both linked the Go Reference badge to `pkg.go.dev/go.loglayer.dev` (no /v2 suffix). pkg.go.dev serves whatever the latest tag at that import path is, which is v1.7.0 (the last v1 release before the v2 cascade). The badge therefore showed v1.7.0 even though the live module path is `go.loglayer.dev/v2` and the latest release is v2.1.0. Append `/v2` to both the badge image URL and the click-through link in README.md and docs/.vitepress/config.ts so the badge resolves to the v2 module's pkg.go.dev page. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Same fix as the root README: every sub-module README's Go Reference
badge URL was missing the `/v2` suffix on both the badge image and
the click-through link, so pkg.go.dev served the v1 (pre-major-bump)
version of each module.
Twelve READMEs updated:
- transports/{charmlog,datadog,http,logrus,lumberjack,otellog,phuslu,pretty,sentry,zap,zerolog}/README.md
- plugins/oteltrace/README.md
The other sub-modules (transports/blank, transports/cli,
transports/console, transports/structured, transports/testing,
transports/slog, transports/central, transports/gcplogging,
plugins/{datadogtrace,fmtlog,plugintest,redact,sampling}) don't
ship per-package READMEs; their badges in the docs site's
transport-list / plugin-list partials already use /v2 correctly.
Co-Authored-By: Claude Opus 4.7 (1M context) <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
1 participant
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.
The README and the docs site's nav both linked the Go Reference badge to
pkg.go.dev/go.loglayer.dev(no/v2). pkg.go.dev shows the latest tag at that import path, which isv1.7.0(the last v1 release before the v2 cascade). The badge therefore showedv1.7.0even though the live module path isgo.loglayer.dev/v2and the latest release isv2.1.0.Two commits
/v2.plugins/oteltrace) get the same fix. The eight other sub-modules don't ship per-package READMEs; their badges in the docs site'stransport-list.mdandplugin-list.mdpartials already use/v2correctly.Verification
cd docs && bun run docs:buildclean (verified before each push).🤖 Generated with Claude Code