chore(master): release 0.11.0

[github-actions[bot]]

trafficstars

:robot: I have created a release beep boop

0.11.0 (2024-10-24)

Features

• Cmd-click to jump to a source file from a build rule (#380) (fa38d08)
• codelens: Add a copy target command (da62c67)
• codelens: Don't add target names for one line targets (#407) (4f02dc5)
• codelens: Extend CodeLens to build and run more targets (00d9971)
• coverage: Basic test coverage support (#366) (0d293b8)
• coverage: Demangling C++ & Rust function names in coverage results (#398) (d28c294)
• coverage: Demangling of Java function names in coverage results (#388) (7084368)
• coverage: Load branch coverage from coverage files #389 (e5c95e4)
• syntax highlighting for .bazelrc (#379) (2aea27e), closes #259

Bug Fixes

• buildifier: Handle relative buildifier path without warning #387 (60051c5)
• Change explorer UI label to "Bazel Targets" (#409) (dba3102)
• codelens: Apply commandArgs to run targets (#408) (9c77c18)
• coverage: Do not emit error on BRDA:0 entries (#417) (7f62f0e)
• coverage: Expand external local repo in coverage report (#418) (c115a86)
• Default to Python syntax highlighting theme (#397) (2614f19)
• Link the full label / file name instead of individual components (#382) (2e207c9)

---

This PR was generated with Release Please. See documentation.

[google-cla[bot]]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[hofbi]

@vogelsgesang Is there any plan for when the next release will be made?

[vogelsgesang]

no, we don't have a specific plan, yet.

We are still in an in-between state of transferring ownership of this project from Google to the open-source community. We rely on people from Google to publish the extension to the Marketplace, and this process is a bit cumbersome. And I was hoping that we could first finish the transfer of ownership to the open-source community before cutting the next release.

Do you need an updated release for some reason? In case you only need a version for your own, local usage: Our Github actions actually include .vsix packages (see, e.g., here) which you can install in VS Code

[hofbi]

No urgent need for a new release, just wanted to check in

[rma-stripe]

We've received a few user complaints about the (small) bug that https://github.com/bazel-contrib/vscode-bazel/pull/387 addresses. Similar to hofbi, we are also not urgently in need of release, but an eventual release would be appreciated.