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.2.0 #5

Merged

Conversation

cameron-martin
Copy link
Owner

@cameron-martin cameron-martin commented Jan 20, 2024

🤖 I have created a release beep boop

0.2.0 (2024-01-24)

Features

  • Allow specifying location of bazel binary (db62a3a)
  • Use a distinct output base for querying (75b9306), closes #3

Bug Fixes

  • Offset of bare completions (715b519)
  • Use correct workspace root for all bazel invocations (4618755)

This PR was generated with Release Please. See documentation.

@cameron-martin cameron-martin force-pushed the release-please--branches--master--components--bazel-lsp branch 2 times, most recently from 12d7e14 to c69820d Compare January 24, 2024 22:33
@cameron-martin cameron-martin force-pushed the release-please--branches--master--components--bazel-lsp branch from c69820d to 8b3f7e0 Compare January 24, 2024 23:32
@cameron-martin cameron-martin merged commit c4b0940 into master Jan 24, 2024
1 check passed
@cameron-martin cameron-martin deleted the release-please--branches--master--components--bazel-lsp branch January 24, 2024 23:34
@cameron-martin
Copy link
Owner Author

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.

Run bazel in a distinct output base
1 participant