🔥 Remove production smoke harness#313
Merged
Merged
Conversation
Delete the release script that copied real user authentication, created a production project token, and queried live builds. Release verification should remain local and non-mutating.
Robdel12
marked this pull request as ready for review
July 22, 2026 02:27
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
1 participant
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.
Why
The CLI included a release smoke script that copied a real user login, linked a live production project, created a scoped token, and queried production builds. Even with cleanup logic, release verification should not mutate customer-facing infrastructure or depend on personal production credentials.
What changed
Impact
Local builds, tests, type checks, and package verification continue to cover the publishable CLI without contacting production. There is no replacement live-system workflow.
Confidence
The complete CLI test suite and local release checks pass, the package still builds correctly, and no production-smoke references remain in the repository.