Skip to content

docs: point download links at v0.2.0 - #94

Merged
oesukam merged 1 commit into
mainfrom
docs/latest-download-links
Aug 4, 2026
Merged

docs: point download links at v0.2.0#94
oesukam merged 1 commit into
mainfrom
docs/latest-download-links

Conversation

@oesukam

@oesukam oesukam commented Aug 4, 2026

Copy link
Copy Markdown
Collaborator

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 workflow scope) makes this sync automatic on every future release so the links can't go stale again.

@oesukam
oesukam merged commit 3b93ed4 into main Aug 4, 2026
6 checks passed
@oesukam
oesukam deleted the docs/latest-download-links branch August 4, 2026 22:56
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.
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