---
- branch: MAIN
  date: Sun Jan 28 06:47:09 UTC 2024
  files:
  - new: '1.7'
    old: '1.6'
    path: pkgsrc/devel/garden/Makefile
    pathrev: pkgsrc/devel/garden/Makefile@1.7
    type: modified
  - new: '1.7'
    old: '1.6'
    path: pkgsrc/devel/garden/cargo-depends.mk
    pathrev: pkgsrc/devel/garden/cargo-depends.mk@1.7
    type: modified
  - new: '1.7'
    old: '1.6'
    path: pkgsrc/devel/garden/distinfo
    pathrev: pkgsrc/devel/garden/distinfo@1.7
    type: modified
  id: 20240128T064709Z.0cdba50526181667b93c5139f7cdf0e5f30ef125
  log: |
    devel/garden: update to 1.2.0

    Released 2023-01-27 - v1.2.0

    Features:
    - If a garden file has no trees defined at all then an implicit tree called
      `.` will now be synthesized into existence. The presence of this implicit tree
      allows garden files that define just the current directory as a tree to omit
      the entire `trees` section altogether. This consequently makes it easier
      to use garden as a simple command runner because the `commands` section
      is the only section required in order to run `garden` commands.

    - When `garden.root` is not configured `garden` will behave as if
      `garden.root` is configured to `${GARDEN_CONFIG_DIR}`. This allows garden
      files to omit `garden.root` from their configuration in typical scenarios.

    - Configuring `garden.root` to an empty string (`""`) will behave as if
      `garden.root` is configured to the current directory from which `garden`
      was run.

    - When a `garden.yaml` file does not exist in the current directory then garden
      will walk up the file system searching for `garden.yaml` or the name specified
      using `garden -c <name>`. Garden will behave as if it were launched from the
      directory containing the garden file when a configuration file is found.

    - The `GARDEN_CEILING_DIRS` and `GIT_CEILING_DIRS` environment variables can be
      used to limit the `garden.yaml` discovery by preventing `garden` from
      traversing into and beyond the specified directories when discovering garden
      files.

    - `garden exec`, `garden cmd` `garden grow`, `garden ls` and custom garden
      commands can now filter the trees they operate over by passing a glob pattern
      using `-t | --trees` option. These commands will only operate on the trees
      whose names match the pattern. This allows you to specify a garden as the tree
      query and use the full set of environment variables from all trees in the
      query while executing commands over a subset of the trees in that garden.

    - `garden init` will now add the current directory to the `trees` block
      when the current directory contains a Git repository. Use `garden init --empty`
      to disable this behavior.

    Development:
    - The `shlex` dependency was upgraded to `1.3.0`, which includes fixes for
      [RUSTSEC-2024-0006](https://rustsec.org/advisories/RUSTSEC-2024-0006.html) a.k.a.
      [GHSA-r7qv-8r2h-pg27](https://github.com/comex/rust-shlex/security/advisories/GHSA-r7qv-8r2h-pg27).
  module: pkgsrc
  subject: 'CVS commit: pkgsrc/devel/garden'
  unixtime: '1706424429'
  user: pin