Package a build artifact without adding an upload service
LOCAL EXPORT COMPATIBILITY · NOT A MANAGED CONNECTOR
A release download and its verification metadata can become separated.
Try it
Run the private composite action inside a checkout on your own runner. Give it a workspace-relative input file and a new output directory. It writes document.uds, document.uds.html, manifest.json and verification-bundle.json. The action rejects paths outside the workspace and will not overwrite an output directory. It invokes the same canonical adapter as the CLI; it does not create a second signing system. Review those outputs before choosing your own release distribution mechanism.
node packages/udify/src/cli.mjs import github-artifact source-file result.uds UDS node packages/udify/src/cli.mjs verify result.uds
Limits
This is runner-local packaging, not a GitHub attestation, GitHub endorsement or a verified remote workflow. Runner and storage costs remain the operator’s responsibility.
Does the action upload a release automatically?
No. It writes local outputs only; no GitHub API call or artifact upload is included.