Files
solvecraft/packaging/windows/signpath-artifact-configuration.xml
bherbruck 045aa64b07 Drop the SolveCraft name: no solvecraft-cli, SOLVECRAFT_* variables or .solvecraft association (#16939)
* Drop the SolveCraft name: no solvecraft-cli, SOLVECRAFT_* variables or .solvecraft association

Remove the solvecraft-cli forwarding binary and its packaging, the
SOLVECRAFT_* environment fallbacks, the migration from the old
product-name settings folders and storage keys, and the .solvecraft file
association and extension handling. Designs saved under the old name
still open, by their contents.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Drop the remaining SolveCraft package and app-ID shims

Remove the deb/rpm Replaces/Conflicts/Provides on solvecraft, the
solvecraft AppImage zsync and Flatpak repo copies, and the
ai.storyteller.solvecraft app ID (Flatpak end-of-life rebase, AppStream,
X-Flatpak-RenamedFrom, ~/.var/app grant, AppRun cleanup, eframe app.ron
copy). ai.storyteller.solidcraft stays.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Format

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Clippy: pass the old folder as a slice

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-16 14:29:58 +00:00

35 lines
1.5 KiB
XML

<?xml version="1.0" encoding="utf-8"?>
<!--
SignPath artifact configuration for the Windows release (project `solidcraft`).
This file is the source of truth: paste it into SignPath (Projects > solidcraft > Artifact
Configurations > the default configuration > Edit) whenever it changes, so the two stay in sync.
.github/workflows/release.yml submits two signing requests per architecture. GitHub stores every
workflow artifact as a zip, so the root element is a zip-file and the files sit at its top level:
1. the binaries, before they are packed: solidcraft.exe, solidcraft-cli.exe
2. the installer built from those signed binaries: solidcraft-<version>-windows-<arch>.msi
Each set is optional (min-matches="0") because each request carries only one of the two shapes.
The workflow checks afterwards that every file it sent came back with an Authenticode signature,
so a request that matched nothing fails the build instead of shipping unsigned files.
-->
<artifact-configuration xmlns="http://signpath.io/artifact-configuration/v1">
<zip-file>
<pe-file-set>
<include path="solidcraft.exe" min-matches="0" />
<include path="solidcraft-cli.exe" min-matches="0" />
<for-each>
<authenticode-sign />
</for-each>
</pe-file-set>
<msi-file-set>
<include path="solidcraft-*-windows-*.msi" min-matches="0" />
<for-each>
<authenticode-sign />
</for-each>
</msi-file-set>
</zip-file>
</artifact-configuration>