moonrepo/proto v0.53.0

0.53.0

on GitHub

Release Notes

💥 Breaking

• Backend managed tools must now include the backend prefix when configuring in [tools], to avoid naming collisions with non-backend tools. Example: [tools."asdf:zig"] instead of [tools.zig].
  • We'll temporarily support the old format until the next release, in which it will be removed completely.
• WASM API
  • Removed RegisterToolOutput.config_schema field. Use define_tool_config instead.

🚀 Updates

• Added a new command, proto exec, that can be used to execute a command in the context of a temporarily activated proto environment. A list of tools and versions can be provided, and the command will run with those tools available in PATH.
  • Example: proto exec node@20 npm@10 -- node --version
• Improved backend plugin support.
  • Added a [backends.<id>] setting for configuring the backend (not the tool) itself.
  • Improved interoperability between plugins.
• Added a mechanism for plugins to setup the environment during activation and execution workflows.
• WASM API
  • Added a get_backend_config helper function to retrieve the backend configuration.
  • Added a define_tool_config, define_backend_config, and activate_environment plugin (guest) functions.
  • Added a DefineToolConfigOutput, DefineBackendConfigOutput, ActivateEnvironmentInput, and ActivateEnvironmentOutput types.
  • Added a ToolInventoryOptions.scoped_backend_dir field.
  • Added a NativeInstallInput.force field.

🐞 Fixes

• Fixed an issue where shims that belong to a backend (like asdf) would fail to run.
  • You may need to regenerate your shims or reinstall the tool to mitigate this.

⚙️ Internal

• Updated Rust to v1.90.0.
• Updated dependencies.

Download proto_cli 0.53.0