v0.6.0

Update set of available CUE toolchain versions

Introduce version 0.8.0, establishing it as the new default, as well as making the prior version 0.7.1 available too. In order to keep the set of available toolchain versions manageable, remove version 0.5.0.

In order to accommodate new behavior in version 0.8.0, introduce the "output_package_name" attribute.

Per CUE CL 1177546, allow use of the CUE tool's broadened interpretation of the --package command-line flag, introducing the "output_package_name" attribute on the cue_consolidated_* and cue_exported_* macros to designate into which CUE package to generate CUE code, when the "output_format" attribute's value is "cue".

With this new "output_package_name" attribute available, deprecate the former "non_cue_file_package_name" attribute, intending to remove it entirely in a subsequent release.

Allow generating CUE code with the cue_exported_* macros.

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_cue", version = "0.6.0")

Full Changelog: v0.5.0...v0.6.0

v0.5.0

Update set of available CUE toolchain versions

Introduce version 0.7.0, establishing it as the new default. In order to keep the set ofavailable toolchain versions manageable, remove the alpha versions preceding version 0.6.0.

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_cue", version = "0.5.0")

Full Changelog: v0.4.2...v0.5.0

v0.4.2

Update set of available CUE toolchain versions

Introduce version 0.6.0, establishing it as the new default. In order to keep the set of available toolchain versions manageable, remove version 0.4.3 and the beta versions preceding version 0.5.0.

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_cue", version = "0.4.2")

Full Changelog: v0.4.1...v0.4.2

v0.4.1

Update set of available CUE toolchain versions

Introduce version 0.6.0-alpha.2, retaining version 0.5.0 as the stable
default.

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_cue", version = "0.4.1")

What's Changed

• Ensure that annotated tag content is available by @seh in #6
• Update set of available CUE toolchain versions by @seh in #7

Full Changelog: v0.4.0...v0.4.1

v0.4.0

Merge pull request #5 from seh/update-available-cue-toolchains

Update set of available CUE toolchain versions

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_cue", version = "0.4.0")

What's Changed

• Update set of available CUE toolchain versions by @seh in #5

New Contributors

• @seh made their first contribution in #5

Full Changelog: v0.3.0...v0.4.0

v0.3.0

Mandate use of Bazel version 6.1.0 to rely on bazelbuild/bazel#17279 being available, having removed our local workaround for that problem.

Commits since last release: v0.2.2...v0.3.0

v0.2.2

Propagate tags from top-level rule-wrapping macro invocations to intermediate targets.

Commits since last release: v0.2.1...v0.2.2

v0.2.1

Upgrade Gazelle to version 0.29.0, and update the go.mod file to require Go version 1.17 at minimum in order to maintain compatibility with Gazelle.

Commits since last release: v0.2.0...v0.2.1