docs: Add proto v0.19 blog post.

Cargo.toml

@@ -24,7 +24,7 @@ default-members = ["crates/cli"]
 
 [workspace.dependencies]
 async-trait = "0.1.73"
-cached = "0.45.1"
+cached = "0.46.0"
 chrono = { version = "0.4.31", features = ["serde"] }
 cd_env = "0.1.2"
 ci_env = "0.2.1"
@@ -39,7 +39,7 @@ pathdiff = "0.2.1"
 petgraph = { version = "0.6.4", default-features = false, features = [
 	"serde-1",
 ] }
-proto_core = "0.18.6"
+proto_core = "0.19.0"
 relative-path = { version = "1.9.0", features = ["serde"] }
 regex = "1.9.5"
 reqwest = { version = "0.11.20", default-features = false, features = [

crates/node/tool/src/node_tool.rs

@@ -185,7 +185,7 @@ impl Tool for NodeTool {
                 if setup || !self.tool.get_tool_dir().exists() {
                     print_checkpoint(format!("installing node {version}"), Checkpoint::Setup);
 
-                    if self.tool.setup(version).await? {
+                    if self.tool.setup(version, false).await? {
                         last_versions.insert("node".into(), version.to_owned());
                         installed += 1;
                     }

crates/node/tool/src/npm_tool.rs

@@ -86,7 +86,7 @@ impl Tool for NpmTool {
 
         print_checkpoint(format!("installing npm {version}"), Checkpoint::Setup);
 
-        if self.tool.setup(version).await? {
+        if self.tool.setup(version, false).await? {
             last_versions.insert("npm".into(), version.to_owned());
             count += 1;
         }

crates/node/tool/src/pnpm_tool.rs

@@ -92,7 +92,7 @@ impl Tool for PnpmTool {
 
         print_checkpoint(format!("installing pnpm {version}"), Checkpoint::Setup);
 
-        if self.tool.setup(version).await? {
+        if self.tool.setup(version, false).await? {
             last_versions.insert("pnpm".into(), version.to_owned());
             count += 1;
         }

crates/node/tool/src/yarn_tool.rs

@@ -148,7 +148,7 @@ impl Tool for YarnTool {
 
         print_checkpoint(format!("installing yarn {version}"), Checkpoint::Setup);
 
-        if self.tool.setup(version).await? {
+        if self.tool.setup(version, false).await? {
             last_versions.insert("yarn".into(), version.to_owned());
             count += 1;
         }

crates/rust/tool/src/rust_tool.rs

@@ -99,7 +99,7 @@ impl Tool for RustTool {
             if setup || !self.tool.get_tool_dir().exists() {
                 print_checkpoint(format!("installing rust {version}"), Checkpoint::Setup);
 
-                if self.tool.setup(version).await? {
+                if self.tool.setup(version, false).await? {
                     last_versions.insert("rust".into(), version.to_owned());
                     installed += 1;
                 }

nextgen/app/src/systems/startup.rs

@@ -136,7 +136,7 @@ pub fn load_toolchain_config(workspace_root: StateRef<WorkspaceRoot>, resources:
         );
     }
 
-    let mut proto_tools = ToolsConfig::load(proto_path)?;
+    let mut proto_tools = ToolsConfig::load_from(workspace_root)?;
     proto_tools.inherit_builtin_plugins();
 
     let config = if config_path.exists() {

nextgen/workspace/src/workspace.rs

@@ -5,7 +5,7 @@ use moon_common::consts;
 use moon_config::{InheritedTasksManager, ToolchainConfig, WorkspaceConfig};
 use moon_hash::HashEngine;
 use moon_vcs::{BoxedVcs, Git};
-use proto_core::{ProtoEnvironment, ToolsConfig, Version, TOOLS_CONFIG_NAME};
+use proto_core::{ProtoEnvironment, ToolsConfig, Version};
 use starbase::Resource;
 use starbase_styles::color;
 use starbase_utils::{dirs, fs};
@@ -176,7 +176,7 @@ impl Workspace {
 
         // Load proto tools
         let proto_env = ProtoEnvironment::new()?;
-        let mut proto_tools = ToolsConfig::load(root_dir.join(TOOLS_CONFIG_NAME))?;
+        let mut proto_tools = ToolsConfig::load_from(&root_dir)?;
         proto_tools.inherit_builtin_plugins();
 
         // Load configs

packages/cli/CHANGELOG.md

@@ -15,6 +15,7 @@
 #### 🚀 Updates
 
 - Updated `moon dep-graph` to support a task in closest project, similar to `moon run`.
+- Updated to proto v0.19.
 
 #### 🐞 Fixes
 

website/blog/2023-09-29_proto-v0.19.mdx

@@ -0,0 +1,78 @@
+---
+slug: proto-v0.19
+title: proto v0.19 - Version pinning and outdated checks
+authors: [milesj]
+tags: [proto, pin, global, local, outdated]
+image: ./img/proto/v0.18.png
+---
+
+In this release, we're improving version pinning and introducing a new command to check for outdated
+versions.
+
+<!--truncate-->
+
+## New `proto pin` command (breaking)
+
+Before our official v1 release, which is relatively soon, we'll be making some breaking changes with
+the proto APIs. The first is the introduction of the new [`proto pin`](/docs/proto/commands/pin)
+command, which replaces the previous `proto local` and `proto global` commands. We felt this was a
+much cleaner change, and far easier to understand than the previous command names.
+
+```shell
+# v0.18
+$ proto local go 1.20
+$ proto global node 20
+
+# v0.19+
+$ proto pin go 1.20
+$ proto pin node 20 --global
+```
+
+## New `pin-latest` setting
+
+While we're on the subject of pinning versions, we've also introduced a new
+[`pin-latest`](/docs/proto/config#pin-latest) setting. Do you want the latest version to always be
+pinned? Do you forgot to pass `--pin` when installing? Do you forget to run the `proto global` or
+`proto local` commands (now `proto pin`)? If you answered yes to any of these questions, then this
+setting is for you.
+
+When enabled, and a tool is installed with the "latest" version, the resolved version will
+automatically be pinned to the configuration of your choice. For example, say we have the following
+user config:
+
+```toml title="~/.proto/config.toml"
+pin-latest = "local"
+```
+
+And we run one of the following commands:
+
+```shell
+$ proto install go
+$ proto install node latest
+```
+
+Then the resolved version of the tool will automatically be set to the `.prototools` file in the
+current directory. Handy right?
+
+## New `proto outdated` command
+
+By request of the community, we're introducing yet another new command,
+[`proto outdated`](/docs/proto/commands/outdated). If you're familiar with package managers, you can
+probably guess what this command does! It'll check for newer available versions, for all tools
+configured in the closest `.prototools` file. Very handy for keeping your tools up to date.
+
+```
+$ proto outdated
+
+go - current version 1.20.2 (via ~1.20), newer version 1.20.8, update available!
+node - current version 20.7.0 (via 20.7.0), latest version 20.8.0, update available!
+```
+
+## Other changes
+
+View the [official release](https://github.com/moonrepo/proto/releases/tag/v0.19.0) for a full list
+of changes.
+
+- Added `PROTO_WASM_LOG` environment variable to toggle the logging of messages from Extism and WASM
+  plugins. Useful for debugging.
+- Updated `proto install` to auto-clean stale plugins after a successful installation.

website/docs/proto/commands/add-plugin.mdx

@@ -2,6 +2,10 @@
 title: add-plugin
 ---
 
+import VersionLabel from '@site/src/components/Docs/VersionLabel';
+
+<VersionLabel version="0.16.0" header />
+
 The `proto add-plugin <id> <locator>` (or `proto ap`) command will add the provided plugin ID and
 locator string to the `[plugins]` section of the local (`.prototools`) or global
 (`~/.proto/config.toml`) config file.