Releases: moonrepo/proto
Releases · moonrepo/proto
0.53.3
Release Notes
🚀 Updates
- Added a
--quiet flag to proto uninstall.
🐞 Fixes
- Fixed an issue where
global config mode wasn't respected during version detection.
Download proto_cli 0.53.3
0.53.2
Release Notes
🐞 Fixes
- Minor fixes for the activate workflow.
🧩 Plugins
- Updated
node_depman_tool to v0.17.0.
- Added an internal shims feature that resolves issues when npm/pnpm/yarn binaries are ran in isolation (from the install directory). This typically only happens for activate workflows.
⚙️ Internal
Download proto_cli 0.53.2
0.53.1
Release Notes
🐞 Fixes
- Fixed some environment variable loading order issues for activate/run flows.
🧩 Plugins
- Updated
schema_tool to v0.17.7.
- Fixed an unwanted primary executable being injected with the tool identifier, instead of inheriting the user configured primary.
⚙️ Internal
- Reworked identifier handling. This should be backwards compatible.
- Updated dependencies.
Download proto_cli 0.53.1
0.53.0
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
0.52.5
Release Notes
🐞 Fixes
- Fixed some
package.json parsing issues for JavaScript related plugins.
⚙️ Internal
Download proto_cli 0.52.5
0.52.4
Release Notes
🚀 Updates
- Added a
--raw flag to proto debug config and proto debug env for deeper debugging purposes.
🐞 Fixes
- Fixed an issue where relative
file:// plugins would not resolve relative to the directory it's configured in.
⚙️ Internal
Download proto_cli 0.52.4
0.52.3
Release Notes
🐞 Fixes
- Potential fix for the "Failed to rename" error that occurs when downloading plugins. This error can easily trigger when parallel processes are all attempting to download the same plugins.
- Fixed an issue where xz/liblzma was dynamically linked, instead of statically.
- Fixed latest Python versions failing checksum verifications.
⚙️ Internal
Download proto_cli 0.52.3
0.52.2
Release Notes
🐞 Fixes
- Fixed an issue where the "new proto version check" would run more often than necessary.
⚙️ Internal
Download proto_cli 0.52.2
0.52.1
Release Notes
🐞 Fixes
- Fixed an unexpected "operating system/architecture mismatch" error that can arise when installing tools.
Download proto_cli 0.52.1
0.52.0
Release Notes
💥 Breaking
- Reworked how backends (asdf, etc) are configured. Instead of being prefixed on the version, they are now on the tool identifier. Example:
zig = "asdf:0.14" -> "asdf:zig" = "0.14"
- This opens the door for new functionality in the future, and also makes more logical sense.
- We tried to keep the old functionality intact as much as possible, but it may be buggy. We highly suggest migrating to the new format!
- Removed the
[tools.*.backend] setting, as it doesn't work with this new pattern.
- WASM API
- Renamed
ToolContext to PluginContext.
- Renamed
ToolUnresolvedContext to PluginUnresolvedContext.
- Renamed
CommandInstruction.bin field to exe.
- Renamed
RegisterToolOutput.inventory field to inventory_options.
- Renamed
ToolInventoryMetadata to ToolInventoryOptions.
🚀 Updates
- Added support for custom and third-party backend plugins, which can be configured with the new
[plugins.backends] setting.
- To differentiate between tool plugins, a new
[plugins.tools] setting was also added. Existing plugins should continue to work without modification.
- Added a
--type option to proto plugin add and proto plugin remove.
- Updated lockfiles to track
os and arch information.
- For existing entries, we attempt to backfill these values. If you run into issues, delete the lockfile and regenerate it with
--force.
- WASM API
- Added a
RegisterToolOutput.lock_options field, so that tools can customize how to interact with the lockfile.
⚙️ Internal
Download proto_cli 0.52.0
