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.10.0 #360

Conversation

github-actions[bot]
Copy link

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

🤖 I have created a release beep boop

0.10.0 (2024-04-11)

Features

  • Add bazel.info.workspace command variable (#351) (8ae24cf)
  • Add buildifier Json File Configuration (#357) (afc3aed)
  • Introduce pickTarget and pickPackage command variables (#354) (2ef6d2a)
  • Pick up .buildifier.json configuration from the Bazel workspace root (#350) (c2f3f8c)
  • Support bazel tasks from tasks.json (#346) (f2426e4)
  • Support relative paths for bazel.buildifierExecutable (#350) (c2f3f8c)
  • Support running buildifier through Bazel (#350) (c2f3f8c)

Bug Fixes

  • Activate the extension automatically (#344) (085262e)
  • Add a welcome view to the Bazel Build Targets tree view (#372) (1cbdfd6)
  • Don't wait on the "Buildifier not found" notification (#368) (8b659a2)
  • Enable the "Restart LSP" command only if the language server is enabled (#345) (15793a4)
  • Hide commands which are intended to be command variables (#347) (6d3e988)

This PR was generated with Release Please. See documentation.

Copy link

google-cla bot commented Apr 2, 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 4d19385 to 956afbe Compare April 4, 2024 20:55
@github-actions github-actions bot force-pushed the release-please--branches--master--components--vscode-bazel branch 4 times, most recently from 261ed58 to 68d050e Compare April 9, 2024 17:32
@cameron-martin cameron-martin force-pushed the release-please--branches--master--components--vscode-bazel branch 2 times, most recently from ec0c758 to 9d79ffc Compare April 9, 2024 17:38
@github-actions github-actions bot force-pushed the release-please--branches--master--components--vscode-bazel branch from 9d79ffc to 6a40310 Compare April 10, 2024 21:12
@github-actions github-actions bot force-pushed the release-please--branches--master--components--vscode-bazel branch from 6a40310 to 3fbde5b Compare April 11, 2024 16:08
@cameron-martin cameron-martin deleted the release-please--branches--master--components--vscode-bazel branch April 11, 2024 17:34
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.

1 participant