Skip to content

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Jul 31, 2025

🤖 I have created a release beep boop

0.13.0 (2025-09-07)

Features

  • codelens: Sort Bazel build targets by name length in codelens (#464) (3c48c7a)
  • navigation: Add 'Copy Label To Clipboard' to command palette (#467) (edbdffc)
  • navigation: Add "Go to BUILD file" command (66f699c)
  • navigation: Add "Go to Label" command (bc2abea)

Bug Fixes


This PR was generated with Release Please. See documentation.

@github-actions github-actions bot force-pushed the release-please--branches--master--components--vscode-bazel branch 2 times, most recently from 397d1d9 to ee4487b Compare August 5, 2025 22:11
@github-actions github-actions bot force-pushed the release-please--branches--master--components--vscode-bazel branch from ee4487b to ebbd602 Compare September 7, 2025 13:51
@github-actions github-actions bot force-pushed the release-please--branches--master--components--vscode-bazel branch from ebbd602 to 1432ade Compare September 7, 2025 14:48
@cbandera
Copy link
Contributor

@cameron-martin What's your typical strategy/guideline for when to create a new release and are there any further manual steps like testing involved?
If it is not a big deal, I would love to see the new features in a new release soon so I can make use of them is VSCode.
The other PRs that I have open will probably need a few more iterations and I am short on time again this and next week.

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