From 87769148887618d3fb553869c03fe7455c697a10 Mon Sep 17 00:00:00 2001 From: decentral1se Date: Mon, 21 Apr 2025 19:49:57 +0200 Subject: [PATCH] docs: point to project, wording/formatting warning --- docs/maintainers/handbook.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/maintainers/handbook.md b/docs/maintainers/handbook.md index 099fa641..15291a3f 100644 --- a/docs/maintainers/handbook.md +++ b/docs/maintainers/handbook.md @@ -374,7 +374,7 @@ And once more, we can validate this tag has been created with `cd ~/.abra/recipe ## How are new recipe versions tested? -This is currently a manual process. Our best estimates are to do a backup and run a test deployment and see how things go. +This is currently a manual process. Our best estimates are to do a backup and run a test deployment and see how things go. [We are working on improving this](https://git.coopcloud.tech/toolshed/-/projects/31). Following the [entry above](/maintainers/handbook/#how-do-i-release-a-new-recipe-version), before running `abra recipe release --publish `, you can deploy the new version of the recipe. You find an app that relies on this recipe and pass `-C/--chaos` to `ugrade` so that it accepts the locally unstaged changes. @@ -398,7 +398,7 @@ And then create a text file which corresponds to the version release, e.g. `1.1. You can also add release notes for the next release into a special file `release/next`. This file will be used when running `abra recipe release`. -!!! warning "Not available previous versions of Abra" +!!! warning "Watch out for old versions of `abra` 🚧" Using `release/next` is only available in > 0.9.x series of `abra`.