Repository navigation
ci: reuse shared release platform components - #8
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.
Shared Release Platform rollout
Replace duplicated version calculation, release-eligible file filtering and release notes with pinned, read-only 4FusionLab/.github actions (commit ad9d60ba4aabc494b4f2c85d6c566a50ca423751). Shared archive verification adds another ZIP/SHA-256 check. Keep each repository's existing CI validation, runtime path allowlist, package builder and automated publication conditions.
Only infrastructure files change. This PR cannot trigger a GitHub Release. Validate project workflows and avoid replacing immutable historical releases.