rix/docs.coopcloud.tech
0
0
Fork 0
forked from toolshed/docs.coopcloud.tech
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: point to project, wording/formatting warning

Browse Source
This commit is contained in:
decentral1se 2025-04-21 19:49:57 +02:00
parent fdec4f5b50
commit 8776914888
Signed by untrusted user: decentral1se
GPG Key ID: 03789458B3D0C410
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/maintainers/handbook.md
View File

@ -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 <recipe>`, 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`.