You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+34-15Lines changed: 34 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,20 +29,37 @@ source-artifact name, and original files authoritative and avoids a second
29
29
runner and artifact download.
30
30
31
31
The standard wheel and Conda builders create a companion for every uploaded
32
-
bundle. The release unit defaults to `wheel:<repository-name>` or
32
+
bundle. The release component ID defaults to `wheel:<repository-name>` or
33
33
`conda:<repository-name>` and can be overridden with `release-unit` when the
34
-
release-platform catalog uses a different ID. The shared action reads exact
35
-
package metadata from the built files and uploads
34
+
release catalog needs to track multiple producer families in one repository as
35
+
distinct components. `release-unit` is the API's historical name for this ID.
36
+
It is a string label, not a file, directory, artifact bundle, or list of files.
37
+
The same ID is written on every primary file in the component and is reused
38
+
across its matrix variants, such as CUDA version, Python version, and
39
+
architecture, so release assembly can group those outputs together. Most
40
+
standard Conda and wheel callers should leave `release-unit` unset. The shared
41
+
action reads exact package metadata from the built files and uploads
36
42
`release-build-output-<artifact-name>`. No release-specific caller
37
43
configuration is required for the standard builders.
38
44
39
-
`custom-job.yaml` remains explicitly opt-in through `release-build-output` and
40
-
also requires `release-unit`, `release-output-directory`, `release-artifacts`,
41
-
and either `release-package` or
42
-
`release-package-file`. Descriptors may name producer-supplied SBOM,
43
-
provenance, and signature sidecars relative to the output directory. Each path
44
-
or glob must resolve to exactly one file; the action never guesses a release
45
-
artifact.
45
+
`custom-job.yaml` remains explicitly opt-in through one `release-build-output`
46
+
JSON object. An empty string disables companion generation. A non-empty object
47
+
requires `component_id`, a non-empty `artifacts` array, and exactly one of
48
+
`package` or `package_file`; `output_directory` defaults to the job's working
49
+
directory. Descriptors may name producer-supplied SBOM, provenance, and
50
+
signature sidecars relative to the output directory. Each path or glob must
51
+
resolve to exactly one file; the action never guesses a release artifact.
52
+
53
+
| Custom-job input | Why and when to use it |
54
+
| --- | --- |
55
+
|`release-build-output`| Supply one complete JSON configuration only when the upload is a release package bundle. Its presence enables companion generation; an empty value disables it. The shared action reports malformed JSON, unknown keys, missing fields, conflicting package sources, and invalid artifact descriptors before materialization. |
0 commit comments