docs: mark new features as experimental (jdx#3659)

miguelmig · Dec 21, 2024 · 192470b · 192470b
1 parent d2181a4
commit 192470b
Show file tree

Hide file tree

Showing 3 changed files with 5 additions and 5 deletions.
diff --git 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) <Badge type="warning" text="experimental" />
 - [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) <Badge type="warning" text="experimental" />
+- [Swift](/lang/swift) <Badge type="warning" text="experimental" />
 - [Zig](/lang/zig)
diff --git a/docs/environments/secrets.md b/docs/environments/secrets.md
@@ -1,4 +1,4 @@
-# Secrets
+# Secrets <Badge type="warning" text="experimental" />
 
 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
@@ -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: <https://mise.jdx.dev/schema/mise-task.json>
 
-## `redactions`
+## `redactions` <Badge type="warning" text="experimental" />
 
 - **Type**: `string[]`