Skip to content

feat(ci): recover previously missed runtime releases on next push - #15

Merged
DiegoV71 merged 2 commits into
mainfrom
ci/recover-unpublished-releases-20261107
Nov 7, 2026
Merged

DiegoV71 merged 2 commits into
mainfrom
ci/recover-unpublished-releases-20261107

Conversation

@DiegoV71

@DiegoV71 DiegoV71 commented Nov 7, 2026

Copy link
Copy Markdown
Contributor

Purpose

Opt into the shared 4FusionLab ability to recover unpublished runtime changes since the last successfully published ZIP Release tag. A failed CI/publishing run must not permanently lose a release if the next push only edits README or documentation.

Changes

  • Pin only runtime-changes to reviewed platform commit 2e961620a068c3ad754f6e1be05fb6e4ac68e843; retain other tested shared Action pins and GitVersion.Tool 6.8.2.
  • Pass recover-unpublished: 'true' and read-only github.token for published-release lookup.
  • Keep the existing runtime allowlist, PR CI, immutable tag checks, manifest/ZIP validation, and publication permissions.
  • Update .github/RELEASE_POLICY.md to clarify that docs-only pushes can retry earlier runtime publication failures.

Post-merge publication expectation

Since v1.0.0, scripts/build.py has changed; publication must preserve the repository's native-CAD stable/prerelease gate.

This PR does not itself create tags or publish artifacts on PR. The first merge into main will use the new detector; any accumulated eligible runtime change can produce the expected automatic release only after full project CI passes.

@DiegoV71
DiegoV71 merged commit 7f7f282 into main Nov 7, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant