[email protected]

[publish-to-bcr-bot]

Release: https://github.com/bazelbuild/rules_rust/releases/tag/0.55.0

Automated by Publish to BCR

[bazel-io]

Hello @UebelAndre, @illicitonion, @scentini, modules you maintain (rules_rust) have been updated in this PR. Please review the changes.

[UebelAndre]

Relates to #3327 (comment) I still don't see any pull-requests of sorts for the extra modules. Support would be appreciated!

@fmeum @kormide maybe?

[illicitonion]

Relates to #3327 (comment) I still don't see any pull-requests of sorts for the extra modules. Support would be appreciated!

We'd probably need to push a new tag to trigger PRs, right? Shall we cut 0.55.1?

[UebelAndre]

Relates to #3327 (comment) I still don't see any pull-requests of sorts for the extra modules. Support would be appreciated!

We'd probably need to push a new tag to trigger PRs, right? Shall we cut 0.55.1?

I had deleted the old tag and re-pushed this one. Maybe there's some caching in the bcr publish infra? But it would be nice to get an informed opinion so I don't have to delete any more tags.

edit: "informed" meaning someone who has access to more logs than you and I might 😅

[fmeum]

I don't know what's up. Recreating a tag is usually good enough.

[UebelAndre]

Does anyone know where https://github.com/bazel-contrib/publish-to-bcr dumps it's logs? Where can I see what it's doing when creating the pull request?

[fmeum]

All maintainers should receive an email if it fails. But I don't know whether there are any logs in case it doesn't fail.

[UebelAndre]

This should be rejected in favor of #3359