Skip to content

feat: accept both profile names in workflows (#161 step 6, stage 1)#101

Merged
Jammy2211 merged 1 commit into
mainfrom
feature/env-profile-rename
Jul 23, 2026
Merged

feat: accept both profile names in workflows (#161 step 6, stage 1)#101
Jammy2211 merged 1 commit into
mainfrom
feature/env-profile-rename

Conversation

@Jammy2211

Copy link
Copy Markdown
Contributor

Summary

Heart half of step-6 stage 1 (PyAutoHands#181): workspace-validation.yml prefers profile_release.yaml with legacy env_vars_release.yaml fallback (same ::error if neither); the reusable smoke workflow's strict validate step fires on either release name (the validator resolves both itself). Docs + smoke_test skill updated to canonical names with one legacy note each. tests/test_test_run.py untouched (opaque fixture data).

Test Plan

  • Both workflow YAMLs yaml.safe_load clean
  • python3 -m pytest tests/ — 289 passed (unaffected, proven)
  • First stage-2 rename PR's smoke gate green confirms the either-name guard live

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

workspace-validation.yml release step prefers profile_release.yaml and
falls back to legacy env_vars_release.yaml; the reusable smoke
workflow's strict validate step fires on either name. Docs/skills text
updated to the canonical names with a single legacy note each. Merge
before the stage-2 workspace rename PRs.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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