feat: dual-name profile discovery (#161 step 6, stage 1)#183
Merged
Conversation
… step 6, stage 1) Every profile reader now accepts BOTH names, canonical preferred: config/build/profile_smoke.yaml (legacy env_vars.yaml) and profile_release.yaml (legacy env_vars_release.yaml). PROFILE_NAMES + find_profile() live in env_config.py; run_python.py/run.py discovery, validate_env_profiles (both-names = ambiguity ERROR; missing named by canonical), and repro_command all resolve through them. Legacy names are a migration-window fallback only — a stage-3 cleanup removes them once every workspace has renamed. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This was referenced Jul 23, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Stage 1 of the step-6 profile rename (PyAutoHands#181): every reader accepts both
profile_smoke.yaml/profile_release.yaml(canonical) and the legacyenv_vars*.yamlnames, so the 11 workspace repos can rename with no CI breakage window. Both-names-present is a validator error (ambiguity); a stage-3 cleanup later removes the legacy fallbacks.API Changes
Internal
autohandstooling surface:env_config.PROFILE_NAMES+env_config.find_profile(build_dir, kind).run_python.py/run.pydiscovery andrepro_commandworkspace-root detection resolve throughfind_profile.validate_env_profiles: per-kind resolution (ambiguity error / canonical-named missing error);PROFILE_FILESremoved.See commit for detail.
Test Plan
python3 -m pytest tests/— 167 passed (new: find_profile matrix, canonical-named workspace clean, ambiguity error, canonical missing error, repro canonical discovery; all legacy-name tests unchanged as fallback coverage)_testrepos (legacy names)Heart gate
Continuation of today's #181 work under the same human-acknowledged pre-existing RED. Merge before the stage-2 workspace rename PRs.
Generated by the PyAutoLabs agent workflow.
🤖 Generated with Claude Code