v0.9.0-alpha.1

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

• internal/cueversion: bump fallbackVersion for v0.9.0-alpha.1 by @mvdan in 74fb5cf
• cue/ast: remove ParseIdent and support for quoted identifiers by @mvdan in f8ec1f4
• cue/ast/astutil: stop using the deprecated ast.ParseIdent by @mvdan in 35acbf4
• cmd/cue: deprecate cue somecmd in favor of cue cmd somecmd by @mvdan in e8ecf23
• internal/_e2e: rename CUE_LOGINS to CUE_TEST_LOGINS by @myitcv in ec655a5
• cue/load: obey "all packages" mode when loading files by @mvdan in 623b6a8
• cmd/cue: ignore errors on empty package directories in fmt by @mvdan in 7fcae93
• Revert "tools/flow: check and return errors from task values" by @rogpeppe in ea385fd
• cmd/cue: more modules help by @rogpeppe in cb121f5
• cmd/cue: un-hide login command and update docs by @mvdan in 50ed912
• internal/ci: do not trigger build of tip.cuelang.org by @myitcv in 4aaa2db
• cmd/cue: find packages by canonical path in get go by @uhthomas in b648cf4
• remove unneeded dockerignore file by @mvdan in 5489392
• cmd/cue: various minor cleanups by @mvdan in c248f4e
• cue: remove op type and op-token maps by @mvdan in 93b1a79
• internal/cueversion: bump to v0.9.0-0.dev by @mvdan in a2d2085