| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| latest.json | 2026-07-23 | 8.5 kB | |
| GitDesktop_0.5.1_x64-setup.exe.sig | 2026-07-23 | 420 Bytes | |
| GitDesktop_0.5.1_x64-setup.exe | 2026-07-23 | 12.6 MB | |
| GitDesktop_0.5.1_x64_en-US.msi.sig | 2026-07-23 | 420 Bytes | |
| GitDesktop_0.5.1_x64_en-US.msi | 2026-07-23 | 18.1 MB | |
| GitDesktop_0.5.1_universal.app.tar.gz.sig | 2026-07-23 | 408 Bytes | |
| GitDesktop_0.5.1_universal.app.tar.gz | 2026-07-23 | 34.9 MB | |
| GitDesktop_0.5.1_universal.dmg | 2026-07-23 | 34.1 MB | |
| GitDesktop_0.5.1_amd64.AppImage.sig | 2026-07-23 | 424 Bytes | |
| GitDesktop_0.5.1_amd64.AppImage | 2026-07-23 | 95.3 MB | |
| GitDesktop-0.5.1-1.x86_64.rpm.sig | 2026-07-23 | 420 Bytes | |
| GitDesktop-0.5.1-1.x86_64.rpm | 2026-07-23 | 19.6 MB | |
| GitDesktop_0.5.1_amd64.deb.sig | 2026-07-23 | 416 Bytes | |
| GitDesktop_0.5.1_amd64.deb | 2026-07-23 | 19.6 MB | |
| GitDesktop v0.5.1 source code.tar.gz | 2026-07-23 | 5.7 MB | |
| GitDesktop v0.5.1 source code.zip | 2026-07-23 | 6.4 MB | |
| README.md | 2026-07-23 | 1.1 kB | |
| Totals: 17 Items | 246.3 MB | 0 | |
Fixed
- Fixed cloning, fetching, pulling, and pushing private Bitbucket repositories
over HTTPS failing with
could not read Password for '…@bitbucket.org': terminal prompts disabledon macOS and Linux. GitDesktop now hands your stored Bitbucket API token to git's credential store over STDIN (never placed on the command line), so operations authenticate without a prompt wherever git has a credential helper — the system keychain on macOS, Git Credential Manager on Windows, or a configured helper on Linux. Cloning over SSH was unaffected. - The task editor no longer warns that an interpreter "wasn't detected" when it's actually installed. Interpreters installed through a version manager (nvm/fnm for Node, and anything else that lives only on your shell's PATH) weren't found by the editor's quick check when GitDesktop was launched from the Dock or Finder on macOS — even though the task ran fine. The editor now confirms the selected interpreter the same way a run resolves it (via your login shell), so it shows the real path instead of a false "not detected" warning.
