From 59343473454b70879d1db73bcc304ea9894444e7 Mon Sep 17 00:00:00 2001 From: goodspark Date: Wed, 7 Jan 2026 07:57:58 -0800 Subject: [PATCH] Fix typo in pinning versions docs I'm guessing there was some tool that ran across stuff and replaced anything that looked vaguely like an email with this but it doesn't make sense for package version pin. Signed-off-by: goodspark --- docs/devbox/guides/pinning-packages/index.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/devbox/guides/pinning-packages/index.mdx b/docs/devbox/guides/pinning-packages/index.mdx index e0e0786..06b60fa 100644 --- a/docs/devbox/guides/pinning-packages/index.mdx +++ b/docs/devbox/guides/pinning-packages/index.mdx @@ -38,11 +38,11 @@ For example, to use the latest version of `ripgrep,` run `devbox add ripgrep`, `devbox add ripgrep@latest`, or add `ripgrep@latest` to your devbox.json package list. To add a specific version of a package, write `@`. For example, to pin the -`nodejs` package to version `20.1.0`, you can run `devbox add [email protected]` or add -`[email protected]` to the packages list in your `devbox.json`: +`nodejs` package to version `20.1.0`, you can run `devbox add package_name@version` or add +`package_name@version` to the packages list in your `devbox.json`: ``` -"packages": [ "[email protected]"] +"packages": [ "package_name@version"] ``` For packages that use semver, you can pin a range of versions for your project. For example, if you