ci: add Studio release server deployment workflow#745
Open
evanlowe wants to merge 1 commit into
Open
Conversation
yaozheng-fang
approved these changes
Jul 26, 2026
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
studio-releaseenvironmentWhy
The dependency cache merged in #744 runs inside the Beijing release server, so the server must be redeployed before cache miss/hit timing can be measured. Local credentials are intentionally unavailable; this workflow uses the repository Secrets already configured for production deployment.
Validation
uv run --group dev pytest -q tests/test_studio_release_server.py tests/cli/test_studio_release.py(32 passed)git diff --check