Google Chrome 歷史版本列表
Google Chrome (32-bit)Google Chrome (64-bit)
更新時間：2019-02-21
更新細節：
更新時間：2019-02-15
更新細節：
更新時間：2019-02-14
更新細節：
What's new in this version:
Google Chrome 72.0.3626.109 (32-bit)
- Publish DEPS for 72.0.3626.109 by chrome-release-bot
- Incrementing VERSION to 72.0.3626.109 by chrome-release-bot
- Add a ForceNetworkInProcess policy to force networking to run in the browser process
- Incrementing VERSION to 72.0.3626.108 by chrome-release-bot
- Incrementing VERSION to 72.0.3626.107 by chrome-release-bot
- Incrementing VERSION to 72.0.3626.106 by chrome-release-bot
- Incrementing VERSION to 72.0.3626.105 by chrome-release-bot
- Incrementing VERSION to 72.0.3626.104 by chrome-release-bot
- Add target-sdk quirk for encoding '#'s in loadData
- Do not post task to IO when updating WebViewRendererState
- Incrementing VERSION to 72.0.3626.103 by chrome-release-bot
- Incrementing VERSION to 72.0.3626.102 by chrome-release-bot
- cros: Fix mismatched enum values in mojo/js by Jacob Dufault
- Incrementing VERSION to 72.0.3626.101 by chrome-release-bot
- Incrementing VERSION to 72.0.3626.100 by chrome-release-bot
- [ios] Correct cherry pick for crrev.com/c/1457473
- [ios] Don't load external URLs on the NTP if the NTP hasn't committed
- [ios] Prevent taps in the NTP if the underlying NTP hasn't committed
- Incrementing VERSION to 72.0.3626.99 by chrome-release-bot
- Incrementing VERSION to 72.0.3626.98 by chrome-release-bot
- Incrementing VERSION to 72.0.3626.97 by chrome-release-bot
- [Merge to M-72] Fix external displays switching to mirror mode unexpectedly
Google Chrome 72.0.3626.96 (32-bit)
- Change log not available for this version
Google Chrome 72.0.3626.81 (32-bit)
Security fixes:
- Critical CVE-2019-5754: Inappropriate implementation in QUIC Networking
- High CVE-2019-5782: Inappropriate implementation in V8
- High CVE-2019-5755: Inappropriate implementation in V8
- High CVE-2019-5756: Use after free in PDFium
- High CVE-2019-5757: Type Confusion in SVG
- High CVE-2019-5758: Use after free in Blink
- High CVE-2019-5759: Use after free in HTML select elements
- High CVE-2019-5760: Use after free in WebRTC
- High CVE-2019-5761: Use after free in SwiftShader
- High CVE-2019-5762: Use after free in PDFium
- High CVE-2019-5763: Insufficient validation of untrusted input in V8
- High CVE-2019-5764: Use after free in WebRTC
- High: Use after free in FileAPI
- High CVE-2019-5765: Insufficient policy enforcement in the browser
- High: Use after free in Mojo interface
- High: Use after free in Payments
- High: Use after free in Mojo interface
- High: Stack buffer overflow in Skia
- Medium CVE-2019-5766: Insufficient policy enforcement in Canvas
- Medium CVE-2019-5767: Incorrect security UI in WebAPKs
- Medium CVE-2019-5768: Insufficient policy enforcement in DevTools
- Medium CVE-2019-5769: Insufficient validation of untrusted input in Blink
- Medium CVE-2019-5770: Heap buffer overflow in WebGL
- Medium CVE-2019-5771: Heap buffer overflow in SwiftShader
- Medium CVE-2019-5772: Use after free in PDFium
- Medium CVE-2019-5773: Insufficient data validation in IndexedDB
- Medium CVE-2019-5775: Insufficient policy enforcement in Omnibox
- Medium CVE-2019-5776: Insufficient policy enforcement in Omnibox
- Medium CVE-2019-5777: Insufficient policy enforcement in Omnibox
- Low CVE-2019-5778: Insufficient policy enforcement in Extensions
- Low CVE-2019-5779: Insufficient policy enforcement in ServiceWorker
- Low CVE-2019-5780: Insufficient policy enforcement
- Low CVE-2019-5781: Insufficient policy enforcement in Omnibox
- We would also like to thank all security researchers that worked with us during the development cycle to prevent security bugs from ever reaching the stable channel
Google Chrome 71.0.3578.98 (32-bit)
- Change log not available for this version
Google Chrome 71.0.3578.80 (32-bit)
Security Fixes and Rewards:
- Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed
- Out of bounds write in V8
- Use after frees in PDFium
- Heap buffer overflow in Skia
- Use after free in PDFium
- Use after free in Blink
- Heap buffer overflow in Canvas
- Use after free in WebAudio
- Use after free in MediaRecorder
- Heap buffer overflow in Blink
- Out of bounds write in V8
- Use after free in Skia
- Inappropriate implementation in Extensions
- Multiple issues in SQLite via WebSQL
- Inappropriate implementation in Site Isolation
- Incorrect security UI in Blink
- Inappropriate implementation in Navigation
- Inappropriate implementation in Omnibox
- Insufficient policy enforcement in Blink
- Insufficient policy enforcement in Blink
- Insufficient policy enforcement in Navigation
- Inappropriate implementation in Media
- Inappropriate implementation in Network Authentication
- Insufficient data validation in Shell Integration
- Insufficient policy enforcement in URL Formatter
- Use after free in Skia
- Insufficient policy enforcement in URL Formatter
- Insufficient policy enforcement in Proxy
- Out of bounds read in V8
- Inappropriate implementation in PDFium
- Use after free in Extensions
- Inappropriate implementation in Navigation
- Inappropriate implementation in Navigation
- Insufficient policy enforcement in Navigation
- Insufficient policy enforcement in URL Formatter
This bug was fixed in Chrome 69, but was incorrectly omitted from the release notes at the time:
- Medium To be allocated: Insufficient policy enforcement in Payments
Google Chrome 70.0.3538.110 (32-bit)
- Change log not available for this version
Google Chrome 70.0.3538.102 (32-bit)
- Change log not available for this version
Google Chrome 70.0.3538.77 (32-bit)
- Publish DEPS for 70.0.3538.77 by chrome-release-bot
- Incrementing VERSION to 70.0.3538.77 by chrome-release-bot
- Web Audio: fix two bugs in audibility detection in BaseAudioContext. by Becca Hughes
- cherry pick r601765 to M70 by Sahel Sharify
- [Picture in Picture] Show controls on mouseover on the window. by Jennifer Apacible
- [Picture in Picture] Fix controls timer issue by Becca Hughes
- Reland "Fling bubbles from OOPIF properly" without the tests. by Sahel Sharify
- [Merge M70][AF] Use 'Manage...' as footer string when popup type is unspecified by Fabio Tirelo
- Revert "Strengthen MITIGATION_DLL_SEARCH_ORDER on non-component builds." by Will Harris
- Incrementing VERSION to 70.0.3538.76 by chrome-release-bot
- [M70 branch] Roll ICU to 0b97836 by Jungshik Shin
- Fix text input on ARC++ Kiosk apps. by Yuichiro Hanada
- Revert "Network Service: Convert port_forwarding_controller.cc to mojo host resolver" by Jun Cai
- Turn off signin-allowed toggle after sign-out from dialog by Thomas Tangl
- Show sign-out dialog when signin-allowed is toggled off by Thomas Tangl
- ozone: Ensure we don't return invalid GbmBuffer objects by Alexandros Frantzis
- Revert "[M70 Merge][TPM Reporting] Add TPM status information to DeviceStatusCollector" by Ivan Sandrk
- Merge to 70: Fixes potential crash when toggling accessibility services by David Tseng
- Incrementing VERSION to 70.0.3538.75 by chrome-release-bot
- [ios] Check for nullptr NavigationItem before updating URL. by Danyao Wang
- Incrementing VERSION to 70.0.3538.74 by chrome-release-bot
- Incrementing VERSION to 70.0.3538.73 by chrome-release-bot
- [M70 merge] viz: Optimize pixel-moving renderpasses damage by wutao
- Incrementing VERSION to 70.0.3538.72 by chrome-release-bot
- Revert "Add a CHECK to non-DICE signin that it's only used for force-signin" by Jochen Eisinger
- Incrementing VERSION to 70.0.3538.71 by chrome-release-bot
- chrome_features: Set Usbguard feature flag to disabled by default. by Allen Webb
- Incrementing VERSION to 70.0.3538.70 by chrome-release-bot
- cros: Fix menus getting squished by Alex Newcomer
- Fix merge time window limit method by Henrique Grandinetti
- Make old time limit locks not be applied to the Chromebook by Henrique Grandinetti
- Fix a crash in TtsControllerImpl::VoicesChanged due to a use after free. by Sam McNally
- Incrementing VERSION to 70.0.3538.69 by chrome-release-bot
- Reland "Fix MessageListView crash on update during close." by Tetsui Ohkubo
- Revert "Fix MessageListView crash on update during close." by Tetsui Ohkubo
- Incrementing VERSION to 70.0.3538.68 by chrome-release-bot
- Fix naming issue when renaming files inside My files by Luciano Pacheco
- Store remaining usage time in milliseconds by Henrique Grandinetti
Google Chrome 70.0.3538.67 (32-bit)
Security Fixes and Rewards:
- Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed
- High CVE-2018-17462: Sandbox escape in AppCache
- High CVE-2018-17463: Remote code execution in V8
- High CVE to be assigned: Heap buffer overflow in Little CMS in PDFium
- High CVE-2018-17464: URL spoof in Omnibox
- High CVE-2018-17465: Use after free in V8
- High CVE-2018-17466: Memory corruption in Angle
- Medium CVE-2018-17467: URL spoof in Omnibox
- Medium CVE-2018-17468: Cross-origin URL disclosure in Blink
- Medium CVE-2018-17469: Heap buffer overflow in PDFium
- Medium CVE-2018-17470: Memory corruption in GPU Internals
- Medium CVE-2018-17471: Security UI occlusion in full screen mode
- Medium CVE-2018-17472: iframe sandbox escape on iOS
- Medium CVE-2018-17473: URL spoof in Omnibox
- Medium CVE-2018-17474: Use after free in Blink
- Low CVE-2018-17475: URL spoof in Omnibox
- Low CVE-2018-17476: Security UI occlusion in full screen mode
- Low CVE-2018-5179: Lack of limits on update() in ServiceWorker
- Low CVE-2018-17477: UI spoof in Extensions
We would also like to thank all security researchers that worked with us during the development cycle to prevent security bugs from ever reaching the stable channel.As usual, our ongoing internal security work was responsible for a wide range of fixes:
- Various fixes from internal audits, fuzzing and other initiatives
Google Chrome 69.0.3497.100 (32-bit)
- Security Fixes and Rewards
- Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed
This update includes 1 security fix from our ongoing internal security work:
- Fixes from internal audits, fuzzing and other initiatives
- Many of our security bugs are detected using AddressSanitizer, MemorySanitizer, UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer, or AFL
Google Chrome 69.0.3497.92 (32-bit)
Security Fixes and Rewards:
- Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed
- This update includes 2 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information
- [$3000][875322] High (CVE to be assigned): Function signature mismatch in WebAssembly. Reported by Kevin Cheung from Autodesk on 2018-08-17
- [$TBD][880759] Medium (CVE to be assigned): URL Spoofing in Omnibox. Reported by evi1m0 of Bilibili Security Team on 2018-09-05
- We would also like to thank all security researchers that worked with us during the development cycle to prevent security bugs from ever reaching the stable channel
- Many of our security bugs are detected using AddressSanitizer, MemorySanitizer, UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer, or AFL
Google Chrome 69.0.3497.81 (32-bit)
- Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed
- This update includes 40 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information
- High CVE-2018-16065: Out of bounds write in V8
- High CVE-2018-16066:Out of bounds read in Blink
- High CVE-2018-16067: Out of bounds read in WebAudio
- High CVE-2018-16068: Out of bounds write in Mojo
- High CVE-2018-16069:Out of bounds read in SwiftShader
- High CVE-2018-16070: Integer overflow in Skia
- High CVE-2018-16071: Use after free in WebRTC
- Medium CVE-2018-16072: Cross origin pixel leak in Chrome's interaction with Android's MediaPlayer
- Medium CVE-2018-16073: Site Isolation bypass after tab restore
- Medium CVE-2018-16074: Site Isolation bypass using Blob URLS
- Medium: Out of bounds read in Little-CMS
- Medium CVE-2018-16075: Local file access in Blink
- Medium CVE-2018-16076: Out of bounds read in PDFium
- Medium CVE-2018-16077: Content security policy bypass in Blink
- Medium CVE-2018-16078: Credit card information leak in Autofill
- Medium CVE-2018-16079: URL spoof in permission dialogs
- Medium CVE-2018-16080: URL spoof in full screen mode
- Medium CVE-2018-16081: Local file access in DevTools
- Medium CVE-2018-16082: Stack buffer overflow in SwiftShader
- Medium CVE-2018-16083: Out of bounds read in WebRTC
- Low CVE-2018-16084: User confirmation bypass in external protocol handling
- Low CVE-2018-16085: Use after free in Memory Instrumentation
- Various fixes from internal audits, fuzzing and other initiatives
Google Chrome 68.0.3440.106 (32-bit)
- Change log not available for this version
Google Chrome 68.0.3440.84 (32-bit)
- Change log not available for this version
更新時間：2019-02-14
更新細節：
更新時間：2019-02-14
更新細節：
更新時間：2019-02-14
更新細節：
更新時間：2019-02-09
更新細節：
更新時間：2019-02-07
更新細節：
更新時間：2019-02-07
更新細節：
What's new in this version:
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-02-07
更新細節：
What's new in this version:
Google Chrome 72.0.3626.96 (32-bit)
- Change log not available for this version
Google Chrome 72.0.3626.81 (32-bit)
Security fixes:
- Critical CVE-2019-5754: Inappropriate implementation in QUIC Networking
- High CVE-2019-5782: Inappropriate implementation in V8
- High CVE-2019-5755: Inappropriate implementation in V8
- High CVE-2019-5756: Use after free in PDFium
- High CVE-2019-5757: Type Confusion in SVG
- High CVE-2019-5758: Use after free in Blink
- High CVE-2019-5759: Use after free in HTML select elements
- High CVE-2019-5760: Use after free in WebRTC
- High CVE-2019-5761: Use after free in SwiftShader
- High CVE-2019-5762: Use after free in PDFium
- High CVE-2019-5763: Insufficient validation of untrusted input in V8
- High CVE-2019-5764: Use after free in WebRTC
- High: Use after free in FileAPI
- High CVE-2019-5765: Insufficient policy enforcement in the browser
- High: Use after free in Mojo interface
- High: Use after free in Payments
- High: Use after free in Mojo interface
- High: Stack buffer overflow in Skia
- Medium CVE-2019-5766: Insufficient policy enforcement in Canvas
- Medium CVE-2019-5767: Incorrect security UI in WebAPKs
- Medium CVE-2019-5768: Insufficient policy enforcement in DevTools
- Medium CVE-2019-5769: Insufficient validation of untrusted input in Blink
- Medium CVE-2019-5770: Heap buffer overflow in WebGL
- Medium CVE-2019-5771: Heap buffer overflow in SwiftShader
- Medium CVE-2019-5772: Use after free in PDFium
- Medium CVE-2019-5773: Insufficient data validation in IndexedDB
- Medium CVE-2019-5775: Insufficient policy enforcement in Omnibox
- Medium CVE-2019-5776: Insufficient policy enforcement in Omnibox
- Medium CVE-2019-5777: Insufficient policy enforcement in Omnibox
- Low CVE-2019-5778: Insufficient policy enforcement in Extensions
- Low CVE-2019-5779: Insufficient policy enforcement in ServiceWorker
- Low CVE-2019-5780: Insufficient policy enforcement
- Low CVE-2019-5781: Insufficient policy enforcement in Omnibox
- We would also like to thank all security researchers that worked with us during the development cycle to prevent security bugs from ever reaching the stable channel
Google Chrome 71.0.3578.98 (32-bit)
- Change log not available for this version
Google Chrome 71.0.3578.80 (32-bit)
Security Fixes and Rewards:
- Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed
- Out of bounds write in V8
- Use after frees in PDFium
- Heap buffer overflow in Skia
- Use after free in PDFium
- Use after free in Blink
- Heap buffer overflow in Canvas
- Use after free in WebAudio
- Use after free in MediaRecorder
- Heap buffer overflow in Blink
- Out of bounds write in V8
- Use after free in Skia
- Inappropriate implementation in Extensions
- Multiple issues in SQLite via WebSQL
- Inappropriate implementation in Site Isolation
- Incorrect security UI in Blink
- Inappropriate implementation in Navigation
- Inappropriate implementation in Omnibox
- Insufficient policy enforcement in Blink
- Insufficient policy enforcement in Blink
- Insufficient policy enforcement in Navigation
- Inappropriate implementation in Media
- Inappropriate implementation in Network Authentication
- Insufficient data validation in Shell Integration
- Insufficient policy enforcement in URL Formatter
- Use after free in Skia
- Insufficient policy enforcement in URL Formatter
- Insufficient policy enforcement in Proxy
- Out of bounds read in V8
- Inappropriate implementation in PDFium
- Use after free in Extensions
- Inappropriate implementation in Navigation
- Inappropriate implementation in Navigation
- Insufficient policy enforcement in Navigation
- Insufficient policy enforcement in URL Formatter
This bug was fixed in Chrome 69, but was incorrectly omitted from the release notes at the time:
- Medium To be allocated: Insufficient policy enforcement in Payments
Google Chrome 70.0.3538.110 (32-bit)
- Change log not available for this version
Google Chrome 70.0.3538.102 (32-bit)
- Change log not available for this version
Google Chrome 70.0.3538.77 (32-bit)
- Publish DEPS for 70.0.3538.77 by chrome-release-bot
- Incrementing VERSION to 70.0.3538.77 by chrome-release-bot
- Web Audio: fix two bugs in audibility detection in BaseAudioContext. by Becca Hughes
- cherry pick r601765 to M70 by Sahel Sharify
- [Picture in Picture] Show controls on mouseover on the window. by Jennifer Apacible
- [Picture in Picture] Fix controls timer issue by Becca Hughes
- Reland "Fling bubbles from OOPIF properly" without the tests. by Sahel Sharify
- [Merge M70][AF] Use 'Manage...' as footer string when popup type is unspecified by Fabio Tirelo
- Revert "Strengthen MITIGATION_DLL_SEARCH_ORDER on non-component builds." by Will Harris
- Incrementing VERSION to 70.0.3538.76 by chrome-release-bot
- [M70 branch] Roll ICU to 0b97836 by Jungshik Shin
- Fix text input on ARC++ Kiosk apps. by Yuichiro Hanada
- Revert "Network Service: Convert port_forwarding_controller.cc to mojo host resolver" by Jun Cai
- Turn off signin-allowed toggle after sign-out from dialog by Thomas Tangl
- Show sign-out dialog when signin-allowed is toggled off by Thomas Tangl
- ozone: Ensure we don't return invalid GbmBuffer objects by Alexandros Frantzis
- Revert "[M70 Merge][TPM Reporting] Add TPM status information to DeviceStatusCollector" by Ivan Sandrk
- Merge to 70: Fixes potential crash when toggling accessibility services by David Tseng
- Incrementing VERSION to 70.0.3538.75 by chrome-release-bot
- [ios] Check for nullptr NavigationItem before updating URL. by Danyao Wang
- Incrementing VERSION to 70.0.3538.74 by chrome-release-bot
- Incrementing VERSION to 70.0.3538.73 by chrome-release-bot
- [M70 merge] viz: Optimize pixel-moving renderpasses damage by wutao
- Incrementing VERSION to 70.0.3538.72 by chrome-release-bot
- Revert "Add a CHECK to non-DICE signin that it's only used for force-signin" by Jochen Eisinger
- Incrementing VERSION to 70.0.3538.71 by chrome-release-bot
- chrome_features: Set Usbguard feature flag to disabled by default. by Allen Webb
- Incrementing VERSION to 70.0.3538.70 by chrome-release-bot
- cros: Fix menus getting squished by Alex Newcomer
- Fix merge time window limit method by Henrique Grandinetti
- Make old time limit locks not be applied to the Chromebook by Henrique Grandinetti
- Fix a crash in TtsControllerImpl::VoicesChanged due to a use after free. by Sam McNally
- Incrementing VERSION to 70.0.3538.69 by chrome-release-bot
- Reland "Fix MessageListView crash on update during close." by Tetsui Ohkubo
- Revert "Fix MessageListView crash on update during close." by Tetsui Ohkubo
- Incrementing VERSION to 70.0.3538.68 by chrome-release-bot
- Fix naming issue when renaming files inside My files by Luciano Pacheco
- Store remaining usage time in milliseconds by Henrique Grandinetti
Google Chrome 70.0.3538.67 (32-bit)
Security Fixes and Rewards:
- Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed
- High CVE-2018-17462: Sandbox escape in AppCache
- High CVE-2018-17463: Remote code execution in V8
- High CVE to be assigned: Heap buffer overflow in Little CMS in PDFium
- High CVE-2018-17464: URL spoof in Omnibox
- High CVE-2018-17465: Use after free in V8
- High CVE-2018-17466: Memory corruption in Angle
- Medium CVE-2018-17467: URL spoof in Omnibox
- Medium CVE-2018-17468: Cross-origin URL disclosure in Blink
- Medium CVE-2018-17469: Heap buffer overflow in PDFium
- Medium CVE-2018-17470: Memory corruption in GPU Internals
- Medium CVE-2018-17471: Security UI occlusion in full screen mode
- Medium CVE-2018-17472: iframe sandbox escape on iOS
- Medium CVE-2018-17473: URL spoof in Omnibox
- Medium CVE-2018-17474: Use after free in Blink
- Low CVE-2018-17475: URL spoof in Omnibox
- Low CVE-2018-17476: Security UI occlusion in full screen mode
- Low CVE-2018-5179: Lack of limits on update() in ServiceWorker
- Low CVE-2018-17477: UI spoof in Extensions
We would also like to thank all security researchers that worked with us during the development cycle to prevent security bugs from ever reaching the stable channel.As usual, our ongoing internal security work was responsible for a wide range of fixes:
- Various fixes from internal audits, fuzzing and other initiatives
Google Chrome 69.0.3497.100 (32-bit)
- Security Fixes and Rewards
- Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed
This update includes 1 security fix from our ongoing internal security work:
- Fixes from internal audits, fuzzing and other initiatives
- Many of our security bugs are detected using AddressSanitizer, MemorySanitizer, UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer, or AFL
Google Chrome 69.0.3497.92 (32-bit)
Security Fixes and Rewards:
- Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed
- This update includes 2 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information
- [$3000][875322] High (CVE to be assigned): Function signature mismatch in WebAssembly. Reported by Kevin Cheung from Autodesk on 2018-08-17
- [$TBD][880759] Medium (CVE to be assigned): URL Spoofing in Omnibox. Reported by evi1m0 of Bilibili Security Team on 2018-09-05
- We would also like to thank all security researchers that worked with us during the development cycle to prevent security bugs from ever reaching the stable channel
- Many of our security bugs are detected using AddressSanitizer, MemorySanitizer, UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer, or AFL
Google Chrome 69.0.3497.81 (32-bit)
- Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed
- This update includes 40 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information
- High CVE-2018-16065: Out of bounds write in V8
- High CVE-2018-16066:Out of bounds read in Blink
- High CVE-2018-16067: Out of bounds read in WebAudio
- High CVE-2018-16068: Out of bounds write in Mojo
- High CVE-2018-16069:Out of bounds read in SwiftShader
- High CVE-2018-16070: Integer overflow in Skia
- High CVE-2018-16071: Use after free in WebRTC
- Medium CVE-2018-16072: Cross origin pixel leak in Chrome's interaction with Android's MediaPlayer
- Medium CVE-2018-16073: Site Isolation bypass after tab restore
- Medium CVE-2018-16074: Site Isolation bypass using Blob URLS
- Medium: Out of bounds read in Little-CMS
- Medium CVE-2018-16075: Local file access in Blink
- Medium CVE-2018-16076: Out of bounds read in PDFium
- Medium CVE-2018-16077: Content security policy bypass in Blink
- Medium CVE-2018-16078: Credit card information leak in Autofill
- Medium CVE-2018-16079: URL spoof in permission dialogs
- Medium CVE-2018-16080: URL spoof in full screen mode
- Medium CVE-2018-16081: Local file access in DevTools
- Medium CVE-2018-16082: Stack buffer overflow in SwiftShader
- Medium CVE-2018-16083: Out of bounds read in WebRTC
- Low CVE-2018-16084: User confirmation bypass in external protocol handling
- Low CVE-2018-16085: Use after free in Memory Instrumentation
- Various fixes from internal audits, fuzzing and other initiatives
Google Chrome 68.0.3440.106 (32-bit)
- Change log not available for this version
Google Chrome 68.0.3440.84 (32-bit)
- Change log not available for this version