Repository navigation
feat(ci): recover previously missed runtime releases on next push - #12
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
runtime-changesto reviewed platform commit2e961620a068c3ad754f6e1be05fb6e4ac68e843; retain other tested shared Action pins and GitVersion.Tool 6.8.2.recover-unpublished: 'true'and read-onlygithub.tokenfor published-release lookup..github/RELEASE_POLICY.mdto clarify that docs-only pushes can retry earlier runtime publication failures.Post-merge publication expectation
Since v1.0.0, scripts/package.py has changed; this PR may automatically recover the pending release.
This PR does not itself create tags or publish artifacts on PR. The first merge into
mainwill use the new detector; any accumulated eligible runtime change can produce the expected automatic release only after full project CI passes.