v0.5.2

Introduce kustomize version 5.8.0, making it the new default version.

While here, freshen both the version of Bazel and the Bazel modules used in this repository.

Details

Using modules with Bazel 6 and later

1. Enable support for modules in your .bazelrc file by adding the following line:
   common --enable_bzlmod
2. Add the following directive to your MODULE.bazel file:

bazel_dep(name = "rules_kustomize", version = "0.5.2")

Full Changelog: v0.5.1...v0.5.2

v0.5.1

Introduce kustomize version 5.7.1 and Helm version 3.19.0, making each of them the new default version.

While here, freshen both the version of Bazel and the Bazel modules used in this repository.

Details

Using modules with Bazel 6 and later

1. Enable support for modules in your .bazelrc file by adding the following line:
   common --enable_bzlmod
2. Add the following directive to your MODULE.bazel file:

bazel_dep(name = "rules_kustomize", version = "0.5.1")

Full Changelog: v0.5.0...v0.5.1

v0.5.0

Use the latest available tool releases

Introduce kustomize version 5.7.0 and Helm version 3.17.4, making each of them the new default version.

In order to keep the set of available toolchain versions manageable, remove the following versions:

• kustomize
  • 5.4.1
  • 5.4.3
• Helm
  • 3.12.1

While here, freshen the version of Bazel used in this repository

Details

Using modules with Bazel 6 and later

1. Enable support for modules in your .bazelrc file by adding the following line:
   common --enable_bzlmod
2. Add the following directive to your MODULE.bazel file:

bazel_dep(name = "rules_kustomize", version = "0.5.0")

Full Changelog: v0.4.0...v0.5.0

v0.4.0

Use the latest available tool releases

Introduce kustomize version 5.6.0 and Helm version 3.17.3, making each of them the new default version.

In order to keep the set of available toolchain versions manageable, remove the following versions:

• kustomize
  • 5.0.1
  • 5.0.3
  • 5.1.0
  • 5.2.1
  • 5.3.0
  • 5.4.0
• Helm
  • 3.11.0
  • 3.11.2
  • 3.11.3
  • 3.12.1

Also test against a fresher set of Bazel versions. Drop support for testing against Bazel at version 6, and start testing against version 8.

While here, freshen the version of Bazel used in this repository

Details

Using modules with Bazel 6 and later

1. Enable support for modules in your .bazelrc file by adding the following line:
   common --enable_bzlmod
2. Add the following directive to your MODULE.bazel file:

bazel_dep(name = "rules_kustomize", version = "0.4.0")

Full Changelog: v0.3.10...v0.4.0

v0.3.10

Update set of available kustomize tool versions

Introduce kustomize version 5.4.1, and make that the default version.

Details

Using modules with Bazel 6 and later

1. Enable support for modules in your .bazelrc file by adding the following line:
   common --enable_bzlmod
2. Add the following directive to your MODULE.bazel file:

bazel_dep(name = "rules_kustomize", version = "0.3.10")

Full Changelog: v0.3.9...v0.3.10

v0.3.9

Update set of available kustomize tool versions

Introduce kustomize version 5.4.0, and make that the default version. Remove version 5.0.0.

In the "golden" test output, work around the newly arrived defect described in kubernetes-sigs/kustomize#5642.

Details

Using modules with Bazel 6 and later

1. Enable support for modules in your .bazelrc file by adding the following line:
   common --enable_bzlmod
2. Add the following directive to your MODULE.bazel file:

bazel_dep(name = "rules_kustomize", version = "0.3.9")

Full Changelog: v0.3.8...v0.3.9

v0.3.8

Accommodate file extension variation on Windows

The kustomize project vacillated recently on how it names the kustomize executable tool published in its release archives. Versions prior to 5.2.1 used the ".exe" extension, version 5.2.1 omitted it, and the most recent version 5.3.0 brought it back. Since we still offer to download multiple versions that straddle this range, anticipate that the tool name will vary based not just on the operating system, but also on the version.

Details

Using modules with Bazel 6 and later

1. Enable support for modules in your .bazelrc file by adding the following line:
   common --enable_bzlmod
2. Add the following directive to your MODULE.bazel file:

bazel_dep(name = "rules_kustomize", version = "0.3.8")

Full Changelog: v0.3.7...v0.3.8

v0.3.7

Update set of available kustomize tool versions

Introduce kustomize version 5.3.0, and make that the default version.

Details

Using modules with Bazel 6 and later

1. Enable support for modules in your .bazelrc file by adding the following line:
   common --enable_bzlmod
2. Add the following directive to your MODULE.bazel file:

bazel_dep(name = "rules_kustomize", version = "0.3.7")

Full Changelog: v0.3.6...v0.3.7

v0.3.6

Use the latest available tool releases

Introduce kustomize version 5.2.1 and Helm version 3.13.1, making each of them the new default version.

Details

Using modules with Bazel 6 and later

1. Enable support for modules in your .bazelrc file by adding the following line:
   common --enable_bzlmod
2. Add the following directive to your MODULE.bazel file:

bazel_dep(name = "rules_kustomize", version = "0.3.6")

Full Changelog: v0.3.5...v0.3.6

v0.3.5

Switch GitHub organization to maintainer account

There are no material changes included here apart from relying on a
different GitHub-hosted repository from which to publish releases.

Details

Using modules with Bazel 6 and later

1. Enable support for modules in your .bazelrc file by adding the following line:
   common --enable_bzlmod
2. Add the following directive to your MODULE.bazel file:

bazel_dep(name = "rules_kustomize", version = "0.3.5")

Full Changelog: https://github.com/seh/rules_kustomize/commits/v0.3.5