step-security/Publish to BCR

Create a new module version entry in a Bazel registry

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Stale
License
None
namedescriptionrequireddefault
attestWhether to generate attestations for files created by Publish to BCR.nofalse
attestations-destDirectory to output attestations to. Attestations are not included in the entry.no""
gh-tokenToken for persisting attestations to the repo. This must be a token with id-token and attestation write permissions.no${{ github.token }}
github-repositoryGitHub repository for the module being published. Used to substititue the OWNER and REPO vars into the source template. Defaults to the repository this action runs in.no${{ github.repository }}
local-artifact-pathA newline separated list of local file paths to scan for artifacts declared in source.json and attestations.json instead of downloading them to compute an integrity checksum.no""
local-registryPath to a locally checked out registry where the entry files will be created.yes
metadata-templateContent of the metadata template. An alternative to supplying a metadata.template.json file in the templates dir.no""
module-rootsA newline separated list of relative paths of modules to publish. Overrides the content of moduleRoots in the configuration file.no
module-versionThe module version to publish to the registry.yes
patchPatch content to apply to the release archive. An alternative to supplying a patches folder in the templates dir. The GitHub action is limited to a single patch input so all patches should be merged into one.no""
presubmitContent of the presubmit. An alternative to supplying a presubmit.yml file in the templates dir.no""
source-templateContent of the source template. An alternative to supplying a source.template.json file in the templates dir.no""
tagTag of the the module repository's release. Used for substitution in the source template.no""
templates-dirDirectory containing BCR release template files: metadata.template.json, source.template.json, presubmit.yaml, patches/. Equivalent to the .bcr directory required by the legacy GitHub app.no""
namedescription
module-namesName(s) of the module(s) from MODULE.bazel, comma-separated
short-descriptionA short, single-line description of the operation, e.g. "Publish foo_module@1.2.3".