From 0ef41b0efc48d79e415ad70ca2019118d73b349c Mon Sep 17 00:00:00 2001 From: Simon Holloway Date: Tue, 17 Dec 2024 23:24:32 +0000 Subject: [PATCH] docs: mark new features as experimental --- docs/core-tools.md | 6 +++--- docs/environments/secrets.md | 2 +- docs/tasks/task-configuration.md | 2 +- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/core-tools.md b/docs/core-tools.md index c7a4ca8a81..337513ecda 100644 --- a/docs/core-tools.md +++ b/docs/core-tools.md @@ -9,13 +9,13 @@ You can see the core plugins with `mise registry -b core`. - [Bun](/lang/bun) - [Deno](/lang/deno) -- [Elixir](/lang/elixir) +- [Elixir](/lang/elixir) - [Erlang](/lang/erlang) - [Go](/lang/go) - [Java](/lang/java) - [NodeJS](/lang/node) - [Python](/lang/python) - [Ruby](/lang/ruby) -- [Rust](/lang/rust) -- [Swift](/lang/swift) +- [Rust](/lang/rust) +- [Swift](/lang/swift) - [Zig](/lang/zig) diff --git a/docs/environments/secrets.md b/docs/environments/secrets.md index 4d5f02f30c..ddace64589 100644 --- a/docs/environments/secrets.md +++ b/docs/environments/secrets.md @@ -1,4 +1,4 @@ -# Secrets +# Secrets Because env vars in mise.toml can store sensitive information, mise has built-in support for reading encrypted secrets from files. Currently, this is done with a [sops](https://getsops.io) implementation diff --git a/docs/tasks/task-configuration.md b/docs/tasks/task-configuration.md index 0e777b304a..f4d5e08b03 100644 --- a/docs/tasks/task-configuration.md +++ b/docs/tasks/task-configuration.md @@ -321,7 +321,7 @@ run = "echo task4" If you want auto-completion/validation in included toml tasks files, you can use the following JSON schema: -## `redactions` +## `redactions` - **Type**: `string[]`