From 20636904a538d4a7885981f97ebbaf1fd50d6b86 Mon Sep 17 00:00:00 2001 From: Damir Vazgird Date: Sat, 3 Oct 2026 22:23:02 -0700 Subject: [PATCH] docs: bump the herdr plugin manifest with each release Set integrations/herdr/herdr-plugin.toml to 0.1.4 and add it to the release-prepare checklist in releasing.md. Co-Authored-By: Claude Sonnet 5.5 --- integrations/herdr/herdr-plugin.toml | 2 +- wiki/guides/releasing.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/integrations/herdr/herdr-plugin.toml b/integrations/herdr/herdr-plugin.toml index 268b246..0dd50a2 100644 --- a/integrations/herdr/herdr-plugin.toml +++ b/integrations/herdr/herdr-plugin.toml @@ -1,6 +1,6 @@ id = "wiki-reader" name = "Wiki Reader" -version = "0.1.0" +version = "0.1.4" min_herdr_version = "0.9.0" platforms = ["linux", "macos"] diff --git a/wiki/guides/releasing.md b/wiki/guides/releasing.md index ed138df..c463ec4 100644 --- a/wiki/guides/releasing.md +++ b/wiki/guides/releasing.md @@ -81,7 +81,7 @@ To go back to an older release, repeat the steps with that release's tarball (or Cut a tag only from a commit whose CI is already green on `main`. The release workflow builds and smoke-tests `--version` but does not re-run the full test suite. -1. **Prepare.** Branch `release/vX.Y.Z` (for example `release/v0.1.2`), bump `version` in the workspace `Cargo.toml` to the next `0.1.N` and refresh `Cargo.lock`, and update the roadmap note. Run `./scripts/check.sh`, open a PR, wait for green checks, and squash-merge. +1. **Prepare.** Branch `release/vX.Y.Z` (for example `release/v0.1.2`), bump `version` in the workspace `Cargo.toml` to the next `0.1.N` and refresh `Cargo.lock`, bump `version` in `integrations/herdr/herdr-plugin.toml` to match, and update the roadmap note. Run `./scripts/check.sh`, open a PR, wait for green checks, and squash-merge. 2. **Optional dry run.** In GitHub, Actions → Release → *Run workflow* on the branch or `main`. It builds all three targets, names the packages `dry-run`, and uploads them as workflow artifacts. It does **not** create or touch a GitHub Release (the attach step only runs on a tag push). Use this after changing `release.yml` or its pinned actions. 3. **Tag the merge commit** as `v` plus the `Cargo.toml` version and push the tag. The workflow fails if the tag and the crate version differ.