this repo has no description
0
fork

Configure Feed

Select the types of activity you want to include in your feed.

cmd/cue: remove all "not yet stable" `cue mod` notes

All of these commands have existed since early 2024.
They have widespread use for authoring and consuming CUE modules today,
so treating them as not stable is not really sensible anymore.

Some of these, like `mod resolve` and `mod edit`, are not nearly as
common as `mod tidy` or `mod publish`. However, they were all added
around the same time and we have no plans to change the design of any.

Signed-off-by: Daniel Martí <mvdan@mvdan.cc>
Change-Id: I3bda58614baab10cb2912b9ca8fc7ae9c4fc8304
Reviewed-on: https://cue.gerrithub.io/c/cue-lang/cue/+/1227722
Reviewed-by: Roger Peppe <rogpeppe@gmail.com>
TryBot-Result: CUEcueckoo <cueckoo@cuelang.org>

-12
-2
cmd/cue/cmd/modedit.go
··· 49 49 The --module flag changes the module's path (the module.cue file's module field). 50 50 The --source flag changes the module's declared source. 51 51 The --drop-source flag removes the source field. 52 - 53 - Note that this command is not yet stable and may be changed. 54 52 `, 55 53 RunE: mkRunE(c, editCmd.run), 56 54 Args: cobra.ExactArgs(0),
-2
cmd/cue/cmd/modfix.go
··· 39 39 40 40 If the module.cue file is already compatible with the new syntax, 41 41 it is just formatted without making any other changes. 42 - 43 - Note that this command is not yet stable and may be changed. 44 42 `, 45 43 RunE: mkRunE(c, runModFix), 46 44 Args: cobra.ExactArgs(0),
-2
cmd/cue/cmd/modget.go
··· 51 51 52 52 See "cue help environment" for details on how $CUE_REGISTRY is used to 53 53 determine the modules registry. 54 - 55 - Note that this command is not yet stable and may be changed. 56 54 `, 57 55 RunE: mkRunE(c, runModGet), 58 56 Args: cobra.MinimumNArgs(1),
-2
cmd/cue/cmd/modpublish.go
··· 64 64 The --out flag can be used to write the module's contents to a directory 65 65 in OCI Image Layout format. See this link for more details on the format: 66 66 https://github.com/opencontainers/image-spec/blob/8f3820ccf8f65db8744e626df17fe8a64462aece/image-layout.md 67 - 68 - Note that this command is not yet stable and may be changed. 69 67 `, 70 68 RunE: mkRunE(c, runModUpload), 71 69 Args: cobra.ExactArgs(1),
-2
cmd/cue/cmd/modresolve.go
··· 50 50 If the --deps flag is provided, all dependencies from the current 51 51 module are resolved and displayed. The --deps flag cannot be used 52 52 with module path arguments. 53 - 54 - Note that this command is not yet stable and may be changed. 55 53 `, 56 54 RunE: mkRunE(c, runModResolve), 57 55 }
-2
cmd/cue/cmd/modtidy.go
··· 42 42 43 43 See "cue help environment" for details on how $CUE_REGISTRY is used to 44 44 determine the modules registry. 45 - 46 - Note that this command is not yet stable and may be changed. 47 45 `, 48 46 RunE: mkRunE(c, runModTidy), 49 47 Args: cobra.ExactArgs(0),