fix(docs): sync topbar version and bumpversion metadata to v0.5.0a1#24
Merged
PythonWoods-Dev merged 3 commits intomainfrom Apr 2, 2026
Merged
fix(docs): sync topbar version and bumpversion metadata to v0.5.0a1#24PythonWoods-Dev merged 3 commits intomainfrom
PythonWoods-Dev merged 3 commits intomainfrom
Conversation
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.
Summary
This PR fixes a version-display mismatch after publishing v0.5.0a1.
The package version was correctly published as 0.5.0a1, but documentation metadata still showed an older value in the topbar and release tooling metadata was not aligned.
Changes
Updated docs topbar version metadata in mkdocs.yml to 0.5.0a1.
Updated release tooling baseline in pyproject.toml:
[tool.bumpversion].current_version = "0.5.0a1"
Why this PR
Keep user-facing docs consistent with the actually published package version.
Avoid confusion during release validation and communication.
Ensure future version bump operations start from the correct baseline.
Scope
Metadata/documentation consistency only.
No runtime code changes.
No package behavior changes.
Validation
Pre-commit checks passed during commit.
Documentation build remains valid with strict mode locally.
Release impact
No need for a new package release (0.5.1a1 is not required).
Existing published 0.5.0a1 remains valid; this PR aligns docs and tooling metadata with it.