ci: remove binary upload workflow and SKIP_COMMIT_HELPER_POSTINSTALL#68
Merged
yujeong-jeon merged 1 commit intomainfrom Mar 5, 2026
Merged
Conversation
Binaries are now bundled inside platform npm packages, so there is no longer a need to upload assets to GitHub Releases after publish. - Remove release-asset.yaml workflow entirely - Remove upload-assets job and checkCommitHelperGo step from release.yaml - Remove SKIP_COMMIT_HELPER_POSTINSTALL env var from all workflows Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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
1 participant
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.
Summary
release-asset.yaml워크플로우 삭제 (GitHub Releases에 바이너리 업로드하는 용도 → 더 이상 불필요)release.yaml에서upload-assetsjob,checkCommitHelperGostep,SKIP_COMMIT_HELPER_POSTINSTALL환경변수 제거detect-changed-packages.yml에서SKIP_COMMIT_HELPER_POSTINSTALL환경변수 제거platform-specific npm packages로 바이너리를 배포하는 방식으로 전환되면서 더 이상 GitHub Releases를 통한 바이너리 배포가 필요하지 않습니다.
Related: #60