Skip to content

CLI 0.37.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 08 Oct 12:41
· 24 commits to main since this release
release-cli/0.37.0
60d5712

Packmind CLI 0.37.0

Installation

npm/npx

npm install -g @packmind/cli@0.37.0

Standalone Executables

Download the appropriate executable for your platform:

  • Linux x64: packmind-cli-linux-x64-0.37.0
  • Linux arm64: packmind-cli-linux-arm64-0.37.0
  • macOS arm64: packmind-cli-macos-arm64-0.37.0
  • Windows x64: packmind-cli-windows-x64-0.37.0.exe
  • Windows arm64: packmind-cli-windows-arm64-0.37.0.exe

Make the executable runnable (Linux/macOS):

chmod +x packmind-cli-*-0.37.0

Changes

Added

  • packmind install @space/my-package now installs a released version of a package rather than whatever the package currently holds, and writes that version into packmind.json. With no version after the slug it installs the latest release; @space/my-package:0.1.0 installs exactly that one; @space/my-package:* follows the package as it changes, which is what every repo did before. A version that was never released refuses the install and lists the ones that were, newest first — whether it was typed on the command line or written in packmind.json. A package that has never been released still installs as it stands, under *
  • A packmind.json written before this keeps saying * and keeps behaving exactly as it did: only a package named for the first time, or named with a version, is pinned. Each packmind.json in a repository carries its own versions, so two folders can be on two different releases of the same package
  • packmind install --upgrade moves every package packmind.json pins to a version onto that package's latest release, and writes the version it landed on. A package tracking * keeps tracking it, and is installed the way any install installs it, so its files do not go stale
  • packmind install --check-upgrades shows what --upgrade would change without writing or recording anything. It exits 1 when upgrades are available or a package could not be checked

Changed

  • packmind track and packmind init no longer send a provider vendor guessed from the remote URL: the server works it out from the remote, which is what lets a self-managed GitLab use its connection

Fixed

  • The CLI drops any token embedded in the repository's remote URL before sending it to Packmind
Assets 7
Loading