Update Factorio to 2.1.24

Chart.yaml

@@ -3,4 +3,4 @@ name: factorio
 description: Portable Factorio dedicated server with metrics and monitoring
 type: application
 version: 0.0.0
-appVersion: 2.1.23
+appVersion: 2.1.24

README.md

@@ -36,14 +36,14 @@ or stores the password. The Secret must contain the `rcon-password` key.
 
 ## Upgrade Factorio yourself
 
-For an application release such as `2.1.23`:
+For an application release such as `2.1.24`:
 
-1. Set `appVersion` in `Chart.yaml` to `2.1.23`. Do not edit `version`; CI derives
+1. Set `appVersion` in `Chart.yaml` to `2.1.24`. Do not edit `version`; CI derives
    the chart package version from Git tags with `git describe --tags --long`.
 2. Run `./test.sh`, inspect the diff, and commit the change to `main`.
 3. Tag that commit with the exact application version, for example
-   `git tag v2.1.23`, then push the commit and tag with
-   `git push origin main v2.1.23`.
+   `git tag v2.1.24`, then push the commit and tag with
+   `git push origin main v2.1.24`.
 4. Gitea Actions validates and publishes the chart to the public indexed Helm
    repository, then updates only Factorio's chart `targetRevision` in
    `homelab-gitops`. Argo CD applies the new release; no manual GitOps edit or
@@ -51,7 +51,7 @@ For an application release such as `2.1.23`:
 
 The chart version at an application tag is the application version. A later
 chart-only commit becomes a unique `git describe` version such as
-`2.1.23-1-g41627abcdef`. GitOps selects the exact promoted chart version.
+`2.1.24-1-g41627abcdef`. GitOps selects the exact promoted chart version.
 
 ## Data and runtime behavior