CrystalDiskInfo 歷史版本列表
更新時間：2019-08-13
更新細節：
What's new in this version:
- Distorted text in text form field (overlapping characters)
- Context menu of form field disappears after a short period of time
- Text get's clipped after TLines are made
- Form editing gets interrupted as soon as tooltip is shown
- Better support for styled checkboxes and radio buttons
- Form field settings get discarded after revisiting the "Properties" dialog
- text changes colour after translation import
- Checkboxes created by Infix don't check/uncheck correctly in Adobe Reader
- Eliminated bogus 'loading bookmarks...' error when opening certain PDFs
- Auto-fit facility was not working correctly in Translate->Local->Import
- interactive form Buttons with icons were not be dealt with correctly
- underlines being inferred incorrectly
- PDF text rendered incorrectly
- backslash disappears when searching and replacing.
- better display of text from TextMaker & PlanMaker from SoftMaker
- Improved display of text added via Bates numbering (font errors)
- Better handling of excessively clipped text - better display and faster editing
- Cannot copy/paste form fields during forms editing
- Tooltips of form objects don't get shown
- Text spacing could be wrong when using multi-byte fonts
- signature image could be wrong size small when inside a form element
- Possible crash when editing a document with TextPlus
- Possible crash when opening PDFs containing very long names
- Better handling of filename with trailing spaces (Windows)
- Text displayed in wrong position if using the 'cm' operator for positioning
- Better handling of PDF with bogus pages
- Coloured pattern doesn't get shown
- Cancel button missing from dialog on Mac during auto-translation
- Possible crash when checking for an active license on start-up
- Missing translation could cause problems using TransPDF from within non-English versions
- Possible crash when doing form editing using German user-interface
- zoom tool not working
更新時間：2019-08-12
更新細節：
What's new in this version:
GitKraken 6.1.1 (64-bit)
Bug fixes:
- Users behind an authenticated proxy will now see a prompt for their credentials inside of the Release Notes & Glo tabs
- Renamed the duplicate GitLab.com option under Preferences → Authentication back to GitLab (Self-Managed)
GitKraken 6.1.0 (64-bit)
New:
- Get out your magnifying glass and prepare to search like you never have before, Detective
- Users can now easily search inside the graph for commits by message, author, or SHA. Access this feature with the keyboard shortcut Ctrl/Cmd + F or click on the toolbar’s search icon. While searching, use Enter or ↓ to view the next result in the graph, or Shift + Enter or ↑ to view the previous result
- New GitHub Actions integration! Users can now add, edit, and delete GitHub Actions workflows inside of GitKraken. The GitHub Actions section will appear in the left panel for repositories with a GitHub upstream or any repository with the .github/workflows directory. Choose from several workflow templates to get started
Improvements:
- We might not have a thunderstone, but we’ve leveled-up GitKraken with these improvements
- The integration tabs under Preferences → Authentication have been changed to a vertical layout
- The merge conflict warning when opening a pull request will now display a list of conflicted files
- An un-bundled version of GitKraken’s strings file has been added. Users can edit/replace for use in non-officially supported languages
- More Keif avatars have been added to profiles
- An option has been added to the Fuzzy Finder to view GitKraken release notes
Bug Fixes:
- Our small yellow friend helped us thunder shock these bugs into oblivion
- Users will no longer encounter the error message caused by .gitignore negation rules, Checkout failed: error matching pattern due to .gitignore, when checking out a branch
- Users can now change the project group name casing when renaming a project group
- When initiating a push and pull request through the context menu, the Pull Request panel will now appear once the local branch has finished pushing to your remote
- The reset branch context menu will now perform as expected after dragging a branch onto another reference in the graph
- We (really) have fixed an issue with authentication for Bitbucket servers when the username is an email address
GitKraken 6.0.1 (64-bit)
New:
- It might take some time to get used to these new powers features, but we’re confident you’ll be shooting webs from your hands in no time
- This one’s for you Aunt May. Users can now configure location notifications in GitKraken by going to Preferences -> UI Preferences -> Notification Location
- The message box for commits is now resizeable
- Users can now use the keyboard shortcut Shift + J (or Shift + ↓) to jump to the parent commit of a selected commit
- Similarly, users can also use the keyboard shortcut Shift + K (or Shift + ↑) to jump to the child commit of a selected commit. No webs required
Improvements:
- Like Spidey’s new suit, it’s as if Stark himself helped with these technical improvements
- The Fuzzy Finder will now filter search results based on frequency of function use
- When you hover over an author/committer name, a tooltip of their email address will display in the commit panel
- A caps lock warning notification will now appear in all password input fields
- A tooltip has been added to Project Groups to display the directory path
Bug Fixes:
- We got some help from our friendly neighborhood Spider-Man to control the GitKraken bug population
- Now, if there is a corrupt reference in the repository, the graph and its branches will still display
- The Commit Changes context menu and button options for submodules will now work properly
- GitKraken will no longer take an extended time to timeout when switching to a tab with an inaccessible remote repository
- Users can now focus the Fuzzy Finder search box by selecting the search commit icon
- Extra new tabs will no longer generate when relaunching GitKraken if you have the Remember Tabs setting disabled
- The Mac keyboard shortcut Cmd + Q will quit GitKraken if Glo is open
- Bitbucket Server users who have email addresses for their usernames can now successfully integrate their repositories
- Merge commits will no longer have unknown authors if the global gitconfig has no email address
- The appropriate branch will now appear in the working directory when performing a branch checkout through the command line
GitKraken 6.0.0 (64-bit)
New:
- No need to keep Tabs on this journey. Launch systems are a go. 3. 2. 1…...
- TABS...sip, ah. The speed and performance improvements involved in v6.0 has finally made switching between multiple repos in the form of tabs possible! Users can also use Tabs to switch between repos and Glo Boards.
- If a merge conflict exists between your source and the target branch, a Merge Conflict Detected! error message will now directly appear in the pull request template panel when attempting to initiate a pull request
Improvements:
- Like a Nascar pit crew, our team spruced up the physical performance of GitKraken to achieve peak racing form. Prepare for lightspeed
- The startup time of GitKraken is up to 2.3x as fast
- The application size has been reduced by approximately 100MB for MacOS users
- It will feel like taking a Buggati for a spin. Checkout in LFS is now 14x as fast
- Newly created pull requests will display much faster
- Toast notifications have been moved from the upper right corner to the lower left corner of the central UI to avoid blocking important information
- File History and Blame views load up to 20x as fast! Top that Usain
Bug Fixes:
- Flash! We’ve zapped these slow pokes out the way
- Users will no longer encounter the error message Cannot read property isGitHookError of undefined when finishing a release branch through GitFlow
- Commits will no longer appear detached from their respective branch if a child commit’s date is older than the parent’s commit date
- Self-hosted remote services with a domain containing a custom port or path will now be supported through GitKraken’s integration feature
- All folders in Tree View can now be expanded
- When using the Bitbucket.org integration, duplicate repositories will no longer appear in the clone menu
- When using the Azure DevOps integration, repositories will be listed alphabetically on the clone menu
- Users with their autoCRLF set to input will no longer have line endings converted to CRLF when resolving a conflict
- Submodules will no longer be not initialized after discarding submodule changes
- Commit message text now wraps correctly inside of the commit message box
Several GPG-related bug fixes have been applied, including:
- All merge conflicts will now be signed after selecting the Sign commits by default checkbox
- The error notification message will be more descriptive when attempting to generate a GPG key with a name not provided in a user’s profile
- If using older versions of GPG, users will no longer encounter a gpg: invalid option --pinentry-mode error notification
- Annotated tags on Windows will now be correctly signed
GitKraken 5.0.4 (64-bit)
- Resolved an issue that prevent GitKraken from opening on RHEL & CentOS
GitKraken 5.0.3 (64-bit)
Features:
- Y’all ready for this? Users may now resize the reference column inside the graph
- Whoop there it is: Favorite repositories are just a keyboard shortcut away. By typing CTRL/CMD + 1/2/3/etc, you will open your favorite repos in the corresponding order
- We know you have that favorite TuneSquid player... Users are now able to reorder favorite repositories
- C'mon, check it out, y'all ready to jam? We added a search filter to the repository management modal
Improvements:
- No more flagrant fouls! Spell-checking has been added to the support and feedback forms
- By typing the keyboard shortcut Ctrl/Cmd + Shift + M, users now have the ability to focus the commit message box. Nothin’. But. Net
Bug Fixes:
- Bitbucket Server users will no longer experience an indefinite hang when opening a pull request or initializing a new repository. Sorry, hang time isn’t allowed on the GitKraken floor
- What’s up doc? The hide/show all tags context menu will now correctly hide and show annotated tags
- NOT. TODAY. Mr. Swackhammer… Commits made with an email address that doesn’t match your GPG key email address will no longer display as trusted
- Keif with the assist! GitKraken now supports different locales of GPG when signing a commit
- Initializing an LFS submodule will no longer cause GitKraken to crash. No more busted brackets workflows around here
- Alley-oop! Performing a pull on a repository with submodules configured with SSH should now correctly update the submodule
GitKraken 5.0.2 (64-bit)
- The error toast Cannot read property 'hostname' of undefined should no longer appear when doing git operations with a SSH key that has a passphrase
GitKraken 5.0.1 (64-bit)
- Rebasing a branch while a WIP node is present will no longer cause GitKraken to get stuck on a loading screen
GitKraken 4.2.2 (64-bit)
- For those of you that didn’t appreciate Inception, we resolved an issue with duplicate repository names appearing in the breadcrumb list when a submodule had the same name as a recently opened repository
- What good is a Blame button when there’s nobody to blame? The History and Blame buttons will now only appear for appropriate files
- We all want to feel welcome, but Keif was getting a little carried away… Now, when opening a repository from the CLI using the -p argument, GitKraken will open the repository instead of the welcome screen
- The History and Blame buttons will no longer throw the error: “File path to get history is required.”
- The error message “GitUrlParse.default.stringify is not a function” will no longer appear when cloning or pushing from a TFS instance
GitKraken 4.2.1 (64-bit)
Improvements:
- GitKraken now ships with a .rpm option for easy installation on CentOS, RHEL, or Fedora
- Two helper processes in GitKraken have been removed. This will reduce GitKraken’s memory consumption
- The keyboard shortcut to open history view has now been changed to Ctrl/Cmd + Shift + H to not interfere with the “Hide” option on MacOS
- The error message for creating a branch that conflicts with a branch directory is more clear
Bug Fixes:
- The Edit on Bitbucket Server button should no longer take users to a 404 page on Windows
- Linux users should now be able to open their terminal from GitKraken
- The Fuzzy Finder and Repository Management modal will now correctly close with the Esc key if no repository is open
- Repositories under a private group on GitLab.com will have their avatar render as the GitLab logo instead of a blank image
- Diffs for rebased commits will no longer display out of order
- The Open with GitKraken context menu option on Windows should now open GitKraken instead of throwing an error message
- The blame & history buttons will no longer appear for untracked files
GitKraken 4.2.0 (64-bit)
Improvements:
- The VSTS integration has been renamed to Azure DevOps and now supports the new URL format (in addition to the older VSTS format)
- You can now access File History and the Blame view from a file’s diff view
Several keyboard shortcuts have been added:
- Fetch (Ctrl/Cmd + L)
- Create a Branch (Ctrl/Cmd + B)
- Open File History in the Fuzzy Finder (Ctrl/Cmd + H)
- A filter bar has been added to the right panel when View all files is selected
- Hovering over a merge commit will now display a tooltip with the commit author’s name
- Hovering over a stash will now display a tooltip with the full name
- Hovering over a repository, branch, or file name will display a tooltip with the full path and name
- When discarding changes to an individual file, the prompt will now display the file name
- The branch “ahead” and “behind” icons have been changed to improve visibility
- The pull request description field can now be expanded
- A filter has been added to the keyboard shortcuts window. This window can be accessed using Ctrl/Cmd + /
Bug Fixes:
- Initializing GitFlow on a repository with an existing local develop branch will no longer throw an error, Failed initializing Git Flow commit.id is not a function
- Lines that would connect reference labels to a commit should no longer appear in the graph if the reference label is hidden
- Launching a terminal from GitKraken will no longer set the NODE_ENV variable to production
GitKraken 4.1.1 (64-bit)
- Change log not available for this version
GitKraken 4.1.0 (64-bit)
- Change log not available for this version
GitKraken 4.0.6 (64-bit)
Improvements:
- Linux users may now notice that there are four builds of GitKraken
- Fedora, CentOS, & RHEL users should utilize the .tar.gz built for Ubuntu LTS 18.04+
Bug Fixes:
- GitKraken will no longer crash on Fedora 28 if a repository that has a SSH remote is opened or cloned
- Resolved an issue that caused the submodule sliding panel to be much more narrow than intended
- Users should now be able to correctly clear out the clone and initialize input fields
GitKraken 4.0.5 (64-bit)
- Readded editor setting to change the font family. Changing this setting will alter the font in the Diff, File, History, & Blame Views
GitKraken 4.0.4 (64-bit)
- Bug Fixes: Temporarily removed editor setting to change the font family to prevent GitKraken from crashing for some users
GitKraken 4.0.3 (64-bit)
Features:
- Added editor settings to change the font size and family. This setting is located under Preferences → Editor Preferences
- Added a setting to remember the last opened repository on startup. This setting is located under Preferences → General
- Added an editor setting and Fuzzy Finder option to toggle syntax highlighting on and off. This setting is located under Preferences → Editor Preferences
- Added a context menu option to delete all branches within a branch folder (local branches only)
- Added the ability to change theme from the Fuzzy Finder
Improvements:
- Using the stage all and unstage all keyboard shortcuts (Ctrl/Cmd + Shift + S & Ctrl/Cmd + Shift + U) will now select the WIP node
- Disabled several keyboard shortcuts when no repository is open
- In the repository management window under the recently opened tab, a browse button has been added if there are no recently opened repositories available
- When viewing a file, Ctrl/Cmd + W will close the file instead of closing the whole repository
- When performing a Fetch or Pull, the text under the loading icon will now reflect which action is being performed
- The prompt to notify a file has been modified externally has been reworked and improved
- The sliding panels for Git Flow, Remotes, Pull Requests, and Submodules have been expanded
Bug Fixes:
- For GitLab.com users, context menus will now be generated for the currently checked out commit
- Tooltips should no longer linger when clicking buttons in the top toolbar
- Unstaging the last hunk of a file would sometimes cause that file not to appear in the unstaged list. This has been fixed
- Esc will once again close the PR panel
- The graph will no longer disappear after creating or editing a file inside of GitKraken
- Resolved an issue that would cause the File View to blank out when staging new additions to a file
- When using Glo inside of GitKraken, Ctrl/Cmd + / will no longer open both GitKraken and Glo’s keyboard shortcut menus
- The discard button should no longer cause the commit panel to shift when multi-selecting files in the staging/unstaging panes
GitKraken 4.0.2 (64-bit)
Improvements:
- When viewing a diff, users may now highlight lines to be staged, unstaged and discarded
- We changed the appearance of the Push and Pull icons. The new icons should no longer cause users' eyes to bleed
- Removed the Blame option for binary files
- Staging files quickly will no longer display a File contents are unchanged message
- Removed several actions from the Fuzzy Finder when no repository is open
Bug Fixes:
- The Stage all changes button should correctly appear after hitting the Mark all resolved button during a conflict
- An error toast will no longer appear after navigating to a commit from File History
- An error toast will no longer appear after switching to File View when viewing the diff of a submodule
- When creating a Feature, Hotfix, or Release branch in Git Flow, the text will now appear correctly in the input field
- After saving a file in the editor, the top toolbar will no longer flash like a strobe light
- The tooltip for hosting service icons, on the new landing page, will now correctly display the service's name instead of GitHub
GitKraken 4.0.1 (64-bit)
Bug Fixes:
- "...a glitch in the Matrix. It happens when they change something." The edit profile modal has been cleaned up
- "Choice. The problem is choice." There will now be a default diff view mode selected
GitKraken 3.6.6 (64-bit)
Improvements:
- Addresses the git vulnerabilities identified in CVE-2018-10887 and CVE-2018-10888
Bug Fixes:
- Windows users experiencing an Assertion Failed! error for git_revwalk_hide should no longer receive this error
Enterprise:
- v3.6.6 does not include any changes to GitKraken Enterprise other than those listed above
GitKraken 3.6.5 (64-bit)
Improvements:
- Addresses the git vulnerabilities identified in CVE-2018-10887 and CVE-2018-10888
Bug Fixes:
- Windows users experiencing an Assertion Failed! error for git_revwalk_hide should no longer receive this error
Enterprise:
- V3.6.5 does not include any changes to GitKraken Enterprise other than those listed above
GitKraken 3.6.4 (64-bit)
Improvements:
- There are never too many places to add help instructions, so keyboard shortcuts are now accessible from the help menu.
- Like a veteran camera man tracking a through ball, checking out a branch through the Fuzzy Finder will now scroll the branch into view.
- GitLab.com users with private remote repositories will now display a placeholder icon instead of a blank box...a keeper, if you will.
Bug Fixes:
- Hopefully we've fixed this one for good! Resolving merge conflicts on Windows should no longer result in the file getting CRLF line endings.
- On Windows, selecting View all Files when viewing a commit diff should correctly display in Tree View. Or, if you're watching Mexico play, El Tri view.
- Two World Cups games at the same time: Awesome; Two scroll bars at the same time: terrible. Long commit messages will no longer have double scroll bars when viewing the diff of a file.
- Can you imagine if two goals by the same player canceled each other out? A Pull Request with the same name as an existing Pull Request will now display, instead of appearing blank.
- Accurate passing is key to any match. When opening a Pull Request in GitKraken, using Tab will now jump to the next field instead of selecting users or labels from the dropdown menu.
- Pushing is grounds for a yellow card, so repositories with long names will no longer overflow in the repository bread-crumb menu.
Enterprise:
- Like a super sub fresh off the bench, Enterprise clients that are launched in an offline environment should load significantly faster.
GitKraken 3.6.3 (64-bit)
Improvements:
- This release addresses the git vulnerability that was recently identified in CVE-2018-11235
- GitKraken is not susceptible to CVE-2018-11233
GitKraken 3.6.2 (64-bit)
Bug Fixes:
- Hashtags are not just a commenting device: lesson learned. Commit messages with a # will now only be commented out if the new comment option is enabled in your Preferences > Commit Template settings
- Discarding or resetting an untracked or renamed file will no longer throw an error, especially since the action completes successfully
Enterprise:
- v3.6.2 does not include any changes to GitKraken Enterprise other than those listed above
GitKraken 3.6.1 (64-bit)
Improvements:
- You may now disable spell check from Preferences > UI Preferences, and of course tell everyone about your spelling bee championship at Lincoln Elementary
Bug Fixes:
- If you installed the Linux .deb package recently, you may have noticed that GitKraken was not installed into your system path. We fixed that by pointing Keif back to the proper location
Enterprise:
- We popped the hood and made a change that allow more memory allocatation when syncing with large LDAP environments
GitKraken 3.6.0 (64-bit)
Features:
Mission Control, we are a go for total pull request management! Users can now do the following when creating a pull request through GitKraken:
GitHub.com & GitHub Enterprise:
- Add assignees
- Add reviewers
- Add labels
GitLab.com & GitLab Self-hosted:
- Add an assignee
- Add labels
- Is your pull request go for launch? GitHub users: GitKraken will now display the status of pull requests in the left panel. Hovering over a pull request will provide a summary of information on a build’s status
- Typos can be costly, so we’ve added spell checking to the commit message box, pull request panel, and the commit template field
- Quickly propel yourself into your repo folder from the new file menu option that allows you to open your repository folder in your default file manager
- You can also use the keybind Alt + O.
- Reduce the drag on your graph by using the new context menu option to Hide all tags
Improvements:
- Looking for more pull request info on the fly? Tooltips for open pull requests have been redesigned and should be easier to read
- GitKraken will now display tag annotations. Let everyone know how amazing your code is
- Selecting the button from the Clone window will now take users to the hosting service tab instead of the general authentication tab
- Switch repos at light speed! Ctrl/Cmd + Shift + O now opens the Fuzzy Finder with the open repo option preselected
Bug Fixes:
- You shouldn’t be faulted for writing a thorough commit message, so we resolved an issue that prevented users from accessing their submodules if the last commit message was very long
- Amending a commit message using the commit keyboard shortcut should properly amend the commit instead of creating a new one
- We managed to fit this one in: long branch names will no longer go off of the Git Flow panel
- [GitLab Self-Hosted] users: Initializing a public repository through GitKraken would actually make the repository private; this has now been fixed
- We’re all for resolving conflicts, especially ones that aren’t really there. For repositories on FAT32 or NTFS drives, GitKraken should now correctly checkout the branch instead of throwing conflict errors
GitKraken 3.5.1 (64-bit)
- Bug Fixes: GitKraken should now be able to connect to GitLab self-hosted servers with self-signed certificates, again
GitKraken 3.5.0 (64-bit)
Features:
- Presto! Commit message D-N-A! You can now create commit message templates for each of your repositories
- For those times when you can’t network eight connection machines and debug two million lines of code all on your own, GitKraken will now display co-authored commits
Improvements:
- Looking for that perfect iteration? We’ve added a context menu option to copy a commit SHA
- Buried repos should stay buried; so GitKraken will no longer display archived GitLab repositories in the clone window
- Since you can’t discard and stage hunks when viewing the diff of an untracked, removed, or renamed file, we’ve eliminated the temptation by removing those buttons
- We consulted a mathematician and fixed the selection algorithm for unstaged/staged files, so it now respects Z-A sorting
- Must code faster, must code faster! GitKraken will now perform an LFS pull after a clone or submodule initialization, when necessary
- You don’t always have to force reboot the system, but you might need to force push some commits. For VSTS users, force pushing to a branch when you do not have the force push permission enabled will now provide a more detailed error message
Bug Fixes:
- That is one big pile of commits. The squash option should now appear after rebasing commits
- Life...finds a way... Just like Keif has found a way to fetch PRs from a repository that is in a nested group on GitLab
- T-Rex is much shorter, but we realize you can’t always abbreviate. Profiles with long email addresses and names should no longer be cut off in the dropdown menu
- Nuh-uh-uh, you didn’t say the magic word! The Repository Management window will no longer freeze up after removing an account from the initialize repository form
- WIP changes shouldn’t go extinct. Starting a new Gitflow branch would cause some WIP changes to vanish—that should no longer happen
- Commit selection shouldn’t have to be explained by chaos theory. So Shift + click between two commits should now select all commits in between the selection instead of randomly omitting a few
GitKraken 3.4.1 (64-bit)
- Bug Fixes: GitKraken should no longer throw the following error when fetching pull requests from VSTS: Fetching pull requests failed. A project name is required in order to reference a git repository by name
GitKraken 3.4.0 (64-bit)
Features:
- From the depths, a magical window has opened! GitKraken now integrates with Visual Studio Team Services (VSTS)! GitKraken Pro feature - Upgrade now to access!
Improvements:
- We like to Add/Remove Programs, too, so GitKraken now supports Araxis and P4Merge as external diff/merge tools
- For the hover explorers out there, a tooltip has been added to the green check mark in the left panel
Bug Fixes:
- Integration help links will now send you to the correct support page instead of a 404 page...and it wasn’t even the fun 404 page; our apologies!
- Resolved an issue that prevented GitKraken from opening repositories that had a tag named X. You probably figured it was the ‘X’ tag in your repo, huh
- Toss those unwanted hunks out the window with confidence! Discarding hunks on Windows will no longer add LF line endings to a file with CRLF endings
Enterprise:
- Beta Feature: GitKraken Enterprise can now be configured to use LDAP as an alternative authentication method
GitKraken 3.3.4 (64-bit)
Features:
- You might see a shiny new menu button. Only click it if you're ready to Glo!
Improvements:
- When discarding a single file through the context menu, you’ll now see a confirmation prompt: also known as the ohnoididntmeantoclickthat prompt
GitKraken 3.3.3 (64-bit)
Features:
- Keif’s New Year’s resolution was to be less secretive. So, hovering over a repository in the breadcrumb menu will now display a tooltip with the repository’s full path.
Improvements:
- After some year-end reflection, Keif decided that when staging or unstaging from a list of files, GitKraken will now select the next item in the list instead of selecting the first file in the list.
Bug Fixes:
- The feedback and support forms should no longer feel laggy when writing in the subject field… We do want your feedback, we promise
- Scrolling through the Fuzzy Finder with your mouse wheel should now work as intended and not—you know—erase the results and act all weird
- Making changes requires commit-ment, so we resolved an issue that prevented some users from entering a commit message after popping a stash
- After staging, unstaging, or discarding all hunks and lines for a given file, GitKraken will no longer get stuck on a loading icon when trying to display the next diff. New year, new kraken! Keif will move on. ??
- To make a change, you need to start from the beginning. So when editing a submodule’s URL, the cursor will no longer jump to the end of the URL
- Wiki repos on GitLab are special. We know this now, and GitKraken will no longer display a “Fetching pull requests failed” toast when performing a fetch on a GitLab self-hosted Wiki repository
GitKraken 3.3.2 (64-bit)
Bug Fixes :
- Users running Git hooks on OSX High Sierra may now commit. We've figured out our commitment issues
Enterprise:
- v3.3.2 does not include any changes to GitKraken Enterprise other than those listed above
GitKraken 3.3.1 (64-bit)
Features:
- Lost in a holidaze of commits? There's now a Fuzzy Finder shortcut to view working directory changes
Improvements:
- For our ambitious GitLab integration users with more than 100 repositories, you should now be able to see all repositories
- feature/cantremember? When creating a branch or tag, GitKraken will now leave the input field open if you navigate to a different window
- We removed some of the...grey areas (sigh) by replacing the greyed-out placeholder text with actual placeholder text in the Clone and Init repository windows
- We know everyone loves a cryptic error message, but they are now more descriptive when trying to initialize a repository on GitLab EnterpriseSorry not sorry
Bug Fixes:
- We realized you need more than one character for a commit message, so GitKraken now allows users to write a full commit message after undoing a commit.
- When fetching from a GitLab repository, with merge requests disabled, an error message would appear saying it could not load your merge requests… GitKraken now understands this is the same as informing someone that something divided by 1 is itself
- GitKraken will now properly cache group information for GitLab instead of constantly pestering the server about the same groups.
Notes:
- Remotes on GitLab self-hosted accounts will now display the GitLab icon instead of the associated remote avatarTrust us, it's better this way.
Enterprise:
- v3.3.1 does not include any changes to GitKraken Enterprise other than those listed above
GitKraken 3.3.0 (64-bit)
Features:
- GitKraken now integrates with GitLab Community Edition and Enterprise Edition (Pro users only).
Improvements:
- When renaming a branch, the current branch name will now pre-populate the input field.
- We’ve added a context menu option to copy a file’s full path from the commit panel.
- Hovering over a user’s gravatar in the graph will now display a tooltip with that user’s name (or email if no name is provided).
- A loading icon has been added to the clone repository window; it displays while GitKraken is retrieving your remote repositories.
Bug Fixes:
- New connections to GitHub Enterprise no longer require GitKraken to restart
- Pull requests on GitHub.com with multiple assignees will now show all assignees in the tooltip and consistently display in bold when you are one of the assignees. (Previously, it would only bold if you were the first assignee.)
- Users will no longer be prevented from discarding changes for a removed file
- In tree view, the commit panel should now properly display which files have been added/modified/removed/renamed while navigating through the graph
GitKraken 3.2.2 (64-bit)
Features:
- Got GitLab.com? Now you may create a pull request and add a remote from GitKraken
Improvements:
- The currently opened repository is part of the repository management window
- Esc will close the Gitflow and pull request panels
- Attempting to delete a primary remote branch now creates a specific error message
Bug Fixes:
- Cloning and working with a LFS repository on Linux via SSH works now
Enterprise:
- v3.2.2 does not include any changes to GitKraken Enterprise other than those listed above
GitKraken 3.2.1 (64-bit)
Bug Fix:
- Fixed a bug in analytics that caused certain clients to over-report analytics data
GitKraken 3.2.0 (64-bit)
Features:
- If you have children, it’s usually a bad idea to have a favorite child. With GitKraken, it is totally fine to have a favorite repository, and thus we introduce you to the new Favorites list!
- Multi-select for discarding changes: like multi-select for Staging and Unstaging, but with Discard. We’ve added a context menu, too, so now you may discard all changes within a folder if you are in tree view. Brought to you by popular demand- we know how much you love multi-select!
Improvements:
- We’ve added a context menu option for updating submodules
- Now use Ctrl+D(Windows/Linux)/Cmd+D(Mac) or the Fuzzy Finder to open your configured external diff/merge tool
Bug Fixes:
- GitKraken no longer displays a Pushed Successfully message if a push fails due to a server hook. In other words, force-pushing to a protected branch will now display an error message instead of a false “success” message
- We resolved an issue that would cause GitKraken to launch outside of your window region. Sorry about that, it won’t happen again
- Hitting the cancel button when trying to finish a Gitflow action (Hotfix, Release, or Feature) now properly closes the Gitflow window (instead of doing nothing)
- Discard all now discards submodule changes, too
- GitKraken now correctly applies the operating system’s newline character when modifying a repository’s .gitignore file
Enterprise:
- v3.2 does not include any changes to GitKraken Enterprise other than those listed above
更新時間：2019-08-12
更新細節：
What's new in this version:
- Added HiDPI support for Task Tray Icon (from 16×16 to 32×32)
- Added Green Mode support for Task Tray Icon
- Fixed Temperature Color for Main Dialog and Task Tray Icon
- Alert Temperature >= Current Temperature : Red
- Alert Temperature < Current Temperature : Blue or Green
更新時間：2019-08-12
更新細節：
What's new in this version:
SmartGit 19.1.1
Fixed Bugs:
- Commit, Discard: invoking Compare for renamed file does not show source file, but only empty file
Git-Flow:
- Integrate did not honor custom base (if configured)
- Start Hotfix fails if an unrelated version-tag is present
- Start Release may suggest invalid (already existing) release name
- Tools: tools with only ${dirSelect} did not show up in menu
- Startup: under certain conditions always asks for confirmation to send bug traces
SmartGit 19.1.0
- GitLab: Open-link did not work for repositories in subgroups
SVN:
- Cloning created 2 smartgit-*.tmp files in repository
- Duplicate tooltip in the status bar while cloning
GUI:
- Docking: unmaximizing a view with double click could close another view
- If its (X) button was positioned at the same location
SmartGit 18.2.9
Fixed Bugs:
- Git-Flow, Finish Hotfix: when using external Git-Flow no "version tag" is created
- Support for new BitBucket API
SmartGit 18.2.8
New Features, Improvements:
- SSH: support user names wrapped in single-quotes, e.g. ssh://'[email protected]'@server:1234/path
Fixed Bugs:
- Linux launcher: only enforce GTK_IM_MODULE=ibus if it was set to xim
- macOS: an update of the installation bundle caused a directory to remain
Other Noteworthy Changes:
- increased version of bundled Git to 2.21.0
SmartGit 18.2.7
New Features, Improvements:
Git:
- Log: improved error message for "Inconsistency between (cached) commit data detected"
- https: added low-level property connection.https.trustedFingerprints to work around certificate problems with self-signed certificates and proxies
- SSH: authentication-related errors are reported now on re-occurring credentials dialog
Fixed Bugs:
Git:
Log:
- Refresh: false-positive "repository has an error-prone admin area configuration" message for submodules in worktrees
- setting smartgit.log.hostingProviderIntegrationEnabled=true should not disable Distributed Review add-on
- Repositories: opening a repository opened already in another window (working tree or log) causes internal error if renamed or deleted on disk (missing repository)
- Repository Settings on missing repository might cause internal error
Working Tree:
- Merge and other commands with embedded log: branch selection dialog should not hide remote, tracked branches
- Check for New Version: broken if "Automatically download and install updates" has been selected in the preferences
- Docking: maximizing and restoring one view by double clicking its title restores the wrong (too old) size
SmartGit 18.2.6
New Features, Improvements:
Git:
- Fetch (background): continues with next submodules if one failed
- Git-Flow: added low-level property gitflow.integrate.shortMergeMessage
- Journal: added low-level property journal.defaultAuxiliaryRef
Log:
- Repositories: disallow to delete submodules
Fixed Bugs:
- Commit: error "Cannot read file .../.gitbugtraq" if content is invalid
Log:
- Details: unexpected ID detection inside words
- Distributed Reviews: trying to reveal comment failed with "Comment ... could not be revealed"
- File log: Window | Repositories caused internal error
- mergable coloring used hard-to-see color for anchor in dark theme
Refresh:
- possible internal error have a large amount of renamed files
- low-level property "log.wt.refreshOpenButUnselectedModels did not work on nested roots
Working Tree:
- Show Changes: Compare with Each Other did not work for files from different repositories
- delete on submodule did not work anymore
- startup: command line parameter "--investigate" was broken
- unmodified SVN submodules in non-SVN parent repositories showed up if "Show Unchanged Files" was unselected
- JIRA/Bitbucket Server/GitLab: problems when trying to access servers which only support a limited set of ciphers (elliptic curves); installation upgrade is required!
- Windows bundles: fixed outdated readme.txt
SmartGit 18.2.5
New Features, Improvements:
Git:
- Gerrit added low-level property gerrit.checkCommitMsgHookContent to avoid false-positive Gerrit detection
Log:
- Branches, Checkout added low-level property log.checkout.forceSelectionOfBranchAnchor
- Linux startup script easier switching back to GTK2
Fixed Bugs:
Git:
- Commit Amend-option was disabled for merge
Log:
- Commits view revealing HEAD should always reveal HEAD and not stay at working tree node (e.g. double-clicking from Journal)
Refresh:
- log.wt.refreshOpenButUnselectedModels broke refresh of commits breaks in case of invalid Bisect configuration (missing "start" branch)
GUI:
- Customize Accelerators dialog internal error if a filtered-out accelerator is cleared by setting another Compare/Merge, Apply Selection possible internal error if all was selected
SmartGit 18.2.4
New Features, Improvements:
Git:
Log:
- Details view: added low-level property
- Log.details.onlyShowActualCommitRefsWhenFiltered
Hg:
- Support for Mercurial 4.8.*
Fixed Bugs:
Git:
Log:
Commits view:
- Reordering commits did not preserve selection
- Rebase/cherry-pick by drag & drop was broken
- When filtering, "actually on commit"-marker for refs (brighter box) was not properly evaluated
Branches view:
- Reveal after Checkout did not work for behind branch with
- "Just Checkout" option
- Checking out a branch should not reset a manually changed
- Selection
External tools: incorrect parameter "--defaultsVersion" (instead Of "--version") for "Show Git Version" tool (regression)
- Working Tree Window, Files view context menu: LFS submenu might
- Have been empty (if LFS was not yet installed)
- MacOS: warning about default osxkeychain credential helper
Hg:
- Possible performance problems with many draft commits in a Repository with many merges
- Startup: possible internal error when specifying invalid value for
- Low-level property ui.verboseDate.weekdayFormat
GUI:
- Changes view: scrolling with mouse-wheel over connector selected
- Next tab (if there were multiple tabs)
- Customize accelerators: did not warn about duplicate accelerators
- If the commands where invisible because of filtering
SmartGit 18.2.3
New Features, Improvements:
Git:
Log:
- Added low-level property log.dragAndDrop.offerAdvancedOperationsForDropsOntoAncestors to allow drag and drop for advanced rebase and cherry-pick operations
- Open File Log reuses Branches view selection from repository log
Repositories view:
- Select the current repository only if another repository or group was selected before (but, e.g., no subdirectory)
Fixed Bugs:
- Compare, Apply Selection: internal error applying change from an inserted block
Git:
Log:
- Git-Flow Light: for various command dialogs "Fetch" options were disabled
- Pull: "Update existing and fetch new tags" did not work for Git >= 2.20
- Refresh: obsolete modified working tree overlaps new commit for a short time, then vanishes
Working Tree window:
- Changes were not reported gradually anymore
GUI:
- Several views: tab order cycled between table and search input field
- Find Command, Find Object: shortcuts were swapped
SmartGit 18.2.2
New Features:
- Repositories: added low-level property log.wt.refreshOpenButUnselectedModels
- To update the repository state of open, but not currently
- Selected repositories
- Pull with rebase, merge commit: added low-level property
- Pull.rebase.mergeCommit.mergeOrRebase to avoid merge-or-rebase dialog
Fixed Bugs:
Changes:
- Index content might not have been displayed if file was
- Case-changed in working tree
- Staging hunk for case-changed file did not work
Commits:
- Filter broke after changing low-level property
- Log.graph.graphicalFiltering in the preferences
- Switching branches lost Working Tree/Index selection
- File/Subdir log did not remember layout
- Repositories: state got lost when opening multiple repositories
- At once and having "Show Working Tree & Index Permanently"
- Selected
- File Compare: forgot about BOM
SmartGit 18.2.1
Git:
- Added low-level property log.graph.workingTreeAutoSelectionForConflicts to disable auto-selection of the working tree node if conflicts were detected
GUI:
- Added low-level property ui.fonts.useDefaultAsInfo to make the info font the same as the default font (instead of a tinier, derived one)
Fixed Bugs:
- Clone listed only own repositories, but should have listed all with read-access ("member" role)
- GitHub/GitLab/BitBucket integration: internal error trying to merge on server
- Log - resettings filter should not auto-select Working Tree or Index node
- Repositories - could not invoke Pull/Push commands on group
Preferences:
- Proxy port was not remembered after switching off the proxy temporarily
SSH
- Some special SSH server setups caused an error "ClassNotFound:
- Org.ietf.jgss.GSSException" to be raised => these users should force an installation update from the About dialog using the button right beside the version text field
GUI
- Update check: multiple "The upgrade to version x is not covered by your license" notifications showed up
SmartGit 18.2
Fixed Bugs:
Git:
Log:
- Branches view: Ctrl+C did not copy ref name
- Changes view (Windows): old file content does not show up for case-changed files
- Push to Gerrit: should be available in case of multiple Gerrit remotes (if sill unique)
SmartGit 18.1.5
New Features and improvements:
Git:
- Push to Gerrit: if topic is entered, add topic to master-option, like "refs/for/master%topic=topic"
Fixed Bugs:
Git:
- Gitignore/Git-config editor: is bright even with dark theme
- Find Objects: possible internal error when entering a long search string
- Refresh/Log: rename detection limit should be 50% by default (as for Git)
Hg:
- internal error if no Git executable is configured
- startup: possible internal error related to a bad settings.xml
SmartGit 18.1.4
- Change log not available for this version
SmartGit 18.1.3
Git (Log):
- Refresh: improved error message in case of bad stash-reflogs revealing a ref in an existing, filtered log window now resets the filter Updated bundled Git to version 2.17.1 (macOS, Windows; needs new installation or manual triggering of a genuine update in the About dialog)
- Bitbucket integration: improved error reporting
- Output dialog: remembers size (and location)
- Some hosting providers: added low-level property "json.enableGzip" to enable GZIP compression
- Setup wizard: added option to use gravatar.com (in the preferences, it was moved from the Commands > Log page to the Privacy page)
Fixed Bugs (Git):
- Commit Message view: entered message was not stored in the history
- Ignore: internal error trying to ignore directory with certain special characters like '[' in its name
- Local | Rename: allowed to rename the . directory
Log:
- internal error switching back from "Varying Coloring" to "Root Coloring" toggling individual pull requests did not work
- Log/Journal: - right-clicking an unselected commit showed commands for previously selected commit (Linux, macOS)
- Refresh: possible error for files with name "aux" (Windows)
- Stash Selection: failed with quotes in the message
- Bitbucket integration: problems parsing multiple reviewers
- GitHub integration (main window): certain errors were not reported
- GitLab integration: API version v3 is not supported any more
SSH:
- recurring error "The fingerprint of the SSH server has changed"
- an invalid .ssh/known_hosts file might show a lot of notifications about the failed read
- Tools: internal error invoking tool on repository located on drive root (Windows)
- Upgrade (Windows): possible "The process cannot access the file because it is being used by another process" error
SmartGit 18.1.2
New Features and improvements:
Git:
- Log: re-introduced former "varying" coloring
- added low-level property compare.gitCompatibleBinaryDetection
Fixed Bugs:
Git:
- interactive rebased timed out after 2min (Windows)
Journal/Log:
- possible "Node ... not found" error when opening repository
- right-clicking loses selection if scrolled down
- Rebase Head To: "Can't rebase HEAD to HEAD or an anchestor commit" error if
- HEAD is hidden
Hg:
- Conflict Solver: did not open for graft-conflicts
- Log: internal error when opening in Rebasing state
- SSH: certain problems with private key authentication (depending on files
- parallel to the provided private key file)
Linux bundle:
- added work-around for reg-ex related Java crashes caused by syntax
- highlighting code
- DEB bundle did not start on Ubuntu 18.04
SmartGit 18.1.1
New features and improvements:
Git:
- Git-Flow: if the low-level property gitflow.requireCleanWorktreeOnStart is set to true, starting a feature or hotfix with local changes will abort
- Log: if low-level property log.graph.displayCommitDateForAuthor is set to true, it will show the author, but the commit (instead of the author) date
- Output: if low-level property output.showOnlyIfViewInvisible is set to false, the Output dialog is shown independent of the Output view's visibility
Fixed Bugs:
Git:
- Blame: memory leak
- Edit Last Commit Message: internal error when in bisecting mode
- Journal, Move & Squash: when dragging onto first pushed commit, no "already pushed" warning was displayed memory leak when switching between repositories frequently quotes around filter definitions, e.g. git-crypt, caused errors starting these commands possible error "Raw log messge does not parse as log entry"
- Refresh: internal error when opening repositories with core.worktree set
Hg:
- Refresh: possible hang related to conflicts
- Compare: Ignore Whitespace should not display completely unchanged blocks as changed
SmartGit 18.1.0
Log:
- Possible internal error opening log in merging or rebasing state
- Added system property smartgit.nodecache.maxCachesToKeepInMemory to limit the log caches to keep in memory
Investigate (DeepGit):
- Memory leak
- Wrong colors used for system-independent light theme
- Various commands with dialog-based Log (Checkout, Merge, ...): graph filter options missing in File input field's drop-down menu
SmartGit 17.1.6 Build 11221
New features and improvements:
- Log, Tools menu: allow tools that operate on the repository using ${repositoryRootPath}
Fixed bugs:
Git:
- Git-Flow: when merging, stop processing if merge aborts due to file permission problems
- Refresh: possible internal error for special characters in file name and wrong system charset
- Stash Selection: contained redundant "--" when invoking "git stash push"
SmartGit 17.1.5 Build 11217
New features and improvements:
- built-in SSH client: support for diffie-hellman-group-exchange-sha256
Fixed Bugs:
- Git:
- Log:
- Compare:
- Linux/GTK2: possible internal error painting comments
- too large font was used for comments
- SVN: changing URL did not work reliable - disabled
- Bitbucket: possible 401 authentication failures after redoing OAuth
authentication while SmartGit is running
SmartGit 17.1.4 Build 11213
External Diff tools:
- set system property "smartgit.core.cat.applyFilters" to true to apply
- filter..smudge
- System property "smartgit.executable.home" supports $USERPROFILE on Windows
- support for Git 2.16's SSH client detection ("The SSH server '-G' could not be found")
Fixed Bugs:
- after a fresh setup, "Mark as Favorite" notification comes up again every couple of seconds when dismissing with red x
- Changes view, Index Editor: staging LF-only files converted it to CRLF in Index
- Investigate: Open Log may result in internal error if Blame was not yet initialized
Log:
- Branches: toggling single branch in unselected category may add additional 2nd-level branch to selection
- Changes: Compact Changes option did not work (regression)
- Refresh: internal error related to renamed files
User interface:
- Preferences, Text Editor colors: ruler colors were not applied/stored
- OS X: possible internal error related to connecting/disconnecting monitors update check: did remind user to enable update check while it was disabled by system property
SmartGit 17.1.3 Build 11198
New Features, Improvements:
- Log: the count of the loaded commits is now hidden by default (set smartgit.log.commits.showLoadedCount to true to show it)
- JIRA integration: option smartgit.jira.fixResolutionId to specify the issue resolution ID that should be used to mark issues as resolved
- Set smartgit.updateCheck.checkForLatestBuildVisible to false to hide Help | Check for Latest Build
- Investigate: don't require DeepGit license for licensed SmartGit users
Fixed Bugs:
Git:
- Merge, Abort and others: could not be invoked if .gitmodules was in conflicting state
Refresh:
- Include with relative path like ../.gitconfig did not work in .git/config
- Wrong display after creating orphan branch
- Review comments: not able to add first comment to file
更新時間：2019-08-11
更新細節：
更新時間：2019-08-06
更新細節：
What's new in this version:
- This is a bug fix release that takes care of a number of small issues. It improves refresh performance of remote files as well as adds a native 64 bit binary for Windows
更新時間：2019-08-05
更新細節：
What's new in this version:
- Fixed NVMe Data Units Read/Written
- Improved Crucial MX500 support
Fixed Temperature Color depends on Alert Temperature Settings for Main Dialog:
- Alert Temperature > Current Temperature : Red
- Alert Temperature == Current Temperature : Yellow
- Alert Temperature < Current Temperature : Blue or Green
更新時間：2019-08-05
更新細節：
更新時間：2019-07-28
更新細節：
What's new in this version:
- Added language code to filename of extracted tracks - The three letter language code will now be inserted in the filename of extracted subtitle, audio and video tracks to make it easier to identify the track. If the language has not been specified UND will be inserted for undefined. This feature is enabled by default, but can be disabled in the Preferences.
- Added option to insert track name in filename of extracted tracks - The track name is entered by the encoder of the file and can contain literally anything. In some cases the encoder will enter the language of the track, in some cases they will enter other details about the track, and in some cases they will enter nothing at all. Due to the unpredictable nature of this feature it is disabled by default and must be enabled in the Preferences if you want to use it. Characters that aren't valid for use in filenames will be stripped out of the track name.
- Added shortcut to check all items of type - A shortcut key has been added to check all boxes of a particular type in the Batch Extract list. Ctrl+Shift+S will check all subtitle boxes, Ctrl+Shift+Z will check all audio boxes and Ctrl+Shift+V will check all video boxes. On Mac the shortcut is Cmd+Shift rather than Ctrl+Shift.
- State of Add Files and Add Directory dialogs now saved - The last open directory and other settings will now be restored.
- Updated Portuguese Brazilian translation - There were a few strings I hadn't marked for translation, but these have now been translated. Additional strings associated with new features have also been translated. Translations by Wagg13.
- Reworked translation strings - Some of the strings contained a lot of HTML, which made them hard for translators to read. These strings have been split up into smaller strings with most of the HTML removed, so are much easier to read and translate.
更新時間：2019-07-27
更新細節：