Skip to content

Conversation

@myieye
Copy link
Collaborator

@myieye myieye commented Sep 15, 2025

No description provided.

@coderabbitai
Copy link

coderabbitai bot commented Sep 15, 2025

📝 Walkthrough

Walkthrough

Updated the Windows SDK version in the GitHub Actions workflow for MSIX bundling from 10.0.19041.0 to 10.0.26100.0 by changing the SdkVersion assignment, thereby altering the sdkToolsPath and referenced SDK. No other logic or control flow changes.

Changes

Cohort / File(s) Summary
CI workflow: Windows SDK bump
\.github/workflows/fw-lite.yaml
Updated SdkVersion from 10.0.19041.0 to 10.0.26100.0, affecting sdkToolsPath and the SDK used during MSIX bundling.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

I twitch my whiskers at version delight,
New SDK shines in the build’s moonlight.
Hops through workflows, paths realigned,
Bundles crisp, with tools refined.
Thump! The CI meadow hums just right. 🥕✨

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)
Check name Status Explanation Resolution
Description Check ❓ Inconclusive There is no pull request description provided, so we cannot verify whether the author's intent, rationale, or any testing/impact notes accompany the workflow SDK update beyond the commit-level summary. Because the description is missing rather than explicitly related or off-topic, the check is inconclusive. Reviewers currently lack context that would speed review and clarify risks or follow-up steps. Please ask the author to add a short description (1–3 sentences) stating that .github/workflows/fw-lite.yaml was updated to use Windows SDK 10.0.26100.0 to match the windows-2025 GHA runner, include the reason for the change, and note any testing performed or expected impact on builds so reviewers have necessary context.
✅ Passed checks (2 passed)
Check name Status Explanation
Title Check ✅ Passed The PR title "Update to use available sdk on gha-runner window-2025" accurately describes the primary change (updating the Windows SDK used on the GitHub Actions windows-2025 runner as reflected in .github/workflows/fw-lite.yaml) and is concise and focused for a reviewer scanning history. It highlights the main intent rather than listing files or unrelated details. Minor grammar and capitalization issues do not make it misleading.
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.
✨ Finishing touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch fix-fw-lite-build-on-gha-windows-2025

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

  • Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
  • Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@argos-ci
Copy link

argos-ci bot commented Sep 15, 2025

The latest updates on your projects. Learn more about Argos notifications ↗︎

Build Status Details Updated (UTC)
default (Inspect) ✅ No changes detected - Sep 15, 2025, 8:40 AM

@github-actions
Copy link

UI unit Tests

  1 files  ±0   45 suites  ±0   27s ⏱️ ±0s
110 tests ±0  110 ✅ ±0  0 💤 ±0  0 ❌ ±0 
158 runs  ±0  158 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit f16e312. ± Comparison against base commit 3bf7e37.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
.github/workflows/fw-lite.yaml (2)

320-324: Make SDK discovery dynamic and prefer x64 tools.

Hard‑coding 10.0.26100.0 and x86 is brittle and will break when the image rotates or if that SDK isn’t installed. Resolve the newest installed Windows 10 SDK at runtime and use the native architecture (x64 on GHA). Also, invoke MakeAppx via its full path.

Apply this diff:

-          $SdkVersion = '10.0.26100.0'
-          $Architecture = 'x86'
-          $sdkToolsPath = Join-Path -Path 'C:\Program Files (x86)\Windows Kits\10\bin' -ChildPath $SdkVersion -AdditionalChildPath $Architecture
-          $env:Path += ";$sdkToolsPath"
+          $kitRoot = 'C:\Program Files (x86)\Windows Kits\10\bin'
+          $arch = if ([Environment]::Is64BitOperatingSystem) { 'x64' } else { 'x86' }
+          $sdk = Get-ChildItem -Path $kitRoot -Directory |
+            Where-Object { Test-Path (Join-Path $_.FullName $arch) } |
+            Sort-Object Name -Descending | Select-Object -First 1
+          if (-not $sdk) { throw "No Windows 10 SDK found under $kitRoot" }
+          $sdkToolsPath = Join-Path $sdk.FullName $arch
+          $makeAppx = Join-Path $sdkToolsPath 'MakeAppx.exe'
+          if (-not (Test-Path $makeAppx)) { throw "MakeAppx.exe not found at $makeAppx" }

And update the invocation below to use the resolved path:

& $makeAppx bundle /v /bv ${{ needs.build-and-test.outputs.semver-version }}.1 /d . /p ../sign/FwLiteMaui.msixbundle

285-301: Optional: Pin the runner if you rely on a specific SDK.

If you must use a particular SDK version, consider pinning runs-on to the image that guarantees it (e.g., windows-2025) or add a matrix fallback to older SDKs. Otherwise, keep dynamic discovery as above.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3bf7e37 and f16e312.

📒 Files selected for processing (1)
  • .github/workflows/fw-lite.yaml (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)
  • GitHub Check: frontend
  • GitHub Check: Build FW Lite and run tests
  • GitHub Check: frontend-component-unit-tests
🔇 Additional comments (1)
.github/workflows/fw-lite.yaml (1)

320-327: Verify the Windows SDK and MakeAppx on a windows-latest runner (run PowerShell on Windows)

The prior run produced no output because PowerShell was executed in a Bash/Linux shell — rerun this on a windows-latest (Windows) runner or locally on Windows and paste the output.

#!/usr/bin/env pwsh
Get-ChildItem 'C:\Program Files (x86)\Windows Kits\10\bin' -Directory | Select-Object -ExpandProperty Name
$arch = if ([Environment]::Is64BitOperatingSystem) { 'x64' } else { 'x86' }
Get-Command MakeAppx.exe -All | Format-Table CommandType, Name, Source -AutoSize
Get-ChildItem "C:\Program Files (x86)\Windows Kits\10\bin\*\$arch\MakeAppx.exe" -ErrorAction SilentlyContinue | Select-Object FullName

@myieye myieye merged commit 40c2ea9 into develop Sep 15, 2025
12 checks passed
@myieye myieye deleted the fix-fw-lite-build-on-gha-windows-2025 branch September 15, 2025 09:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants