[release/v7.6] Separate Store Automation Service Endpoints, Resolve AppID#26599
Conversation
adityapatwardhan
added
the
CL-BuildPackaging
There was a problem hiding this comment.
Pull request overview
This PR backports store automation improvements from the main branch to the v7.6 release branch. It separates Microsoft Store publishing into channel-specific service endpoints and adds dynamic AppID resolution to streamline MSIX package publishing workflows.
Key Changes:
- Separates Store publishing tasks by channel with dedicated service endpoints (
StoreAppPublish-Stablefor LTS/Stable,StoreAppPublish-Previewfor Preview) - Implements dynamic AppID resolution that sets the appropriate AppID based on the detected channel
- Consolidates redundant publishing tasks from three separate tasks into two (one for Stable/LTS, one for Preview)
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
.pipelines/templates/release-MSIX-Publish.yml |
Adds AppID resolution logic, consolidates three publishing tasks into two with channel-specific service endpoints, refactors regex pattern for URL generation |
.pipelines/templates/package-create-msix.yml |
Simplifies variable assignment, splits StoreBroker package creation into two tasks with channel-specific service endpoints |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| outSBName: 'PowerShellStorePackage' | ||
| pdpPath: '$(System.DefaultWorkingDirectory)/PowerShell/.pipelines/store/PDP/PDP' | ||
| pdpMediaPath: '$(System.DefaultWorkingDirectory)/PowerShell/.pipelines/store/PDP/PDP-Media' | ||
| condition: failed() |
There was a problem hiding this comment.
The task has a duplicate condition attribute. Line 255 sets the condition to execute when STABLE or LTS is true, but line 264 overrides it with a failed() condition. This means the Stable/LTS StoreBroker package creation will only run when a previous task fails, which is incorrect. The duplicate condition on line 264 should be removed.
| condition: failed() |
Backport of #26210 to release/v7.6
Triggered by @adityapatwardhan on behalf of @jshigetomi
Original CL Label: CL-BuildPackaging
/cc @PowerShell/powershell-maintainers
Impact
REQUIRED: Choose either Tooling Impact or Customer Impact (or both). At least one checkbox must be selected.
Tooling Impact
Updates MSIX packaging and publishing pipelines to improve channel selection logic and streamline package publishing to different channels (LTS, Stable, Preview). Essential for proper store automation workflow.
Customer Impact
Regression
REQUIRED: Check exactly one box.
This is not a regression.
Testing
Original PR was tested with CI/CD pipeline validation. Backport verified by: 1. Successful cherry-pick with conflict resolution 2. Syntax validation of modified YAML files 3. Verification that separate service endpoints are properly configured for each channel
Risk
REQUIRED: Check exactly one box.
Changes CI/CD pipeline configuration for store publishing, but isolates changes to specific channel handling. Risk is medium because it affects build infrastructure, but the changes are well-scoped and follow established patterns. The separation of service endpoints actually reduces risk by making channel-specific configurations more explicit.
Merge Conflicts
Resolved conflicts in
.pipelines/templates/package-create-msix.ymldue to differences in variable assignment approach and task structure between v7.6 branch and main branch. Applied the PR's intended changes to separate store publishing into distinct tasks with dedicated service endpoints.