Update bazel-contrib/publish-to-bcr action to v0.2.3

Copybara Import from https://github.com/bazelbuild/rules_cc/pull/472

BEGIN_PUBLIC
Update bazel-contrib/publish-to-bcr action to v0.2.3 (#472)

This PR contains the following updates:

| Package | Type | Update | Change |
|---|---|---|---|
| [bazel-contrib/publish-to-bcr](https://redirect.github.com/bazel-contrib/publish-to-bcr) | action | patch | `v0.2.2` -> `v0.2.3` |

---

### Release Notes

<details>
<summary>bazel-contrib/publish-to-bcr (bazel-contrib/publish-to-bcr)</summary>

### [`v0.2.3`](https://redirect.github.com/bazel-contrib/publish-to-bcr/releases/tag/v0.2.3)

[Compare Source](https://redirect.github.com/bazel-contrib/publish-to-bcr/compare/v0.2.2...v0.2.3)

#### What's Changed

- chore(deps): update dependency typescript-eslint to v8.35.0 by [@&#8203;renovate](https://redirect.github.com/renovate)\[bot] in [#&#8203;285](https://redirect.github.com/bazel-contrib/publish-to-bcr/pull/285)
- docs: link to gh workflow examples in rules template by [@&#8203;kormide](https://redirect.github.com/kormide) in [#&#8203;289](https://redirect.github.com/bazel-contrib/publish-to-bcr/pull/289)
- feat: fill substitutions in source.json#docs\_url by [@&#8203;alexeagle](https://redirect.github.com/alexeagle) in [#&#8203;290](https://redirect.github.com/bazel-contrib/publish-to-bcr/pull/290)
- chore: update workflow to point to latest action sha by [@&#8203;kormide](https://redirect.github.com/kormide) in [#&#8203;291](https://redirect.github.com/bazel-contrib/publish-to-bcr/pull/291)

**Full Changelog**: <https://github.com/bazel-contrib/publish-to-bcr/compare/v0.2.2...v0.2.3>

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

â™» **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update again.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

---

This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/bazelbuild/rules_cc).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS44Mi43IiwidXBkYXRlZEluVmVyIjoiNDEuODIuNyIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOltdfQ==-->

Closes #472
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/472 from renovate-bot:renovate/bazel-contrib-publish-to-bcr-0.x c726c36610b0a5bee8abad90c8857fae76a90310
PiperOrigin-RevId: 804339155
Change-Id: I79efe637ca6f5f200f902860a85b8e0e8bf0a568
1 file changed
tree: 1ae6c06526e0591b6a93acbd006628982fd0cf18
  1. .bazelci/
  2. .bcr/
  3. .github/
  4. cc/
  5. docs/
  6. examples/
  7. tests/
  8. .bazelignore
  9. .bazelrc
  10. .gitignore
  11. AUTHORS
  12. BUILD
  13. CODEOWNERS
  14. CONTRIBUTING.md
  15. ISSUE_TEMPLATE.md
  16. LICENSE
  17. MODULE.bazel
  18. README.md
  19. renovate.json
  20. WORKSPACE
  21. WORKSPACE.bzlmod
README.md

C++ rules for Bazel

  • Postsubmit Build status

This repository contains a Starlark implementation of C++ rules in Bazel.

The rules are being incrementally converted from their native implementations in the Bazel source tree.

For the list of C++ rules, see the Bazel documentation.

Getting Started

Add the following to your WORKSPACE file:

load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")

http_archive(
    name = "rules_cc",
    urls = ["https://github.com/bazelbuild/rules_cc/archive/refs/tags/<VERSION>.tar.gz"],
    sha256 = "...",
)

Then, in your BUILD files, import and use the rules:

load("@rules_cc//cc:defs.bzl", "cc_library")

cc_library(
    ...
)

Using the rules_cc toolchain

This repo contains an auto-detecting toolchain that expects to find tools installed on your host machine. This is non-hermetic, and may have varying behaviors depending on the versions of tools found.

There are third-party contributed hermetic toolchains you may want to investigate:

If you'd like to use the cc toolchain defined in this repo, add this to your WORKSPACE after you include rules_cc:

load("@rules_cc//cc:repositories.bzl", "rules_cc_dependencies", "rules_cc_toolchains")

rules_cc_dependencies()

rules_cc_toolchains()

Migration Tools

This repository also contains migration tools that can be used to migrate your project for Bazel incompatible changes.

Legacy fields migrator

Script that migrates legacy crosstool fields into features (incompatible flag, tracking issue).

TLDR:

bazel run @rules_cc//tools/migration:legacy_fields_migrator -- \
  --input=my_toolchain/CROSSTOOL \
  --inline

Contributing

Bazel and rules_cc are the work of many contributors. We appreciate your help!

To contribute, please read the contribution guidelines: CONTRIBUTING.md.

Note that the rules_cc use the GitHub issue tracker for bug reports and feature requests only. For asking questions see: