Skip to content

v0.63.0

Choose a tag to compare

@inkeep-internal-ci inkeep-internal-ci released this 25 Aug 16:30

Minor Changes

  • Git operations now honor the GitHub account you've already declared for a repo, instead of always using whichever GitHub CLI account happens to be active. If the remote URL carries a username (https://alice@github.com/owner/repo) or your git config has a credential.<url>.username entry (HTTPS remotes only), sync pushes, push-permission checks, and ok clone all authenticate as that account — read from standard git mechanisms, in the same order git itself resolves them, with no new OpenKnowledge configuration. Multiple accounts on one machine are a GitHub CLI feature, so this needs each account signed in with gh auth login (GitHub CLI 2.40 or newer); OpenKnowledge's own GitHub connection stores one account per host, so a declaration changes the error messages you see but not which credentials get used unless the account is also signed in to the GitHub CLI. If the declared account isn't signed in there, OpenKnowledge falls back to the credentials it does have rather than losing them, and picks up a later gh auth login fix within a sync cycle or two.

    Error messages now tell the truth about identity: access-denied messages end with the account that was actually used ("Authenticated as bob."), a missed declaration is named ("Your remote URL names alice, but that account's credentials couldn't be used."), and "repository not found" failures no longer offer sign-in as the fix — the repo may not exist, or the account used may not be able to see it, and neither git nor GitHub reveals which.

    Behavior change for remotes that embed a username. A remote like https://alice@github.com/owner/repo is now recognized as a GitHub origin, so OpenKnowledge's own credential flow takes precedence over ambient system credential helpers for it — as it always has for other GitHub remotes. If such a remote's only working credential lived in Git Credential Manager or your OS keychain, sync will report you as signed out after upgrading: connect GitHub in OpenKnowledge once (or sign in to the GitHub CLI) and it resumes. Two smaller effects of the same recognition: public repos with these URLs clone anonymously without requiring sign-in, and receiving a shared folder accepts them instead of asking you to switch the remote.

Downloads

Platform Architecture Download
macOS Apple Silicon OpenKnowledge-arm64.dmg
Windows x64 OpenKnowledge-Setup-x64.exe
Windows arm64 OpenKnowledge-Setup-arm64.exe
Debian / Ubuntu x64 OpenKnowledge-amd64.deb
Debian / Ubuntu arm64 OpenKnowledge-arm64.deb
Fedora / RHEL x64 OpenKnowledge-x86_64.rpm
Fedora / RHEL arm64 OpenKnowledge-aarch64.rpm