[WIP] Fix deploy issues in staging environment #37

2026-01-08T22:14:36Z

Copilot commented

2026-01-08 22:14:36 +00:00

(Migrated from github.com)

Fix Deploy Staging Workflow

Changes:

Analyze the inconsistency between deploy_staging.yml and release_pipeline.yml
Update deploy_staging.yml to use the same build approach as release_pipeline.yml
Ensure the ZIP naming convention is consistent
Test the workflow logic manually
Add clarifying comments for Python setup
Code review completed and addressed

Issue Fixed:

The deploy_staging.yml workflow was using package_extension.py which creates ZIPs with naming pattern {repo}-{version}-{platform}-{ext_type}.zip, while release_pipeline.yml uses direct zip commands with pattern {repo}-{version}-{suffix}.zip. This inconsistency could cause deployment issues.

Solution:

Updated deploy_staging.yml to use the same ZIP creation approach as release_pipeline.yml:

Uses direct zip command instead of Python script for building
Creates ZIP with consistent naming: {repo}-{version}-staging.zip
Excludes the same development artifacts as release pipeline
Maintains the same ZIP structure (extension files at root level)
Python setup is retained for validation scripts

Original prompt

Fix deploy staging

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

## Fix Deploy Staging Workflow ### Changes: - [x] Analyze the inconsistency between deploy_staging.yml and release_pipeline.yml - [x] Update deploy_staging.yml to use the same build approach as release_pipeline.yml - [x] Ensure the ZIP naming convention is consistent - [x] Test the workflow logic manually - [x] Add clarifying comments for Python setup - [x] Code review completed and addressed ### Issue Fixed: The `deploy_staging.yml` workflow was using `package_extension.py` which creates ZIPs with naming pattern `{repo}-{version}-{platform}-{ext_type}.zip`, while `release_pipeline.yml` uses direct `zip` commands with pattern `{repo}-{version}-{suffix}.zip`. This inconsistency could cause deployment issues. ### Solution: Updated `deploy_staging.yml` to use the same ZIP creation approach as `release_pipeline.yml`: - Uses direct `zip` command instead of Python script for building - Creates ZIP with consistent naming: `{repo}-{version}-staging.zip` - Excludes the same development artifacts as release pipeline - Maintains the same ZIP structure (extension files at root level) - Python setup is retained for validation scripts   <details> <summary>Original prompt</summary> > Fix deploy staging </details>  --- 💬 We'd love your input! Share your thoughts on Copilot coding agent in our [2 minute survey](https://gh.io/copilot-coding-agent-survey).

jmiller-moko (Migrated from github.com) reviewed 2026-01-08 22:14:36 +00:00

jmiller-moko commented

2026-01-08 22:43:44 +00:00

(Migrated from github.com)

@copilot try again

jmiller-moko commented

2026-01-09 00:06:39 +00:00

(Migrated from github.com)

@copilot try again

Copilot commented

2026-01-09 00:10:10 +00:00

(Migrated from github.com)

@copilot try again

Could you provide more details about what needs to be fixed? The workflow has been updated to:

Use direct zip commands matching release_pipeline.yml
Create consistent ZIP naming with -staging suffix
Exclude development artifacts

What specific issue are you encountering with the staging deployment?

> @copilot try again Could you provide more details about what needs to be fixed? The workflow has been updated to: - Use direct zip commands matching release_pipeline.yml - Create consistent ZIP naming with `-staging` suffix - Exclude development artifacts What specific issue are you encountering with the staging deployment?

copilot-pull-request-reviewer[bot] (Migrated from github.com) reviewed 2026-01-09 00:26:05 +00:00

copilot-pull-request-reviewer[bot] (Migrated from github.com) left a comment

Pull request overview

This PR fixes deployment inconsistencies in the staging workflow by aligning the ZIP creation process with the release pipeline approach.

Key Changes:

Replaced Python-based packaging script with direct zip command for consistency
Standardized ZIP naming convention to use {repo}-{version}-staging.zip format
Aligned exclusion patterns with release pipeline to match production builds

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

## Pull request overview This PR fixes deployment inconsistencies in the staging workflow by aligning the ZIP creation process with the release pipeline approach. **Key Changes:** - Replaced Python-based packaging script with direct `zip` command for consistency - Standardized ZIP naming convention to use `{repo}-{version}-staging.zip` format - Aligned exclusion patterns with release pipeline to match production builds --- 💡 <a href="/mokoconsulting-tech/moko-cassiopeia/new/main/.github/instructions?filename=*.instructions.md" class="Link--inTextBlock" target="_blank" rel="noopener noreferrer">Add Copilot custom instructions</a> for smarter, more guided reviews. <a href="https://docs.github.com/en/copilot/customizing-copilot/adding-repository-custom-instructions-for-github-copilot" class="Link--inTextBlock" target="_blank" rel="noopener noreferrer">Learn how to get started</a>.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: MokoConsulting/MokoCassiopeia#37