Skip to content

Comments

[bazel] Setup workflow to publish to BCR#1639

Open
mmorel-35 wants to merge 2 commits intoemscripten-core:mainfrom
mmorel-35:bcr
Open

[bazel] Setup workflow to publish to BCR#1639
mmorel-35 wants to merge 2 commits intoemscripten-core:mainfrom
mmorel-35:bcr

Conversation

@mmorel-35
Copy link
Contributor

@mmorel-35 mmorel-35 commented Dec 4, 2025

This provide the workflow to publish each new tag to the BCR as it was yet done https://github.com/bazelbuild/bazel-central-registry/tree/main/modules/emsdk

Fixes: #1674

@mmorel-35 mmorel-35 force-pushed the bcr branch 2 times, most recently from f63d8bd to e0ae060 Compare December 4, 2025 07:42
@sbc100 sbc100 changed the title Setup workflow to publish to BCR [bazel] Setup workflow to publish to BCR Dec 8, 2025
Copy link
Collaborator

@sbc100 sbc100 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know much about this stuff I'm afraid. Perhaps @walkingeyerobot can review?

@mmorel-35
Copy link
Contributor Author

The workflow is provided based on https://github.com/bazel-contrib/publish-to-bcr/ and BCR is here

Signed-off-by: Matthieu MOREL <matthieu.morel35@gmail.com>
uses: bazel-contrib/publish-to-bcr/.github/workflows/publish.yaml@v1.0.0
with:
tag_name: ${{ inputs.tag_name || github.ref_name }}
registry_fork: emscripten-core/bazel-central-registry
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@sbc100 ,
You'll need a fork

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is that because the workflow involves sending a PR to the upstream bazel-central-registry?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's my understanding yes

attestations: write
secrets:
# Necessary to push to the BCR fork, and to open a pull request against a registry
publish_token: ${{ secrets.BCR_PUBLISH_TOKEN }}
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You'll need to create a dedicated token

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you tell me the exact steps I need to take here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Signed-off-by: Matthieu MOREL <matthieu.morel35@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[feature request/bazel] integrate GH action for automatic push to BCR on release

2 participants