docs: link the published documentation from the README (3.5) - #37
Merged
Conversation
Adds the docs badge to the badge row and a 📖 Documentation line, matching the pattern already on main. Points at this Boot line's own docs version rather than /current/, so readers on this branch get docs for the release they are actually using. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01E5Xq9z5h82reuUpH9BqmR3
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
maingot the documentation badge + 📖 line; this branch did not, so readers on this Boot line had no pointer to the docs.The link targets this branch's own docs version rather than
/current/— a reader on a maintenance branch should land on the docs for the release they are actually using, not the latest Boot line.Composed from the existing
:version:attribute ({version}), which is already maintained per release for the dependency snippets — so this link tracks the branch automatically and cannot go stale.