Skip to content

0.2.0

Choose a tag to compare

@mattt mattt released this 16 Nov 10:59
1a98a84

Plonge now has rules for every core tool that mise installs, and it's more careful about what it deletes.

New rules:

  • .NET: bin and obj beside a project file, and the NuGet caches (#7)
  • Zig: .zig-cache and Zig's global cache (#8)
  • Python: .tox, .nox, and build and dist beside a Python project (#9)
  • Bun, Deno, and Yarn 2 and later: their global caches (#10)
  • Swift Package Manager: the shared cache (#12), and .build folders whose dependency clones SwiftPM can restore (#19)
  • Elixir and Erlang: Mix _build, and the Hex and Rebar3 package caches (#13)
  • Rust: Cargo's registry (#14)
  • Ruby: vendor/bundle, Rails tmp/cache, and the RubyGems cache (#15)
  • Java: Gradle build output and caches, and the Maven repository (#16)

Plonge now refuses to delete a cache that holds a Git repository, in a project (#11) or a global cache (#17). It also refuses caches that hold data a rebuild can't restore, such as a Mix release or a Maven artifact from mvn install.

Fixes:

  • Plonge didn't recognize projects where a Paseo agent was running, because it didn't expand ~ in Paseo's paths. It does now, and if it can't read Paseo's status, it treats every project as busy (#3).
  • --root with a folder of repositories no longer hides the mise projects inside it (#5).
  • mise-tools measures mise's own installs directory, including a custom MISE_DATA_DIR (#6).
  • Freed-space estimates are closer to the truth: a dry run labels a prune rule's size as the whole cache, --apply reports the change in free space, and on macOS, sizes account for APFS clones (#20).

Rules can now delete a folder's contents, read a path from a tool's output or an environment variable, and protect paths inside a cache. See the rule reference.