Windows installer not produced by mach package
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 84/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- github-actions
- Domain
- build-system, ci-cd
Research direction
Start with .github/workflows/browser.yml and inspect the Windows build, packaging, and Upload Artifacts steps. Run or review the existing mach package flow, then verify the separate mach repackage installer step uses the generated ZIP. Done means a successful Windows build uploads the installer from obj-tf-release/dist/foxhound-*.en-US.win64.installer.exe.
Written by the indexing model from the issue text.
Description
Windows installer not produced by mach package
Describe the bug
The GitHub Actions workflow uploads the Windows build artifact from:
obj-tf-release/dist/install/sea/foxhound-*.en-US.win64.installer.exe
This path no longer exists. It was removed upstream in Bug 1970692 ("Get rid of install/sea"), which landed between
Firefox 140 and 149.
Additionally, mach package only produces a .zip archive (dist/foxhound-*.en-US.win64.zip). The .installer.exe requires a separate mach repackage installer step that
is not currently in the workflow.
Steps to reproduce
Run the Windows CI build — the "Upload Artifacts" step will silently upload nothing because the glob matches no files.
Expected behavior
A foxhound-*.en-US.win64.installer.exe artifact is uploaded after a successful Windows build.
Also see: https://github.com/SAP/project-foxhound/actions/runs/26110426051/job/76785878361
Run actions/upload-artifact@v4
Warning: No files were found with the provided path: obj-tf-release/dist/install/sea/foxhound-*.en-US.win64.installer.exe. No artifacts will be uploaded.
Fix
Two changes are needed in .github/workflows/browser.yml:
- Add a
mach repackage installerstep aftermach package, passing the produced.zipas input. - Update the artifact upload path to
obj-tf-release/dist/foxhound-*.en-US.win64.installer.exe.
- Dominant language
- JavaScript
- Stars
- 178
- Forks
- 30
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from SAP/project-foxhound
-
chore upstream
Difficulty 5/5 Over a week Newbie friendliness 45/100
SAP/project-foxhound#387 ·
-
bug Incomplete taint propagation
SAP/project-foxhound#386 · 1 comment · 2 assignees ·
-
Foxhound and WPT Openbug upstream
SAP/project-foxhound#385 · 1 comment · 1 assignee ·
-
"Flaky" escape Test Openbug javascript
SAP/project-foxhound#384 · 1 comment · 2 assignees ·
-
bug
SAP/project-foxhound#382 · 1 assignee ·
All issues in SAP/project-foxhound
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
[Block] Latest Posts [Type] Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
sugarlabs/musicblocks#8847 ·