Repository navigation
ci: consume pinned shared release platform without changing publication policy - #7
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
Migrate the project's GitVersion calculation, runtime-impact detection and release-note generation onto read-only reusable composite Actions in
4FusionLab/.github, pinned to immutable commit ad9d60ba4aabc494b4f2c85d6c566a50ca423751. Add shared ZIP/SHA-256/Fusion manifest validation before publishing.Keep the existing project-specific build scripts, native CAD acceptance gates, three-OS test matrix, distribution filenames, trigger conditions (only runtime changes on
main) and publisher unchanged. No manual tags.Scope: only GitHub workflows, no add-in or packaging runtime files. The merge must not create a GitHub Release. Verify all CI checks before merging.