docs: explain auto_update's release delay and prefer mise settings KEY=VALUE

docs/dev-tools/index.md

@@ -165,6 +165,19 @@ fails or you are offline, mise warns and runs the version you have.
 A duration such as `"6h"` sets that tool's own interval. Intervals under one
 hour are raised to one hour.
 
+Updates respect [`minimum_release_age`](/security.html#minimum-release-age),
+which defaults to `24h`, so a release is never installed until it is at least
+that old. The check interval adds to this: a release becomes eligible 24 hours
+after it is published, but mise only notices it at the next check. With the
+defaults, an update can land anywhere from 24 to 48 hours after a release. To
+wait longer, raise the cutoff for one tool with its own `minimum_release_age`
+option:
+
+```toml [~/.config/mise/config.toml]
+[tools]
+node = { version = "24", auto_update = "6h", minimum_release_age = "3d" }
+```
+
 - Only global config can turn this on. A project config cannot, and when a
   project sets its own version of the tool, runs in that project do not update
   it.