Skip to content

Commit 3f6ddd6

Browse files
committed
Explain maintenance preview versioning after the source import
Signed-off-by: Ralf W. Grosse-Kunstleve <rgrossekunst@nvidia.com>
1 parent aa9970b commit 3f6ddd6

1 file changed

Lines changed: 8 additions & 1 deletion

File tree

‎ci/README.md‎

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -279,7 +279,14 @@ and `maintenance` describe release roles that can change at the next major.
279279
The standalone `cuda-python` source distribution contains its own small tag
280280
selector map because it cannot import repository CI tooling. The pre-commit
281281
metadata check keeps those selectors, bindings packaging, and the maintenance
282-
preview target aligned with the registry. Run it explicitly with:
282+
preview target aligned with the registry. Copying maintenance files does not
283+
make their old branch an ancestor of `main`, so its later release tags are not
284+
necessarily reachable. Until an appropriate tag is reachable, CI uses
285+
`ci.tools.bindings_scm_version` to create a local preview tag in its disposable
286+
checkout, then lets setuptools-scm derive the version normally. Existing
287+
appropriate tags take precedence. The helper never pushes or moves tags;
288+
local preview builds should use an independent clone so their temporary tags
289+
do not affect other worktrees. Run the metadata check explicitly with:
283290

284291
```console
285292
python -m ci.tools.bindings_config --check-package-metadata

0 commit comments

Comments
 (0)