Allow large amount of files in wix

[t0mdavid-m]

When adding additional dependencies in umetaflow, the file count limit of the streamlit.cab file was exceeded. This PR ensures that files are automatically distributed across multiple .cab files if necessary.

I also enabled the test-win-exe-w-embed-py GA on PR to main. However, from what I saw it does not seem to test anything. @Arslan-Siraj can this be removed?

Summary by CodeRabbit

• Chores
  • Enhanced the installer packaging process for improved media handling and accurate file path resolution.
• Tests
  • Updated the Windows testing workflow to be manually triggered, offering more controlled and reliable test runs.

[Arslan-Siraj]

Thanks for contributing.
I tested work fine.

When adding additional dependencies in umetaflow, the file count limit of the streamlit.cab file was exceeded. This PR ensures that files are automatically distributed across multiple .cab files if necessary.

I also enabled the test-win-exe-w-embed-py GA on PR to main. However, from what I saw it does not seem to test anything. @Arslan-Siraj can this be removed?

This is helpful for quickly testing the Wix packaging without building OpenMS (I will suggest keeping it as workflow_dispatch ).

[coderabbitai]

Walkthrough

The changes modify two GitHub Actions workflows. Both workflows now replace the <Media> element with <MediaTemplate> in the WiX XML configuration and update the linking command by adding the -b SourceDir option to process .wixobj files into a .msi installer. Additionally, the test workflow no longer triggers on pushes to the main branch (using workflow_dispatch instead) and includes a minor formatting update in the artifact upload step. No public or exported entities were altered.

Changes

File(s)	Change Summary
.github/workflows/build-windows-executable-app.yaml .github/workflows/test-win-exe-w-embed-py.yaml	Replaced <Media> with <MediaTemplate> in the WiX XML, and added the -b SourceDir option to the linking command for .wixobj files to .msi conversion.
.github/workflows/test-win-exe-w-embed-py.yaml	Removed the automatic push trigger for the main branch (now using workflow_dispatch) and adjusted the artifact upload path formatting.

Sequence Diagram(s)

sequenceDiagram
    participant U as User
    participant GH as GitHub Actions
    participant Wix as WiX Tool
    U->>GH: Manually trigger workflow (workflow_dispatch)
    GH->>Wix: Process WiX XML (using MediaTemplate)
    Wix->>GH: Generate .wixobj files
    GH->>Wix: Link .wixobj files into .msi using -b SourceDir
    GH->>GH: Upload artifacts (with formatting adjustments)

Loading

Possibly related PRs

• Temp Fix for Windows CI #161: The changes in the main PR and the retrieved PR both involve modifications to the WiX XML configuration and the linking command for .wixobj files, indicating a direct relationship at the code level.

Poem

I'm a hopping rabbit in the code field so bright,
With MediaTemplate shining in the installer light.
Linking with "-b SourceDir" is now our new tune,
Manual triggers set the workflow in bloom.
Cheers from my bunny heart—code magic tonight! 🐰

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2c788c1 and 9ec5138.

📒 Files selected for processing (1)

• .github/workflows/build-windows-executable-app.yaml (2 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• .github/workflows/build-windows-executable-app.yaml

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.