Skip to content

fix: resolve configuration mismatch and implement loud migration warnings#1

Merged
buko merged 1 commit into
mainfrom
fix/config-mismatch-bug
May 30, 2026
Merged

fix: resolve configuration mismatch and implement loud migration warnings#1
buko merged 1 commit into
mainfrom
fix/config-mismatch-bug

Conversation

@buko
Copy link
Copy Markdown
Owner

@buko buko commented May 30, 2026

This commit addresses several critical configuration path issues:

  1. Environment Variable Fallback: codewhale_home() and legacy_deepseek_home() now explicitly check the $HOME environment variable before falling back to dirs::home_dir(). This fixes a bug on Windows where dirs::home_dir() could resolve to a different path than $HOME, causing split configuration states.
  2. Robust Settings Migration: Added migrate_settings_if_needed() to safely migrate settings.toml from legacy DeepSeek folders (and Windows AppData) to the new CodeWhale configuration directory.
  3. Loud Migration Exit: If any configuration or settings files are migrated on startup, the application now loudly notifies the user with colorful terminal output, displaying the exact paths to the new and legacy files, and safely exits to ensure the user verifies the new configuration before continuing.

…ings

This commit addresses several critical configuration path issues:
1. Environment Variable Fallback: codewhale_home() and legacy_deepseek_home() now explicitly check the $HOME environment variable before falling back to dirs::home_dir(). This fixes a bug on Windows where dirs::home_dir() could resolve to a different path than $HOME, causing split configuration states.
2. Robust Settings Migration: Added migrate_settings_if_needed() to safely migrate settings.toml from legacy DeepSeek folders (and Windows AppData) to the new CodeWhale configuration directory.
3. Loud Migration Exit: If any configuration or settings files are migrated on startup, the application now loudly notifies the user with colorful terminal output, displaying the exact paths to the new and legacy files, and safely exits to ensure the user verifies the new configuration before continuing.
@buko buko force-pushed the fix/config-mismatch-bug branch from 28e7765 to 62988d7 Compare May 30, 2026 18:50
@buko buko changed the title Fix config mismatch bug fix: resolve configuration mismatch and implement loud migration warnings May 30, 2026
@buko buko merged commit 1909645 into main May 30, 2026
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.

1 participant