Documentation
¶
Overview ¶
Command release tags a release of every module in this repository.
The tag names are mechanical: the supported paths share the core's version, the Arrow adapter and the GPU tier carry majors of their own, and each tag is prefixed with its module's directory. Spelling that out by hand five times was the part of releasing that went wrong quietly, so this derives it.
Tagging order does not matter. Each module is checked against the versions its own go.mod names, with the workspace off, and a green check is what licences the tag — see release.Check. Nothing here edits a manifest: a module that needs a newer core says so by failing its check, and that is a change to commit and review, not one to make during a release.
Without -push the command stops after the checks and prints what it would have tagged.
Source Files