Skip to content

docs: sync docs-versioning policy and clarify compatibility baseline#25

Merged
PythonWoods-Dev merged 5 commits intomainfrom
fix/v0.5.0a1-docs-version-sync
Apr 2, 2026
Merged

docs: sync docs-versioning policy and clarify compatibility baseline#25
PythonWoods-Dev merged 5 commits intomainfrom
fix/v0.5.0a1-docs-version-sync

Conversation

@PythonWoods-Dev
Copy link
Copy Markdown
Contributor

Description:
This PR finalizes documentation consistency after v0.5.0a1 release.

What’s included:

Docs topbar version anti-drift:
mkdocs.yml now reads version from DOCS_VERSION env (fallback dev).
deploy-docs.yml sets DOCS_VERSION from pyproject.toml.
Production Cloudflare deploy is now restricted to main only, preventing docs from getting ahead of merged code/release state.
Ownership/attribution clarity:
Added explicit attribution that Zenzic is a PythonWoods project.
Clarified that Zensical, MkDocs, and other ecosystem tools are third-party projects.
Applied in NOTICE, README (EN/IT), and About pages (EN/IT).
Compatibility wording:
Declared explicit baseline as Zensical v0.0.31+ in README (EN/IT).
Why v0.0.31+:

It reflects the minimum supported baseline rather than a single pinned patch.
It matches migration/config docs already referencing Zensical v0.0.31+.
It avoids unnecessary documentation churn for compatible patch/minor updates.
Validation:

markdownlint passed for updated README files.
workflow YAML checks passed.
mkdocs build --strict passed.
pre-commit hooks passed during commits.

@PythonWoods-Dev PythonWoods-Dev merged commit f82a461 into main Apr 2, 2026
9 checks passed
@PythonWoods-Dev PythonWoods-Dev deleted the fix/v0.5.0a1-docs-version-sync branch April 3, 2026 10:38
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