docs: version warning and drop --ignore-env-version

See toolshed/abra#607

docs/abra/hack.md

@@ -91,6 +91,26 @@ Please ask `@decentral1se` or on the Matrix channels for SSH access to the machi
 
 We use [`bats`](https://bats-core.readthedocs.io/en/stable/) to run the tests. You can install the required dependencies with the following. You also need a working installation of Docker and Go >= 1.16 (not covered in this section).
 
+##### Fedora 
+
+```
+sudo dnf install bats
+```
+
+Unfortunately, the Fedora `bats` package doesn't include the libraries we need, so we need to clone those manually:
+
+```
+mkdir -p ~/.local/share/bats/
+cd ~/.local/share/bats
+git clone https://github.com/bats-core/bats-assert.git
+git clone https://github.com/bats-core/bats-file.git
+git clone https://github.com/bats-core/bats-support.git
+```
+
+Then, before running tests, set `export BATS_LIB_PATH=~/.local/share/bats/`
+
+##### Debian
+
 ```
 apt install bats-file bats-assert bats-support jq make git
 ```
@@ -111,7 +131,7 @@ For some tests an actual server is needed, where apps can be deployed. You can e
 ##### Remote swarm
 
 ```
-export ABRA_TEST_DOMAIN="test.example.com"
+export TEST_SERVER="test.example.com"
 export ABRA_DIR="$HOME/.abra_test"
 ```
 
@@ -200,6 +220,52 @@ bats -Tp tests/integration --filter-status failed # re-run only failed
 
 If you're running into issues and want to debug stuff, you can pass `-x` to `bats` to trace all commands run in the test. You can add `echo '...' >&3` debug statements to your test to output stuff also.
 
+## Internationalisation
+
+`abra` can be translated into other languages. We use a combination of [`gettext`](https://www.gnu.org/software/gettext/), [`weblate`](https://translate.coopcloud.tech) and some [intermediate automation](https://git.coopcloud.tech/toolshed/abra/src/commit/20909695e0e05c6251029dba270b3d4741aeb7a8/.drone.yml#L10-L29) to help developers and translators work together conveniently.
+
+### Developer workflow
+
+You just hack on `abra` as you normally would.
+
+If you need to add a string, use `i18n.G` to wrap it. See [`gotext`](https://github.com/leonelquinteros/gotext) for the full API.
+
+For example.
+
+```go
+i18n.G("my string")
+i18n.G("my string with err: %s", err)
+log.Debug(i18n.G("my string"))
+log.Info(i18n.G("my string with err: %s", err))  # N.B no log.Infof usage here
+```
+
+Then you need to update the `pkg/i18n/locales/abra.pot` file with your new strings for the translators.
+
+```bash
+apt install -y gettext
+go install -v -x github.com/snapcore/snapd/i18n/xgettext-go@2.57.1
+make i18n
+```
+
+Commit the changes. Ignore `*.mo` changes if they only update the generation timestamp.
+
+### Translator workflow
+
+You can translate strings on [Weblate (`translate.coopcloud.tech`)](https://translate.coopcloud.tech). 
+
+It's also possible to translate using [`poedit`](https://poedit.net). Weblate is the recommended approach. 
+
+All translation files are located in [`pkg/i18n/locales`](https://git.coopcloud.tech/toolshed/abra/src/branch/main/pkg/i18n/locales). Once translations are updated in weblate, they will be incorporated into the next release of `abra` automatically.
+
+### End-user workflow
+
+You simply export the `LANG` env var to match your desired translation.
+
+```
+export LANG=es
+abra -h
+```
+
 ## Using the `abra` public API
 
 Warning, there is currently no stability promise for the `abra` public API! Most of the internals are exposed in order to allow a free hand for developers to try build stuff. If people start to build things then we can start the discussion on what is useful to have open/closed and keep stable etc. Please let us know if you depend on the APIs!

docs/abra/trouble.md

@@ -23,6 +23,7 @@ Host example.com
 and your IdentityFile should be added to the authentication agent:
 
 ```
+eval `ssh-agent`
 ssh-add ~/.ssh/example@somewhere
 ```
 
@@ -101,3 +102,7 @@ Otherwise, you can try manually cloning the recipe repository to the correct loc
 ```
 $ git clone https://git.coopcloud.tech/coop-cloud/MyCoolRecipe.git ~/.abra/recipes
 ```
+
+## "only updates to Labels are allowed"
+
+See [Packaging handbook » What does "only updates to Labels are allowed" mean](maintainers/handbook/#what-does-only-updates-to-labels-are-allowed-mean).

docs/abra/upgrade.md

@@ -53,6 +53,11 @@ And test things work.
 
 > General release notes are [here](https://git.coopcloud.tech/toolshed/abra/releases/)
 
+### `0.10.x-beta` -> `WIP`
+
+* We now ensure that `$ABRA_DIR/servers` has stricter permissions (`0600`).
+  See [`#592`](https://git.coopcloud.tech/toolshed/abra/pulls/592) for more.
+
 ### `0.9.x-beta` -> `0.10.x-beta`
 
 * `abra` will now write the app deployment version to the app env file
@@ -77,6 +82,10 @@ And test things work.
 * Auto-completion for `abra` is handled differently now. See `abra autocomplete
   --help` for more. The full help output is available for each specific shell,
   e.g. `abra autocomplete zsh --help`. It is now generated on the fly.
+  **WARNING**: you'll need to REMOVE your pre `v0.10.x` `abra` auto-complete
+  config for the new auto-complete to work. Check your `$SHELL` configuration
+  file (e.g. `.zshrc` for Zsh). See
+  [`#553`](https://git.coopcloud.tech/toolshed/abra/issues/553) for more.
 
 * Several commands now make use of the `--chaos/-C` commands, such as `abra app
   ps` and `abra app cp`. See `--help` for more.
@@ -133,6 +142,10 @@ And test things work.
 * It's now possible to set the character charset for a password. See
   [`#521`](https://git.coopcloud.tech/toolshed/abra/issues/521) for more.
 
+* `abra secret insert` now supports a `--file/-f` flag to support inserting
+  from file without using Bash-isms. See See
+  [`#555`](https://git.coopcloud.tech/toolshed/abra/issues/555) for more.
+
 ### `0.8.x-beta` -> `0.9.x-beta`
 
 None at this time.

docs/federation/handbook.md

@@ -32,6 +32,6 @@ Here is some invitation boilerplate which you can use:
 >
 > There are no "stupid questions"! It's a space to inquire, be curious and have a good time and get to know each other.
 >
-> We take notes and doodle on [this collaboratively editable pad](https://pad.autonomic.zone/LqotfSJJRj69RcTtWmr7iw). If you don't have time to attend, feel free to drop your questions and some contact details also, so we can get in touch. This is only the first Kite Flying Hour in a recurring series of Kite Flying Hours.
+> We take notes and doodle on [this collaboratively editable pad](https://pad.autonomic.zone/VtyrLUl9RWaJGgEDrncQUw?view). If you don't have time to attend, feel free to drop your questions and some contact details also, so we can get in touch. This is only the first Kite Flying Hour in a recurring series of Kite Flying Hours.
 >
 > Hope to see you there! ☁️ 🌞 🖥️

docs/federation/membership.md

@@ -18,6 +18,6 @@ title: Membership
 | [UTAW](https://utaw.tech) | -  | - | `@javielico:matrix.org` |
 | `@decentral1se` | Waiver | - | `@decentral1se` |
 | [ruangrupa](https://ruangrupa.id) | - | - | Henry `@babystepper:matrix.org` |
-| [Ammar](https://social.coop/@ammaratef45) | - | - | `@ammaratef45:matrix.org` |
+| [RTM](https://resisttechmonopolies.online) | ✅ | - | `@ammaratef45:matrix.org` + `@linnealovespie:matrix.org`|
 | [MIR](https://mirnet.org/) | ✅ | - | `@brooke:pub.solar` |
 | [Red Abya Yala](https://abyayala.sutty.nl/) | - | - | `@fauno:sutty.nl` |

docs/federation/resolutions/in-progress/033.md

@@ -0,0 +1,33 @@
+---
+title: "Resolution 033: Changing OpenCollective fiscal host"
+---
+
+- Topic: Changing OpenCollective fiscal host to Platform6
+- Date: 2025-07-16
+- Deadline: 2025-07-30
+- Size: Large
+
+## Summary
+
+Currently, the Open Collective "fiscal host" for Co-op Cloud is [Autonomic
+co-operative](https://autonomic.zone).
+
+This resolution proposes switching fiscal host to [Platform
+6](https://platform6.coop), by transferring our funds from Autonomic to
+Platform 6, and changing our registered fiscal host on Open Collective.
+
+This resolution will close Budget 001, because Platform 6 will take a fixed 5%
+of income, instead of being paid hourly.
+
+## Details
+
+Autonomic has been the fiscal host for Co-op Cloud since the first project
+funding was received.
+
+Since then, Autonomic has less capacity for finance administration work -- and
+Co-op Cloud is now managed by a democratic federation.
+
+So, to open up more capacity for project finance administration work, and to
+further decentralise Co-op Cloud organising from Autonomic, we're proposing
+Platform 6. Platform 6 have been fiscal host for co-operative projects
+including [meet.coop](https://meet.coop) and [wiki.cafe](https://wiki.cafe).

docs/federation/resolutions/passed/001.md

@@ -1,5 +1,5 @@
 ---
-title: "Resolution 001"
+title: "Resolution 001: Decision-Making Process"
 ---
 
 - Topic: Decision Making Process

docs/federation/resolutions/passed/002.md

@@ -1,5 +1,5 @@
 ---
-title: "Resolution 002"
+title: "Resolution 002: Membership/Dues"
 ---
 
 * Topic: Membership/Dues

docs/federation/resolutions/passed/003.md

@@ -1,5 +1,5 @@
 ---
-title: "Resolution 003"
+title: "Resolution 003: Paid Work"
 ---
 
 * Topic: Paid work

docs/federation/resolutions/passed/004.md

@@ -1,5 +1,5 @@
 ---
-title: "Resolution 004"
+title: "Resolution 004: Budgeting (+ Budget 001: Monlthy Meetings)"
 ---
 
 * Topic: Budget 001: Budgeting

docs/federation/resolutions/passed/005.md

@@ -1,5 +1,5 @@
 ---
-title: "Resolution 005"
+title: "Resolution 005: Public federation membership.."
 ---
 
 * Topic: Public federation membership, notes and decisions

docs/federation/resolutions/passed/006.md

@@ -1,5 +1,5 @@
 ---
-title: "Resolution 006"
+title: "Resolution 006: Budget 002 Resolution Writing-up"
 ---
 
 - Budget 002: Resolution Writing-up
@@ -11,7 +11,7 @@ title: "Resolution 006"
 
 Agree Budget 002, for €100 for @decentral1se to write up 2 resolutions.
 
-### Details (Budget YYY)
+### Details (Budget 002)
 
 **Budget amount**: EUR 100
 

docs/federation/resolutions/passed/007.md

@@ -1,5 +1,5 @@
 ---
-title: "Resolution 007"
+title: "Resolution 007: Dues waiver for Doop.coop"
 ---
 
 - Topic: 1 year dues waiver for Doop.coop

docs/federation/resolutions/passed/008.md

@@ -1,5 +1,5 @@
 ---
-title: "Resolution 008"
+title: "Resolution 008: Budget 003 Paying Invoices"
 ---
 
 - Topic: Budget 003 Paying invoices

docs/federation/resolutions/passed/009.md

@@ -1,5 +1,5 @@
 ---
-title: "Resolution 009" 
+title: "Resolution 009: Federation common fund buffer" 
 ---
 
 - Topic: Federation common fund buffer

docs/federation/resolutions/passed/010.md

@@ -1,5 +1,5 @@
 ---
-title: "Resolution 010"
+title: "Resolution 010: Budget 004 Critical fixes"
 ---
 
 - Topic: Budget 004: Critical fixes

docs/federation/resolutions/passed/011.md

@@ -1,5 +1,5 @@
 ---
-title: "Resolution 011" 
+title: "Resolution 011: Budget 005: Backup improvements" 
 ---
 
 - Topic: Budget 005: Backup improvements

docs/federation/resolutions/passed/012.md

@@ -1,5 +1,5 @@
 ---
-title: "Resolution 012"
+title: "Resolution 012: Budget 006: Abra integration test suite"
 ---
 
 - Budget 006: Abra integration test suite

docs/federation/resolutions/passed/014.md

@@ -1,5 +1,5 @@
 ---
-title: "Resolution 014"
+title: "Resolution 014: Budget 008: Critical Fixes"
 ---
 
 - Topic: Budget 008: Critical Fixes

docs/federation/resolutions/passed/015.md

@@ -1,5 +1,5 @@
 ---
-title: "Resolution 015"
+title: "Resolution 015: Klasse and Methode joins"
 ---
 
 - Topic: Klasse & Methode joins the Co-op Cloud Federation

docs/federation/resolutions/passed/016.md

@@ -1,5 +1,5 @@
 ---
-title: "Resolution 016"
+title: "Resolution 016: Budget 008: Backup-bot-two …"
 ---
 
 - Topic: Budget 008: Backup-bot-two Documentation and Specification

docs/federation/resolutions/passed/017.md

@@ -1,5 +1,5 @@
 ---
-title: "Resolution 017"
+title: "Resolution 017: BeWater joins"
 ---
 
 - Topic: BeWater joins the Co-op Cloud Federation

docs/federation/resolutions/passed/018.md

@@ -1,5 +1,5 @@
 ---
-title: "Resolution 018"
+title: "Resolution 018: EOTL joins"
 ---
 
 - Topic: EOTL joins the Co-op Cloud Federation

docs/federation/resolutions/passed/019.md

@@ -1,5 +1,5 @@
 ---
-title: "Resolution 019"
+title: "Resolution 019: Karrot joins"
 ---
 
 - Topic: Karrot joins the Co-op Cloud Federation

docs/federation/resolutions/passed/020.md

@@ -1,8 +1,8 @@
 ---
-title: "Resolution 020"
+title: "Resolution 020: Budget 010: Abra integration test suite"
 ---
 
-- Topic: Budget 10: Abra integration suite automation
+- Topic: Budget 010: Abra integration suite automation
 - Date: 04-04-2024
 - Deadline: 18-04-2024
 - Size: Large

docs/federation/resolutions/passed/021.md

@@ -1,5 +1,5 @@
 ---
-title: "Resolution 021"
+title: "Resolution 021: Budget 011: Migrate to Cobra"
 ---
 
 - Topic: Budget 011: Migrate to Cobra

docs/federation/resolutions/passed/022.md

@@ -1,5 +1,5 @@
 ---
-title: "Resolution 022"
+title: "Resolution 022: Ammar joins"
 ---
 
 - Topic: Ammar joins the Co-op Cloud Federation

docs/federation/resolutions/passed/023.md

@@ -1,5 +1,5 @@
 ---
-title: Resolution 023
+title: "Resolution 023: Budget 012: … new Co-op Cloud website"
 ---
 
 - Topic: Budget 012: Feedback gathering and content architecture for the new Co-op Cloud website

docs/federation/resolutions/passed/024.md

@@ -1,4 +1,6 @@
-# Resolution 024: Budget: 013: Reintroduce kite-flying
+---
+title: "Resolution 024: Budget: 013: Reintroduce kite-flying"
+---
 
 - Topic: Reintroduce paid kite-flying hour
 - Date: 2024-10-30

docs/federation/resolutions/passed/025.md

@@ -1,4 +1,6 @@
-# Resolution 025 Maintainers Proposal
+---
+title: "Resolution 025 Maintainers Proposal"
+---
 
 - Topic:  Maintainers Proposal
 - Date: 05-12-2024

docs/federation/resolutions/passed/026.md

@@ -1,5 +1,5 @@
 ---
-title: "Resolution 026"
+title: "Resolution 026: Budget 014: Backpay for v0.10.x abra release work"
 ---
 
 - Topic: Budget 014: Backpay for `v0.10.x` abra release work

docs/federation/resolutions/passed/027.md

@@ -1,5 +1,5 @@
 ---
-title: "Resolution 027"
+title: "Resolution 027: MIR joins"
 ---
 
 - Topic: MIR joins the Co-op Cloud Federation

docs/federation/resolutions/passed/028.md

@@ -1,4 +1,6 @@
-# Resolution 028: Red Abya Yala joins the Co-op Cloud Federation
+---
+title: "Resolution 028: Red Abya Yala joins the Co-op Cloud Federation"
+---
 
 - Topic: Red Abya Yala joins the Co-op Cloud Federation
 - Date: 16-01-2025

docs/federation/resolutions/passed/029.md

@@ -1,4 +1,6 @@
-# Resolution 29 Budget 14: Federation Radmin
+---
+title: "Resolution 029: Budget 014: Federation Radmin"
+---
 
 - Topic: Establish Budget 14, to pay for up to 12 hours a month of "radmin" (radical administration) work, to help the federation run smoother, for an initial period of 12 months.
 - Date: 05-04-2025

docs/federation/resolutions/passed/031.md

@@ -1,5 +1,5 @@
 ---
-title: "Resolution 031"
+title: "Resolution 031: Critical fixes amended process"
 ---
 
 - Topic: Critical fixes amended process

docs/federation/resolutions/passed/032.md

@@ -0,0 +1,22 @@
+---
+title: "Resolution 032: RIM joins"
+---
+
+- Topic: RTM joins Coopcloud
+- Date: 2025-06-30
+- Deadline: 2025-07-10
+- Size: Large
+
+### Summary
+
+Ammar's membership was approved in [Resolution 022](/federation/resolutions/passed/022).
+
+Since the establishment of RTM (Resist Rech Monopolies) collective in Seattle, Ammar has been unofficially representing the collective with coopcloud and vice versa.
+	
+### Details
+	
+RTM relies on the coop-cloud stack to host and manage their infrastructure, with the possibility of expanding this infrastructure to serve other communities and groups as the needs are identified and the capacity of the collective grows.
+
+In a loomio decision, the collective approved pursuing a membership with the federation and Ammar is both happy to vouch and to yield their membership to the group.
+
+This way this decision doesn't affect the total number of members.

docs/federation/resolutions/stalled/013.md

@@ -1,5 +1,5 @@
 ---
-title: "Resolution 013" 
+title: "Resolution 013: Budget 007: Operator sync" 
 ---
 
 !!! note

docs/federation/resolutions/stalled/030.md

@@ -1,4 +1,6 @@
-# Co-op Cloud resolution 030: docs / naming survey
+---
+title: "Co-op Cloud resolution 030: Budget XXX: Docs / naming survey"
+---
 
 - Topic: Budget for a survey about the Co-op Cloud documentation 
 - Date: 2025-04-03

docs/maintainers/handbook.md

@@ -386,6 +386,19 @@ It is good practice to take note of all the issues you ran into and share them w
 
 If you don't have time or are not an operator, reach out on our communication channels for an operator willing to do some testing.
 
+## What does "only updates to Labels are allowed" mean
+
+If you see something like this:
+
+```
+FATA failed to update config traefik_traefik_yml_v22: Error response from daemon: rpc error: code = InvalidArgument desc = only updates to Labels are allowed
+```
+
+It means that a Docker "config" has been updated, but the version number has not been incremented.
+
+To fix this, edit a recipe's `abra.sh` and update the version number of the relevant line –­in this case, `export TRAEFIK_YML_VERSION=v22`.
+`
+
 ## How do I write version release notes?
 
 In the root of your recipe repository, run the following (if the folder doesn't already exist):
@@ -400,7 +413,7 @@ You can also add release notes for the next release into a special file `release
 
 !!! warning "Watch out for old versions of `abra` 🚧"
 
-    This feature is only available in the > 0.9.x series of `abra`.
+    This feature is only available in the >= 0.9.x series of `abra`.
 
 ## How do I know whether to accept version upgrades when running `abra recipe upgrade <something>`?
 
@@ -476,6 +489,35 @@ If you want to get the highest rating on SSL certs, you can use the following tr
 
 See [this PR](https://git.coopcloud.tech/coop-cloud/traefik/pulls/8/files) for the technical details
 
+## How do I skip secret generation for a specific secret
+
+!!! warning "Watch out for old versions of `abra` 🚧"
+
+    This feature is only available in the >= 0.11.x series of `abra`.
+
+Add the `# generate=false` comment
+
+```
+SECRET_JWT_SECRET_VERSION=v1 # generate=false
+```
+
+## How do I specify the charset for a specific secret generation
+
+!!! warning "Watch out for old versions of `abra` 🚧"
+
+    This feature is only available in the >= 0.10.x series of `abra`.
+
+```
+SECRET_JWT_SECRET_VERSION=v1 # charset=default,special
+```
+
+Options are:
+* `default`: [source](https://github.com/decentral1se/passgen/blob/8404cb922dea92efa8c3514f0ec8c37ce12a880f/const.go#L23)
+* `special`: [source](https://github.com/decentral1se/passgen/blob/8404cb922dea92efa8c3514f0ec8c37ce12a880f/const.go#L22C29-L22C43)
+* `safespecial`: [source](https://git.coopcloud.tech/toolshed/abra/src/commit/6abaf7a094df1a96599af2c4cbae1769821ad17c/pkg/secret/secret.go#L182)
+* `default,special`: mix of `default` and `special`
+* `default,safespecial`: mix of `default` and `safespecial`
+
 ## How do I change secret generation length?
 
 It is possible to tell `abra` which length it should generate secrets with from your recipe config.

docs/operators/handbook.md

@@ -94,6 +94,26 @@ git commit
 make link
 ```
 
+## Configure `abra` with `abra.yml`
+
+There are few configuration options supported at this time but more can be added. We are open to requests!
+
+### `$ABRA_DIR`
+
+The lookup logic is defined like so.
+
+* lookup $ABRA_DIR env
+* look for config file and take value from there
+* $HOME/.abra as fallback
+
+If you create an `abra.yml` file in your `$PWD` with the following contents.
+
+```
+abraDir: .
+```
+
+Then `$ABRA_DIR` will be automatically picked up as `$PWD`. This is useful when you maintain multiple project configurations and recipes in various state of chaos and would like to separate those. `abra` will create all the usual `$HOME/.abra` state (`servers`/`recipes`/etc.) under your chosen `abraDir` value. This allows you to have multiple independent versions of specific recipes which are relevant for specific projects vs. relying on a single `$ABRA_DIR/recipes/<recipe>` and constantly having to switch between different chaotic hacks.
+
 ## Running abra server side
 
 If you're on an environment where it's hard to run Docker, or command-line programs in general, you might want to install `abra` on a server instead of your local work station.
@@ -464,6 +484,10 @@ route requests after. You're free to make as many `$whatever.yml` files in your
 Yes, it's possible although currently Quite Experimental! See
 [`#388`](https://git.coopcloud.tech/toolshed/organising/issues/388) for more.
 
+## Can I deploy images from a private registry?
+
+Yes, as of [`#585`](https://git.coopcloud.tech/toolshed/abra/pulls/585), this is possible. At current time of writing, this feature is unreleased but this will change shortly. You need to run `docker login` before you run your deploy command.
+
 ## Running an offline coop-cloud server 
 
 You may want to run a coop-cloud directly on your device (or in a VM or machine on your LAN), whether that's for testing a recipe or to run coop-cloud apps outside of the cloud ;-)
@@ -488,7 +512,7 @@ abra app secret insert localhost ssl_key v1 localhost.key -f
 
 !!! warning "Watch out for old versions of `abra` 🚧"
 
-    This feature is only available in the > 0.10.x series of `abra`.
+    This feature is only available in the >= 0.10.x series of `abra`.
 
 It is possible to specify a remote recipe in your `.env` file:
 
@@ -508,7 +532,7 @@ $ABRA_DIR/recipes/mygit_org_myorg_cool-recipe
 
 !!! warning "Watch out for old versions of `abra` 🚧"
 
-    This feature is only available in the > 0.10.x series of `abra`.
+    This feature is only available in the >= 0.10.x series of `abra`.
 
 If you `abra app new`/`abra app deploy`/`abra app upgrade`/`abra app rollback`,
 the version that is deployed will be written to your app `.env` file. You can
@@ -529,13 +553,13 @@ TYPE=custom-html:1.7.1+1.27.2
 
 This `.env` version is then used as the recipe checkout version for **all**
 `abra` operations afterwards unless you specify otherwise on the command-line
-with `[version]` `--chaos/-C` or `--ignore-env-version/-i`.
+with `[version]` `--chaos/-C` or `--latest/-l`.
 
 ## How is the new deployment version determined?
 
 !!! warning "Watch out for old versions of `abra` 🚧"
 
-    This feature is only available in the > 0.10.x series of `abra`.
+    This feature is only available in the >= 0.10.x series of `abra`.
 
 ### `.env` version
 
@@ -545,7 +569,7 @@ deployment overview.
 
 This `.env` version is then used as the recipe checkout version for **all**
 `abra` operations afterwards unless you specify otherwise on the command-line
-with `[version]` `--chaos/-C` or `--ignore-env-version/-i`.
+with `[version]` `--chaos/-C` or `--latest/-l`.
 
 ### `abra app deploy`
 
@@ -568,7 +592,7 @@ The version is chosen using the following priority logic.
 1. deployed app
 1. recipe catalogue (if undeployed)
 
-Use `--ignore-env-version/-i` to deploy the latest release version or commit.
+Use `--latest/-l` to deploy the latest release version or commit.
 
 In all cases 3-5, the app `.env` version is **ignored** as a version candidate.
 

mkdocs.yml

@@ -122,12 +122,14 @@ nav:
               - federation/resolutions/passed/027.md
               - federation/resolutions/passed/028.md
               - federation/resolutions/passed/029.md
+              - federation/resolutions/passed/032.md
+              - federation/resolutions/passed/031.md
           - "Stalled":
               - federation/resolutions/stalled/013.md
+              - federation/resolutions/stalled/030.md
           - "In Progress":
               - federation/resolutions/index.md
-              - federation/resolutions/in-progress/030-docs-naming-survey.md
-              - federation/resolutions/in-progress/031.md
+              - federation/resolutions/in-progress/033.md
       - "Minutes":
           - federation/minutes/index.md
           - "Recently":