This release adds initial support for the CUE Central Registry (details below) and includes a number of fixes and improvements.
As a reminder: users can register their projects with Unity, our regression and performance testing setup. Unity is used to ensure that a project's CUE evaluations do not unexpectedly stop working, or regress in terms of performance. It continues to catch multiple issues with each release. Adding your project to Unity not only guarantees that we will not break your tests (if we do, we will work with you to fix your CUE code), but it also helps to improve the quality of each CUE release. Follow this link to learn more about Unity, install it, or get in touch with any questions.
Modules
This release includes experimental support for the CUE Central Registry at registry.cue.works
. We have added a cue login
command to log into the Central Registry via a GitHub account, and other commands know how to use these credentials when talking to the registry.
We will share more details about the Central Registry and support for other login mechanisms in the future. For now, we are looking to get early feedback.
To get started with the Central Registry, we have published a tutorial on working with modules and the central registry as well.
CL 1185280 adds cue help modules
as a high-level overview of CUE modules as well.
Go API
CL 1185281 reverts a change in v0.8.0 to fix valid uses of tools/flow
involving task inputs derived from the evaluation of other tasks.
CL 1185684 removes the last remaining bits of API which supported quoted identifiers, which had already been deprecated and largely unsupported for years.
cmd/cue
CL 1173100 fixes cue get go
to avoid panics when dealing with vendored packages or any type aliases which refer to indirectly imported packages.
CL 1185356 tweaks cue/load
so that cue fmt
is able to format CUE files given directly as arguments even when they belong to different packages.
CL 1185473 deprecates the short-form cue somecmd
in favor of cue cmd somecmd
, as the former caused a number of bugs and slowness when working out which subcommand to execute.
Full list of changes since v0.8.0
cue somecmd
in favor of cue cmd somecmd
by @mvdan in e8ecf23