-
Notifications
You must be signed in to change notification settings - Fork 305
[CI] Publish to BCR worklow not working. #776
Copy link
Copy link
Open
Description
Seen in the logs in CI, when publishing opentelemetry-proto 1.10.0 to bcr:
with:
attest: true
attestations-dest: attestations
tag: v1.10.0
module-version: 1.10.0
local-registry: bazel-central-registry
templates-dir: this/.bcr
gh-token: ***
github-repository: open-telemetry/opentelemetry-proto
env:
REGISTRY_BRANCH: main
REGISTRY: bazelbuild/bazel-central-registry
REGISTRY_FORK: open-telemetry/bazel-central-registry
TAG_NAME: v1.10.0
VERSION: 1.10.0
/usr/local/bin/node /home/runner/work/_actions/bazel-contrib/publish-to-bcr/ff2c5e3fe8c3b83678df560bfc1cf4d0ba2eb3e1/dist/cli/index.js create-entry --templates-dir=/tmp/templates-Hl0zi8 --local-registry=bazel-central-registry --module-version=1.10.0 --github-repository=open-telemetry/opentelemetry-proto --tag=v1.10.0
Publish to BCR
Did not find configuration file in /tmp/templates-Hl0zi8; setting defaults
Loading template files from /tmp/templates-Hl0zi8
Creating entry for module version 1.10.0 in bazel-central-registry
Fetching release archive https://github.com/open-telemetry/opentelemetry-proto/archive/refs/tags/v1.10.0.tar.gz
The release archive is missing a MODULE.bazel file! This file is needed to form a BCR entry.
Error: The process '/usr/local/bin/node' failed with exit code 1
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels