6f85f378ff
## What this PR does Updates the `update-website-docs` job in `.github/workflows/tags.yaml` to match the new docs-versioning contract introduced in cozystack/website#495. The website repo replaces the old "pre-create `vX.Y/` draft directory" scheme with a permanent `content/en/docs/next/` trunk. Released version directories are no longer implicitly pre-created — the upstream release workflow owns the explicit decision of when to promote `next/` → `vX.Y/`. ### Changes - **New step `Determine if this release promotes next/`** — parses the tag and only sets `promote=true` for final `vX.Y.Z` tags where `content/en/docs/vX.Y/` does not already exist. Prereleases (`vX.Y.Z-rc.N`, etc.) and patch releases skip promotion. - **New step `Promote next/ to released version`** — gated on `promote=true`; runs `make release-next RELEASE_TAG=<tag>`. - **Step order**: `release-next` runs **before** `update-all`. This way `update-all` routes into the freshly-created `vX.Y/` directory (per the website Makefile's routing logic), and `next/` stays untouched as the trunk for the following release. - **`git add content hugo.yaml`** — `release-next` registers the new version in `hugo.yaml` via `register_version.sh`, so the commit step must stage it. - Converted the existing `update-all` step to use `env:` vars for consistency with the new step and workflow-injection hardening. ### Behaviour by tag | Tag | `release-next`? | `update-all` targets | |-----|-----------------|----------------------| | `v1.3.0` (v1.3 does not exist) | yes — promotes next/ → v1.3/ | v1.3/ | | `v1.3.1` (v1.3 exists) | no — skipped | v1.3/ | | `v1.3.0-rc.1` | no — skipped (prerelease) | next/ | | `v2.0.0` (v2.0 does not exist) | yes — promotes next/ → v2.0/ | v2.0/ | ### Release note ```release-note Release tagging now promotes the website's `next/` docs trunk to `vX.Y/` when cutting a new minor or major release (requires cozystack/website#495 to be merged first). ``` ### Dependency Must not merge until cozystack/website#495 is merged on `main` of the website repo, otherwise `make release-next` won't exist there and new-minor release tags will fail. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Chores** * Updated release automation to apply conditional logic for version promotion based on tag patterns and documentation availability. Modified documentation staging behavior in release workflows. <!-- end of auto-generated comment: release notes by coderabbit.ai --> |
||
|---|---|---|
| .. | ||
| ISSUE_TEMPLATE | ||
| workflows | ||
| CODEOWNERS | ||
| PULL_REQUEST_TEMPLATE.md | ||