Skip to content

ci: use an absolute bundle output dir in the release workflow - #13

Merged
maoyeedy merged 1 commit into
masterfrom
fix/release-bundle-dir
Oct 16, 2026
Merged

maoyeedy merged 1 commit into
masterfrom
fix/release-bundle-dir

Conversation

@maoyeedy

Copy link
Copy Markdown
Owner

Problem

The v0.1.4 tag build (run 38843566297) built the bundle but failed at "Find MSIX bundle": MSBuild resolved the relative -p:AppxPackageDir=UnityExtension\BundleArtifacts\ against the project folder, so the bundle was written to UnityExtension\UnityExtension\BundleArtifacts\ while the step searched UnityExtension\BundleArtifacts\ from the repo root.

Fix

  • release-msix.yml: PACKAGE_DIR is now ${{ github.workspace }}\UnityExtension\BundleArtifacts (absolute).
  • ci.yml bundle-build: pass the same AppxPackageDir override and look for the bundle there, so this path logic is covered on PRs.

Verification

  • actionlint passes.
  • Local build with an absolute -p:AppxPackageDir writes UnityExtension_0.1.4.0_x64_arm64.msixbundle under that directory.
  • This PR's bundle-build job exercises the CI form.

After merge, v0.1.4 has to be re-pointed at the new master (the tag ruleset blocks deletion).

MSBuild resolves a relative -p:AppxPackageDir against the project folder, so
the v0.1.4 tag build wrote UnityExtension/UnityExtension/BundleArtifacts while
the 'Find MSIX bundle' step searched UnityExtension/BundleArtifacts and failed.
Make PACKAGE_DIR absolute in release-msix.yml and pass the same override in the
PR bundle-build job so this path logic is exercised before a tag.
@maoyeedy
maoyeedy merged commit 74aedd2 into master Oct 16, 2026
3 checks passed
@maoyeedy
maoyeedy deleted the fix/release-bundle-dir branch October 16, 2026 03:10
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.

1 participant