You can find all notable changes to Bridge For Git Explorer in this document.
- Fixed the 'read our documentation' link in the Bridge for Git Explorer welcome view.
- Fixed an issue that prevented the blame lines from being rendered in the Element change level comparing tabs.
- Added a Git Pre-push hook un-installation ability. You can also uninstall or re-install the Pre-push hook for a particular mapping.
- Adjust Git Pre-push hook installation indication and messages.
- Added a Git Pre-push hook installation detection. You can now automatically install a Git Pre-push hook for a mapping or you can skip installation.
- Added an ability to see a detailed message for each of the status records in the Mapping Activity view.
- Fixed an issue that prevented the Update Processor Group action on the elements, that were newly added to the mapping, from using.
- Fixed an issue with the flickering of the Welcome message in the Elements view during the extension initialization.
- Fixed an issue that led to performance degradation during git branch switching.
- Mapping Activity view default location is changed to the bottom panel.
- Changed the VSCode version requirement. Ensure that you use VSCode 1.82.0 or higher.
- Added proper handling for Bridge for Git and Endevor connection issues related to invalidation of certificate or use of self-signed certificates.
- Zowe Bridge for Git and Endevor profile used for mapping actions are now explicitly reported in the extension logs.
- Fixed an issue with adding element to the mapping operation which falsely reported that a subsystem for the element is not found in certain scenarios.
- Fixed an issue with "Unexpected end of JSON input" pop-up message appearing constantly when switching between the editor tabs in VSCode.
- Bridge for Git mapping activity section. Review the Bridge for Git activity in the currently opened mapping.
- Elements History section in the tree. See the changes and the authors of changes in elements directly in the editor area.
- Specify processor groups for elements feature. Now you can update processor groups for your elements in a VS Code workspace.
- Improved experience with profiles. Zowe V1 and team configuration profiles are still supported but are not necessary for the extension to work.
- Introduced minor logging mechanism improvements.
- Support for Zowe V2 profiles with Team and User Configuration files.
- Support for version 4 of the mapping.json files (Bridge for Git version 2.12.0).
- Support for v1 Endevor REST API (Endevor version 18.0).
- Changed the VS Code version requirement. Ensure that you use VS Code 1.58.0 or higher.
- Removed the outstanding CA reference from the extension description as part of the re-branding effort.
- Added a
Show logsbutton in the notification panel, which enables you to open the output of the extension. - Added a build commit hash to the extension activation message.
- Reworked the documentation by introducing the product name rebranding changes.
- Improved user notifications and log messages.
- Fixed an issue in the URI building process. Characters that may potentially break the building process are escaped.
- Added the compatibility for the latest Endevor WebServices charset response headers
- Added support for the latest version of the BFG mapping configuration
- Added the tree view multi-selection ability
- Added support for the multi-branch & multi-system BFG mappings
- Added support for the HTTPS sessions for the Endevor and BFG connections
- Added progress bars for the long operations
- Fixed the refresh icon in the tree view
- Improved the user notifications and messages
- Improved the internal type system
- Improved the codebase structure. Migrated the content to the monorepo
- Fixed a bug in the display of the license on the Visual Studio Code Marketplace as well as in the Open VSX Registry
- Initial release