Skip to content

smoke profile: own PYAUTO_SKIP_WORKSPACE_VERSION_CHECK (step 3)#54

Merged
Jammy2211 merged 1 commit into
mainfrom
feature/env-scrubbed-baseline
Jul 17, 2026
Merged

smoke profile: own PYAUTO_SKIP_WORKSPACE_VERSION_CHECK (step 3)#54
Jammy2211 merged 1 commit into
mainfrom
feature/env-scrubbed-baseline

Conversation

@Jammy2211

Copy link
Copy Markdown
Collaborator

Summary

Paired with PyAutoBuild#161 step 3 (base-env scrub). Adds PYAUTO_SKIP_WORKSPACE_VERSION_CHECK: "1" to this workspace's smoke profile (config/build/env_vars.yaml).

Why: the mega-run (PyAutoHeart workspace-validation.yml) injects that var at the job env: level, and the smoke profile was silent on it. Once PyAutoBuild's resolver scrubs the ambient PYAUTO_* family, an ambient-only injection would be dropped and every mega-run smoke script would fail WorkspaceVersionMismatchError. Making the profile own the var keeps the mega-run byte-identical (proven: 65/65 scripts unchanged) while closing the ambient-leak surface.

The release profile already sets this var; this brings the smoke profile in line.

Test Plan

  • This PR's own smoke gate (clones PyAutoBuild at the matching feature/env-scrubbed-baseline branch, so it runs against the scrub) is the end-to-end check.

Generated by the PyAutoLabs agent workflow.

Paired with PyAutoBuild's base-env PYAUTO_ scrub: the mega-run injects this var
ambiently and the smoke profile was silent on it, so once the scrub strips the
ambient PYAUTO_ family the injection would be lost and every mega-run smoke
script would fail WorkspaceVersionMismatchError. Making the profile own it
keeps the mega-run byte-identical while closing the ambient-leak surface. The
release profile already sets it.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@Jammy2211 Jammy2211 added the pending-release PR queued for the next release build label Jul 17, 2026
@Jammy2211
Jammy2211 merged commit 0290c7b into main Jul 17, 2026
4 checks passed
@Jammy2211
Jammy2211 deleted the feature/env-scrubbed-baseline branch July 17, 2026 18:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pending-release PR queued for the next release build

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant