Merge pull request #159 from buildkite-plugins/release/v1.9.0

Bump version in readme

Author: petetomasik

CHANGELOG.md

@@ -6,13 +6,52 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [v1.9.0]
+
+### Added
+* Add step validation to skip invalid configurations with helpful warnings (#158)
+* Add SHA256 checksum verification for downloaded binaries (#155)
+* Add map format support for env configuration with null literal support for reading from OS environment (#154)
+* Preserve and display plugins defined within command steps in README documentation (#157)
+
+### Fixed
+* Fix notify processing in group steps (#156)
+
+## [v1.8.0]
+
 ### Added
-* Accept both `artifact_paths` (preferred) and `artifacts` (alternative) field names in plugin configuration for backward compatibility (#120)
+* Accept both `artifact_paths` (preferred) and `artifacts` (alternative) field names in plugin configuration for backward compatibility (#151)
+* Keep the binary in the plugin directory instead of build directory (#135)
+
+### Changed
+* Update module github.com/bmatcuk/doublestar/v4 to v4.10.0 (#150)
+* Update dependency go to v1.25.7 (#152)
+* Update module github.com/sirupsen/logrus to v1.9.4 (#146)
+* Update dependency go to v1.25.6 (#147)
+* Update buildkite plugin secrets to v2 (#149)
 
 ### Fixed
-* Fix `artifact_paths` field being ignored when specified in plugin configuration. Both `artifact_paths` and `artifacts` now work correctly (#120)
-* Fix typo in test case: "artifiact" → "artifact"
-* Fix BATS test failures caused by unbound `BUILDKITE_PLUGINS_PATH` variable in hooks/command
+* Fix `artifact_paths` field being ignored when specified in plugin configuration (#151)
+* Have `download: false` respect `binary_folder` configuration (#148)
+
+## [v1.7.0]
+
+### Added
+* Add support for `secrets` field in step configuration (#137)
+
+## [v1.6.2]
+
+### Fixed
+* Fix env parsing of complex values with equals signs (#141)
+
+### Changed
+* Update versions in README (#142)
+
+## [v1.6.1]
+
+### Added
+* Add `download` configuration option to support pre-installed binaries (#130)
+* Add retry logic for binary download to handle transient network issues (#138)
 
 ## [v1.6.0]
 

README.md

@@ -45,7 +45,7 @@ For example, in the following configuration:
 steps:
   - label: "Triggering pipelines"
     plugins:
-      - monorepo-diff#v1.8.0:
+      - monorepo-diff#v1.9.0:
           diff: "git diff --name-only HEAD~1"
           watch:
             - path: "**/*"
@@ -125,7 +125,7 @@ The plugin preserves `plugins:` blocks when specified in command step configurat
 steps:
   - label: "Triggering pipelines"
     plugins:
-      - monorepo-diff#v1.8.0:
+      - monorepo-diff#v1.9.0:
           watch:
             - path: services/api/
               config:
@@ -150,7 +150,7 @@ When changes are detected in the watched paths, the plugin generates steps that
 steps:
   - label: "Triggering pipelines"
     plugins:
-      - monorepo-diff#v1.8.0:
+      - monorepo-diff#v1.9.0:
           watch:
             - path: app/
               config:
@@ -181,7 +181,7 @@ steps:
 steps:
   - label: "Triggering pipelines with plugin"
     plugins:
-      - monorepo-diff#v1.8.0:
+      - monorepo-diff#v1.9.0:
           watch:
             - path: test/.buildkite/
               config: # Required [trigger step configuration]
@@ -210,7 +210,7 @@ The plugin supports conditional execution of pipeline steps using the `if` key,
 steps:
   - label: "Triggering pipelines with plugin"
     plugins:
-      - monorepo-diff#v1.8.0:
+      - monorepo-diff#v1.9.0:
           diff: git diff --name-only HEAD~1
           watch:
             - path: services/api
@@ -273,7 +273,7 @@ git diff --name-only "$LATEST_TAG"
 steps:
   - label: "Triggering pipelines"
     plugins:
-      - monorepo-diff#v1.8.0:
+      - monorepo-diff#v1.9.0:
           diff: "git diff --name-only HEAD~1"
           watch:
             - path: "bar-service/"
@@ -300,7 +300,7 @@ A default `config` to run if no paths are matched, the `config` key is not requi
 steps:
   - label: "Triggering pipelines"
     plugins:
-      - monorepo-diff#v1.8.0:
+      - monorepo-diff#v1.9.0:
           diff: "git diff --name-only HEAD~1"
           watch:
             - path: "bar-service/"
@@ -322,7 +322,7 @@ The object values provided in this configuration will be appended to `env` prope
 steps:
   - label: "Triggering pipelines"
     plugins:
-      - monorepo-diff#v1.8.0:
+      - monorepo-diff#v1.9.0:
           diff: "git diff --name-only HEAD~1"
           watch:
             - path: "foo-service/"
@@ -348,7 +348,7 @@ The map format provides clean, readable syntax:
 steps:
   - label: "Triggering pipelines"
     plugins:
-      - monorepo-diff#v1.8.0:
+      - monorepo-diff#v1.9.0:
           env:
             NODE_ENV: production
             API_URL: https://api.example.com
@@ -383,7 +383,7 @@ The array format uses key=value syntax:
 steps:
   - label: "Triggering pipelines"
     plugins:
-      - monorepo-diff#v1.8.0:
+      - monorepo-diff#v1.9.0:
           env:
             - NODE_ENV=production
             - API_URL=https://api.example.com
@@ -423,7 +423,7 @@ Add `log_level` property to set the log level. Supported log levels are `debug`
 steps:
   - label: "Triggering pipelines"
     plugins:
-      - monorepo-diff#v1.8.0:
+      - monorepo-diff#v1.9.0:
           diff: "git diff --name-only HEAD~1"
           log_level: "debug" # defaults to "info"
           watch:
@@ -447,7 +447,7 @@ This option is useful for:
 steps:
   - label: "Triggering pipelines"
     plugins:
-      - monorepo-diff#v1.8.0:
+      - monorepo-diff#v1.9.0:
           download: false
           diff: "git diff --name-only HEAD~1"
           watch:
@@ -477,7 +477,7 @@ To enable checksum verification:
 steps:
   - label: "Triggering pipelines"
     plugins:
-      - monorepo-diff#v1.8.0:
+      - monorepo-diff#v1.9.0:
           verify_checksum: true  # Recommended for enhanced security
           diff: "git diff --name-only HEAD~1"
           watch:
@@ -512,7 +512,7 @@ Add `key` to set the step or group key.
 steps:
   - label: "Setting Key"
     plugins:
-      - monorepo-diff#v1.8.0:
+      - monorepo-diff#v1.9.0:
           diff: "git diff --name-only HEAD~1"
           watch:
             - path: "bar-service/"
@@ -531,7 +531,7 @@ Add `secrets` to inject [Buildkite Secrets](https://buildkite.com/docs/pipelines
 steps:
   - label: "Deploy with secrets"
     plugins:
-      - monorepo-diff#v1.8.0:
+      - monorepo-diff#v1.9.0:
           diff: "git diff --name-only HEAD~1"
           watch:
             - path: "service/"
@@ -548,7 +548,7 @@ steps:
 steps:
   - label: "Deploy with secrets"
     plugins:
-      - monorepo-diff#v1.8.0:
+      - monorepo-diff#v1.9.0:
           diff: "git diff --name-only HEAD~1"
           watch:
             - path: "service/"
@@ -565,7 +565,7 @@ Secrets also work within grouped steps:
 steps:
   - label: "Deploy services"
     plugins:
-      - monorepo-diff#v1.8.0:
+      - monorepo-diff#v1.9.0:
           diff: "git diff --name-only HEAD~1"
           watch:
             - path: "services/"
@@ -588,7 +588,7 @@ steps:
 steps:
   - label: "Triggering pipelines"
     plugins:
-      - monorepo-diff#v1.8.0:
+      - monorepo-diff#v1.9.0:
           diff: "git diff --name-only $(head -n 1 last_successful_build)"
           interpolation: false
           env:
@@ -659,7 +659,7 @@ This is the filesystem folder where the Go binary will be kept.
 steps:
   - label: "Triggering pipelines"
     plugins:
-      - monorepo-diff#v1.8.0:
+      - monorepo-diff#v1.9.0:
           binary_folder: "/var/buildkite-agent"
           watch:
             - path: "bar-service/"