docs: point download links at v0.2.0 - #94
Merged
Merged
Conversation
oesukam
added a commit
that referenced
this pull request
Aug 4, 2026
…lease (#95) ## Summary Two related release-pipeline changes now that releases are cut manually. ### Remove the nightly prerelease - Delete `.github/workflows/prerelease.yml` (the entire rolling-nightly workflow — no longer needed with manual releases). - Drop the now-dead "Cancel in-flight nightlies" step and its `actions: write` permission from `release.yml`. - Clean stale nightly references in `cliff.toml` (comment + `skip_tags`) and `docs/release-signing.md`. ### Auto-sync docs download links every release The docs landing pages hardcode the release version in their direct download URLs. That sync was bundled inside the `Bump version (when provided)` step, gated on the manual `version` input — so a release cut **without** typing a version skipped the docs update, leaving the links stale (exactly what happened at v0.2.0). - Split the docs-link rewrite into its own step that **always runs**, driven by the resolved release version (not the manual input). - Reads the docs' current version from the `**vX.Y.Z**` marker, rewrites EN + FR links, and commits only when something changed (safe on re-runs). The one-off v0.2.0 doc content sync is in #94; this PR prevents the staleness recurring. ## Note - The Release workflow still tags `v<version>` automatically (via the Releases API) — unchanged. - `release.yml`'s version-bump and this new docs-sync step both `git push origin HEAD:main`. If `main` gets a 'require PR before merge' rule, these need an Actions exemption or a rework to open a PR.
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
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.
The landing-page download grid (EN + FR) still pointed at v0.1.0 assets after the v0.2.0 release. Updates every direct download link and the "Latest release" / "Dernière version" marker to v0.2.0.
A companion workflow change (separate PR, needs
workflowscope) makes this sync automatic on every future release so the links can't go stale again.