Repository navigation
refactor(ci): retire duplicated release helpers after shared platform adoption - #8
Merged
DiegoV71 merged 3 commits intoNov 7, 2026
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.
After the repository migrated onto commit-pinned shared 4FusionLab Release Platform Actions, remove the now-unused duplicated scripts/release_changes.py and scripts/release_notes.py and update RELEASE_POLICY.md to identify the central action as authoritative. Existing release_contract.py, build scripts, native acceptance and GitHub Release publishing remain unchanged. No files in the runtime allowlist are modified, so merging must not publish a release. Verify project CI before merging.