v0.9.0

Update set of available CUE toolchain versions

Introduce version 0.11.0, establishing it as the new 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.9.0")

Full Changelog: v0.8.3...v0.9.0

v0.8.3

Correct comparison against stamping policy name

Thanks to @bwuerknerTTTech for discovering, reporting, and proposing the fix for this defect, first introduced in commit 03c2ddf.

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.8.3")

Full Changelog: v0.8.2...v0.8.3

v0.8.2

Update set of available CUE toolchain versions

Introduce version 0.10.1, establishing it as the new default. In order to keep the set of available toolchain versions manageable, remove version 0.8.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.8.2")

Full Changelog: v0.8.1...v0.8.2

v0.8.1

Restore WORKSPACE.bazel file for Bazel 6 support

In order to accommodate users with Bazel version 6, we must retain the WORKSPACE.bazel file, even though it's no longer required to be present in Bazel 7.

Note that the Bazel Central Registry (BCR) CI workflow tests with both Bazel version 6 and 7 per the "bazel" matrix entries in the .bcr/presubmit.yml file.

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.8.1")

Full Changelog: v0.8.0...v0.8.1

v0.8.0

Update set of available CUE toolchain versions

Introduce version 0.10.0, establishing it as the new default, removing the prior versions 0.9.0, 0.9.1, and 0.9.2, as none of them could accommodate symbolic links within imported modules that most of Bazel's sandboxing strategies require.

Pertinent URLs to related discussion:

• Thread in the "modules" channel of the "CUE" Slack workspace
• cue-lang/cue#3300

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.8.0")

Full Changelog: v0.7.0...v0.8.0

v0.7.0

Update set of available CUE toolchain versions

Introduce version 0.8.2, establishing it as the new default. In order to keep the set of available toolchain versions manageable, remove 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.7.0")

Full Changelog: v0.6.0...v0.7.0

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