Skip to content

fix: add legacy claude-workspace/claude-agent remote aliases for update checker#359

Merged
outsourc-e merged 1 commit intooutsourc-e:mainfrom
kadeross:fix/update-legacy-remote-aliases
May 7, 2026
Merged

fix: add legacy claude-workspace/claude-agent remote aliases for update checker#359
outsourc-e merged 1 commit intooutsourc-e:mainfrom
kadeross:fix/update-legacy-remote-aliases

Conversation

@kadeross
Copy link
Copy Markdown
Contributor

@kadeross kadeross commented May 6, 2026

Users who set up their workspace before the rename from claude-workspace to hermes-workspace (and claude-agent to hermes-agent) have remotes with the old names. The update checker fails to recognize their repos as valid remotes, showing spurious "unrecognized remote" warnings or silently skipping update detection.

Add claude-workspace and claude-agent as legacy aliases alongside the existing hermes-workspace and hermes-agent aliases so the update checker works for both old and new remote naming conventions.

…te checker

Installs that were set up before the claude→hermes rename may have their
git remotes named claude-workspace and claude-agent rather than the new
hermes-workspace / hermes-agent names. Without these aliases the update
checker misidentifies the remote, reports no update URL match, and the
Update Center shows a misleading error.

Adds backward-compatible aliases so both old and new remote naming
conventions are recognised.
@outsourc-e outsourc-e merged commit 6aee17e into outsourc-e:main May 7, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants