docs: add release badge and fix BCR install version to 0.4.1 - #24
Merged
Merged
Conversation
rules_odin is now published on the Bazel Central Registry (rules_odin@0.4.1, BCR PR bazelbuild/bazel-central-registry#9769). Update the README to reflect first publication: - Add an auto-updating github/v/release badge linking to the latest release, so the advertised version never goes stale. - Fix the Quick Start install snippet, which pinned a never-published version (0.1.0), to the actual published version 0.4.1. - Note that rules_odin is on the BCR and link the module page plus the latest release for discovering newer versions, following the convention used by peer rulesets (aspect bazel-lib, rules_go/rust/python).
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.
What does this PR do?
rules_odinis now published on the Bazel Central Registry —rules_odin@0.4.1(BCR PR bazelbuild/bazel-central-registry#9769, merged byfmeumon 2026-07-26). This updates the README to reflect first publication:github/v/releaseshields badge linking to the latest release, so the advertised version never goes stale.version = "0.1.0", a version that was never published. Corrected to the actual published version0.4.1(real copy-paste bug for anyone following the README).rules_odinis on the Bazel Central Registry and link the module page + latest release for discovering newer versions, following the convention used by peer rulesets (aspect bazel-lib, rules_go/rust/python).Docs-only; no rule/toolchain behavior changes.
How was it tested?
pre-commit run --files README.md— all hooks pass (prettier made no changes; trailing-whitespace, end-of-file-fixer, typos all green).releases/latest→ HTTP 302 (works);github/v/releaseshields badge → HTTP 200. The canonical BCR module page is still propagating (CDN lag right after merge); the badge and primary "latest release" link both target the working GitHub releases page, so no badge is broken.check.yaml) will verify on this PR.Checklist
check.yaml— lint + test matrix)