Skip to content

fix: migrate resolves --env-file and --data paths against the project - #12

Merged
romamo merged 1 commit into
mainfrom
fix/migrate-paths-in-project
Oct 2, 2026
Merged

romamo merged 1 commit into
mainfrom
fix/migrate-paths-in-project

Conversation

@romamo

@romamo romamo commented Oct 2, 2026

Copy link
Copy Markdown
Collaborator

migrate --env-file NAME=PATH and --data NAME=PATH resolve a relative path against the project again. The argparse CLI ran migrate inside the project directory, so that is what a relative path meant; the treaty port (#6 to #11) resolved these two against the current directory, unlike every other path flag.

Found rewriting the LedgrAI deployment runbook for the new CLI.

Checks

  • New test test_migrate_resolves_env_and_data_files_against_the_project fails without the fix
  • uv run pytest: 458 passed; ruff, mypy clean

🤖 Generated with Claude Code

https://claude.ai/code/session_015MJdwagp7FxuuxminHgv2V

The argparse CLI ran migrate inside the project directory, so a relative
env file or source URL file meant one there. The treaty port resolved them
against the current directory instead. Found rewriting the LedgrAI
deployment runbook for the new CLI.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015MJdwagp7FxuuxminHgv2V
@romamo
romamo merged commit e80a050 into main Oct 2, 2026
1 check passed
@romamo
romamo deleted the fix/migrate-paths-in-project branch October 2, 2026 08:57
@shipmill-romamo shipmill-romamo Bot added this to the 0.6.0 milestone Oct 8, 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