-
Notifications
You must be signed in to change notification settings - Fork 77
Open
Description
The chainsaw documentation site's /latest/ URL currently redirects to v0.2.3, but the current release is v0.2.13.
Root Cause:
The docs deployment workflow (.github/workflows/docs-release.yaml) only triggers on docs-v* tags. While release tags exist up to v0.2.13, documentation tags only exist up to docs-v0.2.3.
Evidence:
Latest release tag:
$ git tag -l "v*" | grep -E "v0\.2\.[0-9]+$" | sort -V | tail -1
v0.2.13
But docs tags are missing:
$ git tag -l "docs-v*" | sort -V | tail -1
docs-v0.2.3
Solution:
Create missing documentation tags from docs-v0.2.4 through docs-v0.2.13 to bring docs in sync with releases.
Impact:
Users visiting https://kyverno.github.io/chainsaw/latest/ see outdated documentation that's 10 versions behind.
I'd like to take this on as my first contribution to Chainsaw. Could a maintainer clarify:
- Should I create all missing docs-v* tags (0.2.4 through 0.2.13) or just the latest docs-v0.2.13?
- Do I have permission to push tags, or does a maintainer need to handle the tagging?
thanks!
Metadata
Metadata
Assignees
Labels
No labels