[python] enable typespec-azure integration testing for http-client-python changes#10432
Merged
Merged
Conversation
iscai-msft
requested review from
AlitzelMendez,
bterlson,
chrisradek,
markcowl,
timotheeguerin and
witemple-msft
as code owners
Contributor
|
No changes needing a change description found. |
Collaborator
|
You can try these changes here
|
iscai-msft
force-pushed
the
python/integrationTest
branch
from
ac8812c to
e93a764
Compare
timotheeguerin
approved these changes
Apr 20, 2026
iscai-msft
force-pushed
the
python/integrationTest
branch
5 times, most recently
from
e9298df to
62beffe
Compare
Create python-integration.yml that triggers on http-client-python changes and runs the full typespec-azure branded Python e2e test suite: - Build & Regenerate - Mock API Tests - Type Checking (mypy, pyright) - Lint & Format (pylint, lint:extra, format:extra:check) - Docs Validation (apiview, sphinx) The workflow checks out Azure/typespec-azure, patches the core submodule to the PR commit, builds and packs http-client-python locally, then overrides typespec-python's dependency to use the PR version instead of the published npm version. This ensures tests validate the actual PR changes, not the last release. Reuses typespec-azure's composite actions for environment consistency. external-integration.yml is unchanged — http-client-python stays in paths-ignore since this dedicated workflow provides full Python coverage. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
iscai-msft
force-pushed
the
python/integrationTest
branch
from
62beffe to
0211dd3
Compare
timotheeguerin
approved these changes
Apr 20, 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
3 participants
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
Remove
packages/http-client-python/**frompaths-ignorein the external integration workflow (external-integration.yml).Motivation
@azure-tools/typespec-python(branded emitter) in thetypespec-azurerepo has a direct dependency on@typespec/http-client-python(unbranded emitter). Previously, changes tohttp-client-pythonwere excluded from triggering the typespec-azure integration check, meaning branded emitter breakages could go undetected until after merge.What this does
When a PR touches files in
packages/http-client-python/, the integration workflow will now:Azure/typespec-azurecoresubmodule to the PR committypespec-pythonwhich depends onhttp-client-python)This ensures that unbranded emitter changes don't break the branded emitter build.