conco/OpenMaidEngine
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 3 Wiki Activity

Close out dual-platform release CI
All checks were successful
Core validation / Linux core gate (push) Successful in 54s
Details
Release builds / Linux x64 artifact (push) Successful in 1m18s
Details
Release builds / Windows x64 artifact (push) Successful in 1m19s
Details
Release builds / Publish tagged Gitea release (push) Has been skipped
Details

Browse Source
This commit is contained in:
gamer147
2026-08-03 23:08:29 -04:00
parent 93d8236371
commit 0926125cbd
3 changed files with 15 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
docs/platform-portability.md
View File

@@ -156,8 +156,9 @@ Windows received structural cross-target verification only. Source-only paired c
pass. The hosted develop run at `d657c63` completed both platform builds and correctly skipped tag promotion on
2026-08-03, accepting the paired non-tag path. Its core job initially failed before checkout on a transient
runner DNS lookup for GitHub, then passed unchanged on retry; this was infrastructure availability rather than a
validation failure. The user must still select a future tag for the end-to-end release proof; `v0.1.0` remains
unchanged.
validation failure. The lightweight `v0.2.0` tag at `93d8236` then completed both platform jobs and promotion on
2026-08-03. The resulting Gitea release exposes exactly the Linux archive, Windows archive, and
`RELEASE-SHA256SUMS`, accepting the dual-platform CI/CD path end to end; `v0.1.0` remains unchanged.
Code signing, an installer, Windows-on-Linux execution, and retroactively modifying the accepted Linux-only
`v0.1.0` release are outside this effort. A future signing slice can use `osslsigncode` and protected credentials