Merge pull request #1153 from nginx-proxy/acme.sh-3.0.9

build: bump acme.sh to 3.0.9

Dockerfile

@@ -3,7 +3,7 @@ FROM docker.io/nginxproxy/docker-gen:0.14.2 AS docker-gen
 FROM docker.io/library/alpine:3.20.3
 
 ARG GIT_DESCRIBE="unknown"
-ARG ACMESH_VERSION=3.0.7
+ARG ACMESH_VERSION=3.0.9
 
 ENV ACMESH_VERSION=${ACMESH_VERSION} \
     COMPANION_VERSION=${GIT_DESCRIBE} \

docs/Let's-Encrypt-and-ACME.md

@@ -12,7 +12,7 @@ The following environment variables are optional and parametrize the way the Let
 
 #### DNS-01 ACME challenge
 
-In order to switch to the DNS-01 ACME challenge, set the `ACME_CHALLENGE` environment variable to `DNS-01` on your acme-companion container. This will also require you to set the `ACMESH_DNS_API_CONFIG` environment variable to a JSON or YAML string containing the configuration for the DNS provider you are using. Inside the JSON or YAML string, the `DNS_API` property is always required and should be set to the name of the [acme.sh DNS API](https://github.com/acmesh-official/acme.sh/tree/3.0.7/dnsapi) you want to use.
+In order to switch to the DNS-01 ACME challenge, set the `ACME_CHALLENGE` environment variable to `DNS-01` on your acme-companion container. This will also require you to set the `ACMESH_DNS_API_CONFIG` environment variable to a JSON or YAML string containing the configuration for the DNS provider you are using. Inside the JSON or YAML string, the `DNS_API` property is always required and should be set to the name of the [acme.sh DNS API](https://github.com/acmesh-official/acme.sh/tree/3.0.9/dnsapi) you want to use.
 
 The other properties required will depend on the DNS provider you are using. For more information on the required properties for each DNS provider, please refer to the [acme.sh documentation](https://github.com/acmesh-official/acme.sh/wiki/dnsapi) (please keep in mind that nginxproxy/acme-companion is using a fixed version of acme.sh, so the documentation might include DNS providers that are not yet available in the version used by this image).