Releases: keanemind/jjk
Releases · keanemind/jjk
v0.6.2
@kevin314 and I focused heavily on fixing issues for this release.
- Added debug logging of every invocation of the
jjCLI that the extension performs. You can view this by going to the Outputs view in VS Code and selecting the "Jujutsu Kaizen" output channel.jjinvocations are leveldebug, so to view them, you'll need to change the log level setting in the viewer from the default ofinfotodebug. #27 - Fixed the count badge displayed on the source control view container icon to only include changes in the working copy, not parents. #30 (closes #16)
- jjk now supplies its own config to its
jjinvocations so that user configs don't break jjk functionality. #25 and #31 (closes #13) - Fixed a bug where squashing a file or change in the source control view could lead to indefinite hanging. #33
- Fixed a bug where the gutter diffs would fail to update properly when moving to a change with multiple parents. Now the gutter diffs disappear (rather than showing incorrect diffs) because we don't yet have the ability to compare the working copy against multiple parents. #39
- Moved all VS Code commands from jjk to be under the "Jujutsu" category. This means you can now find all of jjk's commands by typing in Jujutsu in the Command Palette.
- Added support for jj v0.28.0's new
jj statusoutput. #46 - Fixed a bug where abandoning a change while jjk was in the middle of refreshing the source control view could result in the source control view being unable to update until the extension was restarted. #49
- Fixed incorrect added/deleted/modified decorations for files in the Explorer on Windows. #51 (closes #47)
Contributors
kevin314
Assets 3
v0.6.1
- Updated gitignore to include (exclude?) test output (e259706)
- Improved performance by removing unnecessary diff generation (f0570b9)
- Fixed potentially incorrect file decorations during startup (5ac196a)
- Fixed blame annotations not updating properly to the end of the line being edited (22c8e57)
- Fixed wrong file decorations being displayed in Windows (cd4cd2f)
v0.6.0
- Fixed issue where the Source Control view's folders displayed invalid commands (1cadeab)
- Removed extraneous refreshing of the Source Control view (a115d56)
- Added warnings for disabling the Git extension when opening co-located repos (9d57df6)
- Added graying out ignored files in the file explorer (084f575) and (56584ae)
- Fixed file decorations to work around VS Code's event count limit (a79dec0)
- Improved compatibility with the
jjCLI with additional flags (bcb8c38) - Added an extension setting to disable blame annotations (241ed51)
- Fixed issue where diff views failed to work in Windows (6d57db1)
v0.5.2
- Ensured only one SCM refresh operation happens at at a time (4d04f21)
- Temporarily removed file system provider caching until we have proper cache invalidation (6f79965)
- Fixed a memory leak caused by not disposing of parent resource groups (d78222e)
- Shortened file paths displayed in the SCM / Cleaned up usage of URIs (f44cc29) and (d08911f)
- Supported showing the source change for files starting at changes other than the current working copy (781013f)
- Fixed issue when attempting to open the diff of a file that was created or deleted (5500f38)
v0.5.1
v0.5.0
v0.4.3
v0.4.1
v0.4.0
- Added blame annotations in the file editor, showing change authorship per line (adc61cd)
- Added a view to track and manage executed jj operations (CLI commands) with the ability to undo/restore (da18bab)
- Revamped the revision history graph with a new look (and hopefully more intuitive UI) (30d5388)
- Fixed an issue with flickering file statuses (A/M/D/R decorations) (c1f3705)
Note:
The vsix for 0.4.0 is not published here, as there was a breaking bundling issue that's been resolved in v0.4.1.