Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(master): release 0.11.0 #381

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

github-actions[bot]
Copy link

@github-actions github-actions bot commented Apr 16, 2024

🤖 I have created a release beep boop

0.11.0 (2024-08-13)

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)
  • 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.

Copy link

google-cla bot commented Apr 16, 2024

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.

@github-actions github-actions bot force-pushed the release-please--branches--master--components--vscode-bazel branch 4 times, most recently from f180217 to 0b6aaac Compare April 19, 2024 22:19
@github-actions github-actions bot force-pushed the release-please--branches--master--components--vscode-bazel branch 2 times, most recently from f8a97bb to 8512be7 Compare May 5, 2024 20:02
@github-actions github-actions bot force-pushed the release-please--branches--master--components--vscode-bazel branch 2 times, most recently from 7e214ce to bc153ca Compare May 27, 2024 16:41
@github-actions github-actions bot force-pushed the release-please--branches--master--components--vscode-bazel branch 2 times, most recently from cb51b93 to f1c5242 Compare June 11, 2024 18:45
@github-actions github-actions bot force-pushed the release-please--branches--master--components--vscode-bazel branch from f1c5242 to 01acab7 Compare June 12, 2024 19:54
@github-actions github-actions bot force-pushed the release-please--branches--master--components--vscode-bazel branch 3 times, most recently from d72949c to 392591f Compare July 4, 2024 21:35
@github-actions github-actions bot force-pushed the release-please--branches--master--components--vscode-bazel branch from 392591f to 7e0b13d Compare July 23, 2024 00:08
@hofbi
Copy link

hofbi commented Aug 9, 2024

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

@vogelsgesang
Copy link
Collaborator

vogelsgesang commented Aug 9, 2024

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
Copy link

hofbi commented Aug 9, 2024

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

@github-actions github-actions bot force-pushed the release-please--branches--master--components--vscode-bazel branch from 7e0b13d to d4444d2 Compare August 10, 2024 13:31
@github-actions github-actions bot force-pushed the release-please--branches--master--components--vscode-bazel branch from d4444d2 to 8545c99 Compare August 13, 2024 21:21
@rma-stripe
Copy link

We've received a few user complaints about the (small) bug that #387 addresses. Similar to hofbi, we are also not urgently in need of release, but an eventual release would be appreciated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Feature request: syntax support for bazelrc files
3 participants