Files
SteamlessController/.signpath/artifact-configurations/exes.xml
T
Dylan DeverillandClaude Opus 5.5 1a1253a384 Build and sign releases through SignPath on GitHub Actions
SignPath Foundation signs only what a trusted build system built from the
repository, so releases move from local builds to a workflow. A tag push
builds, signs the three executables, compiles the installer around the
signed copies, signs the installer, and opens a draft release. A manual run
does the same under test-signing, without the release.

The README gains the code signing policy the Foundation requires, including
a privacy note for the Google Fonts request the remap window makes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-22 22:57:33 -07:00

26 lines
904 B
XML

<?xml version="1.0" encoding="utf-8"?>
<!--
Round one of a release: the three executables the installer packages.
The file of record is the copy pasted into SignPath's web UI under the
project's artifact configuration with slug "exes". This copy is here so the
configuration is reviewed and versioned alongside the workflow that submits
to it. Change both together.
The ViGEmBus installer is deliberately absent. It is nefarius's binary,
already signed by them, and never passes through SignPath.
-->
<artifact-configuration xmlns="http://signpath.io/artifact-configuration/v1">
<zip-file>
<pe-file path="SteamlessController.exe">
<authenticode-sign/>
</pe-file>
<pe-file path="SteamlessDeviceCycle.exe">
<authenticode-sign/>
</pe-file>
<pe-file path="ViGEmBusProbe.exe">
<authenticode-sign/>
</pe-file>
</zip-file>
</artifact-configuration>