Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion apps/desktop/CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ The VS Code / Cursor extension has its own changelog at
separately — desktop releases are tagged `app-v*`, extension releases `ext-v*` —
but they share the same engine, so most Git behaviour lands in both at once.

## [Unreleased]
## [2.7.1] - 2026-10-25

### Fixed
- **GitHub sign-in works behind a proxy.** On a network that reaches the
Expand Down
2 changes: 1 addition & 1 deletion apps/desktop/package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "gitstudio-desktop",
"version": "2.7.0",
"version": "2.7.1",
"private": true,
"license": "Apache-2.0",
"description": "GitStudio \u2014 the native cross-platform desktop app (Electron). Reuses @gitstudio/engine, git-service, webview-ui, and host-bridge behind host-agnostic seams.",
Expand Down
13 changes: 13 additions & 0 deletions docs/releases/app-v2.7.1.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
# GitStudio 2.7.1

### Fixed
- **GitHub sign-in works behind a proxy.** On a network that reaches the
internet only through a proxy, Sign in with GitHub failed with "Couldn't
reach GitHub", and so did every other GitHub view, the update check and
cloud AI providers: those requests connected directly and never used the
system proxy. They now go out the same way the rest of the app does,
through the system proxy or PAC script. Local model servers (Ollama, LM
Studio) are still reached directly. When a request does fail, the message
now says why and which address, for example "Couldn't reach GitHub
(ERR_PROXY_CONNECTION_FAILED) — github.com/login/device/code"
(#133).
2 changes: 1 addition & 1 deletion package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Loading