Skip to content

Commit

Permalink
Bumps to v15.0.2
Browse files Browse the repository at this point in the history
  • Loading branch information
d13 committed May 14, 2024
1 parent 765107f commit ba2032e
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 2 deletions.
5 changes: 4 additions & 1 deletion CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,8 @@ The format is based on [Keep a Changelog](http://keepachangelog.com/) and this p

## [Unreleased]

## [15.0.2] - 2024-05-14

- Fixes [#3270](https://github.com/gitkraken/vscode-gitlens/issues/3270) - GitLens erroneously thinks certain branches are worktrees under some conditions

## [15.0.1] - 2024-05-14
Expand Down Expand Up @@ -5349,7 +5351,8 @@ The format is based on [Keep a Changelog](http://keepachangelog.com/) and this p

- Initial release but still heavily a work in progress.

[unreleased]: https://github.com/gitkraken/vscode-gitlens/compare/v15.0.1...HEAD
[unreleased]: https://github.com/gitkraken/vscode-gitlens/compare/v15.0.2...HEAD
[15.0.2]: https://github.com/gitkraken/vscode-gitlens/compare/v15.0.1...gitkraken:v15.0.2
[15.0.1]: https://github.com/gitkraken/vscode-gitlens/compare/v15.0.0...gitkraken:v15.0.1
[15.0.0]: https://github.com/gitkraken/vscode-gitlens/compare/v14.9.0...gitkraken:v15.0.0
[14.9.0]: https://github.com/gitkraken/vscode-gitlens/compare/v14.8.2...gitkraken:v14.9.0
Expand Down
2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
"name": "gitlens",
"displayName": "GitLens — Git supercharged",
"description": "Supercharge Git within VS Code — Visualize code authorship at a glance via Git blame annotations and CodeLens, seamlessly navigate and explore Git repositories, gain valuable insights via rich visualizations and powerful comparison commands, and so much more",
"version": "15.0.1",
"version": "15.0.2",
"engines": {
"vscode": "^1.82.0"
},
Expand Down

0 comments on commit ba2032e

Please sign in to comment.