Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions .github/RELEASE_POLICY.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,8 +3,8 @@
## Trigger

- A direct push to `main` or a PR merge into `main` is the only normal release event. PR checks, manual CI dispatch and version-tag pushes **do not** initiate publication.
- Before publishing, compare the entire `github.event.before..GITHUB_SHA` range, including renamed/deleted runtime files. A release is eligible **only** if the pushed commits change a shippable add-in/runtime file, runtime resource, native component, or explicitly designated distribution input.
- The repository's `.github/release-paths.txt` is the audited allowlist; the pinned shared 4FusionLab runtime-changes Action enforces it. Changes limited to README, guides, design documents, screenshots, tests, CI workflows, repository policy or GitVersion config must not publish a release.
- Before publishing, compare `GITHUB_SHA` to the newest **published** GitHub Release tag that is an ancestor of `main`. If no ZIP Release exists, use the original `github.event.before..GITHUB_SHA` push range. Deleted and renamed runtime files remain release-eligible.
- The repository's `.github/release-paths.txt` remains the audited release allowlist. README, guides, tests and CI-only changes **do not independently create a release**. A docs-only push may recover an earlier failed runtime release when eligible changes since the last published tag are still pending.
- All required existing CI checks must succeed before publishing. A failed gate means no release, no mutable tag and no replaced assets.

## Version and distribution
Expand All @@ -18,8 +18,10 @@

Runtime allowlist: `RuEn/**` (including shipped native DLL/dylib binaries) and `scripts/package.py`. Native source/build-script-only changes do not affect distributed binaries until those binaries are rebuilt and committed. Check three platform ZIPs and checksum integrity.

If a push changes no eligible runtime file, CI may run but the GitHub Release job is skipped, even when GitVersion computes a different candidate version.
When no eligible runtime input has changed since the last published release, CI may run but publication is skipped even if GitVersion computes a different version. A failed publication is retried by the next push to `main` after all normal CI gates pass; existing released tags/assets are never overwritten.

## Shared release actions

The reusable, read-only GitVersion/runtime-change/release-notes/ZIP Actions are pinned to `4FusionLab/.github` commit `ad9d60ba4aabc494b4f2c85d6c566a50ca423751`. RuEn retains its native DLL/dylib packaging, multi-OS ZIP and immutable GitHub Release publishing workflow. Unused duplicated helper scripts were retired.

**Recovery platform:** The published-release classifier is pinned separately to `2e961620a068c3ad754f6e1be05fb6e4ac68e843` with `recover-unpublished: 'true'` and read-only `github.token`. Other shared actions retain the reviewed `ad9d60ba4aabc494b4f2c85d6c566a50ca423751` pin.
4 changes: 3 additions & 1 deletion .github/workflows/release.yml
Original file line number Diff line number Diff line change
Expand Up @@ -26,11 +26,13 @@ jobs:
- name: Detect runtime changes (shared platform)
id: impact
if: github.event_name == 'push' && github.ref == 'refs/heads/main'
uses: 4FusionLab/.github/.github/actions/runtime-changes@ad9d60ba4aabc494b4f2c85d6c566a50ca423751
uses: 4FusionLab/.github/.github/actions/runtime-changes@2e961620a068c3ad754f6e1be05fb6e4ac68e843
with:
before: ${{ github.event.before }}
after: ${{ github.sha }}
paths-file: .github/release-paths.txt
recover-unpublished: 'true'
token: ${{ github.token }}

test:
needs: changes
Expand Down
Loading