Craft Windows x64 build repository

Build-only Forgejo workflow for the release branches of:

• storytold/PhotoCraft
• storytold/VectorCraft

The workflow builds each application on windows-latest and uploads the MSI installer and portable ZIP as workflow artifacts. It does not push source changes, create tags, publish releases, or trigger another workflow.

Run

1. Create this repository in the authorized Forgejo account/org (suggested name: craft-windows-builds).
2. Add the contents of this folder to the repository's default branch.
3. Ensure the runner can read both source repositories.
4. Run Actions → Windows x64 release artifacts → Run workflow.
5. Optionally enter a version override. An empty value uses the checked-out repository version.
6. Download the two artifacts: photocraft-windows-x64 and vectorcraft-windows-x64.

The source repositories are always checked out at branch release by the workflow. The packaging entry point is the existing packaging/windows/package.ps1 script in each source repository, invoked with -Arch x86_64.

Required access and configuration

• Forgejo Actions must support actions/checkout, dtolnay/rust-toolchain, and actions/upload-artifact.
• The workflow token/runner identity needs read access to both source repositories.
• A Windows runner with PowerShell, .NET, Rust, and network access for the toolchain is required.
• WiX v5.0.2 is installed by the workflow.
• CRAFT_FONTS_REQUIRED=0 is used because this build repository does not check out craft-fonts. If either packaging script requires embedded fonts, add an authorized fonts checkout and change this setting.

Secrets

No secret is required for the unsigned build-only workflow. Do not place credentials in this repository.

If release/tag automation is later added by an explicitly authorized operator, use only a Forgejo secret named RELEASE_TOKEN. Do not add that secret to this build job, and do not implement tag/release publication without explicit authorization.

Optional Windows code-signing credentials from the source packaging script must be added only after approval and only as Forgejo secrets. They are deliberately not wired into this workflow.

Safety boundary

This repository is intentionally separate from the application repositories. It reads release branches and produces CI artifacts only. It does not modify storytold/PhotoCraft or storytold/VectorCraft.

Layout

.forgejo/workflows/windows-x64.yml
README.md
docs/VALIDATION.md