diff --git a/RELEASE_PLATFORM.md b/RELEASE_PLATFORM.md index 7e339d3..a63951b 100644 --- a/RELEASE_PLATFORM.md +++ b/RELEASE_PLATFORM.md @@ -7,7 +7,7 @@ Central, reusable Actions for 4FusionLab repositories. Source: [4FusionLab/.gith | Action | Purpose | Required context | | --- | --- | --- | | `.github/actions/resolve-version` | GitVersion.Tool **6.8.2**, returns numeric version or SemVer | Complete checkout (`fetch-depth: 0`) | -| `.github/actions/runtime-changes` | Compare the full push range to `.github/release-paths.txt` | Full checkout, `before` and `after` commit SHA | +| `.github/actions/runtime-changes` | Compare unpublished runtime changes since last published ZIP Release (opt-in), or original push range | Full checkout, `before` / `after` SHA and read-only `github.token` | | `.github/actions/release-notes` | Use reviewed version notes or generate from history | Full checkout and writable `runner.temp` file | | `.github/actions/verify-archive` | Validate package ZIP, SHA-256, optional Fusion manifest and nonempty notes | Built ZIP(s) and checksum files | @@ -26,17 +26,21 @@ Central, reusable Actions for 4FusionLab repositories. Source: [4FusionLab/.gith before: ${{ github.event.before }} after: ${{ github.sha }} paths-file: .github/release-paths.txt + recover-unpublished: 'true' + token: ${{ github.token }} ``` -A product publishes only on `push` to `main` after its existing tests, build, notes and archive verification pass **and** the runtime-changes Action returns `release=true`. Skip publishing for PR, `workflow_dispatch` and documentation-only changes. +A product publishes only on `push` to `main` after its existing tests, build, notes and archive verification pass **and** the runtime-changes Action returns `release=true`. PR and `workflow_dispatch` never publish. A docs-only push may recover a previously **missed** release, but cannot create a release unless unpublished shippable runtime changes exist since the most recent published ancestor tag. The original push-range behavior remains the default unless `recover-unpublished` is enabled. ### Safety contract - All composite Actions here are **read-only** and create no tags, GitHub Releases or Pages deployments. Final GitHub Release publication stays in the product repository to preserve its acceptance gates, channel semantics and packaging. - No `contents: write` permission is granted by these Actions. - A previously published version or mismatched immutable Git tag must never be overwritten. -- Changing tests or docs alone must not create releases. Runtime changes, including additions, deletions and renames, do. +- Changes to tests, docs and workflows are not release-eligible themselves. A later docs-only push may retry unpublished runtime changes after an earlier CI/publisher failure. Runtime additions, deletions and renames remain release-eligible. - Do not assume that a successful CI ZIP build is proof of a native Fusion CAD integration test. +Full details, failure behavior and migration guidance: [RELEASE_RECOVERY.md](RELEASE_RECOVERY.md). For recovered releases, **do not apply `push.paths` filters** to the main publishing workflow, since that would block docs-only retry triggers. + ### Execution model Repositories keep existing Linux/macOS/Windows CI matrices, Fusion acceptance checks, distribution builders and publishing gates. Centralized Actions only replace duplicated version resolution, path filtering, notes generation and archive validation.