Brandon Thomas 3d6050b931 Release workflow: pass the Azure signing secrets so Windows builds are signed (#3794) ... Since the release workflow moved to storytold/craft-common-actions, it has passed only the Apple and WINDOWS_CERTIFICATE secrets. The signing job reads values from the release environment, but only for names the caller lists, so the AZURE_* names that Trusted Signing uses came through empty and Windows builds would ship unsigned. Same fix as storytold/craft-launcher#174. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>		2026-10-12 11:08:34 -04:00
..
ci.yml	psd: harden the standalone binary parsers (fuzz + property tests, gradient/swatch correctness) (#3542)	2026-10-12 02:49:08 -04:00
docs.yml	docs: add mdBook and security documentation foundation (#35)	2026-10-04 12:31:18 -04:00
freebsd.yml	CI: never cancel main's runs; trim per-PR runner time (#800)	2026-10-07 19:46:18 -04:00
packaging-lint.yml	Security: verify AppImage build inputs (#2270)	2026-10-11 22:33:26 -06:00
perf-nightly.yml	Scorecard: cargo xtask perf + scorecard, budgets, checklists, nightly perf (#221) (#239) (#239)	2026-10-05 10:53:02 -04:00
release.yml	Release workflow: pass the Azure signing secrets so Windows builds are signed (#3794)	2026-10-12 11:08:34 -04:00
windows-arm64.yml	ci: refactor workflows to use storytold/craft-common-actions (#3432)	2026-10-11 11:50:48 -04:00