ci(release): trigger docs build after stable publish#18
Merged
Palbahngmiyine merged 1 commit intomasterfrom Apr 20, 2026
Merged
ci(release): trigger docs build after stable publish#18Palbahngmiyine merged 1 commit intomasterfrom
Palbahngmiyine merged 1 commit intomasterfrom
Conversation
release-please가 기본 GITHUB_TOKEN으로 GitHub Release를 생성할 때, GitHub Actions 정책상 `release: [published]` 이벤트가 다음 워크플로를 트리거하지 않는다. 이 제약으로 v6.0.0 이후 `build-docs.yaml`이 자동으로 돌지 않아 API Reference가 구버전으로 남아 있었다. `workflow_dispatch`는 GITHUB_TOKEN으로도 기동이 허용되므로, publish 잡 성공 후 `gh workflow run build-docs.yaml --ref $TAG`로 명시적 디스패치 하는 `trigger-docs` 잡을 추가한다. master 브랜치이고 release_created가 true일 때만 동작하므로 beta 경로나 release PR 생성 단계에서는 트리거 되지 않는다. `--ref $TAG`로 릴리즈 태그 기준 커밋에서 문서를 빌드해 릴리즈와 동일한 소스 상태가 보장된다. build-docs.yaml 자체는 그대로 유지 — 수동 재빌드 경로와 향후 PAT 전환 시의 release 이벤트 경로 모두 보존. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
8 tasks
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
GITHUB_TOKEN으로 생성한 GitHub Release의release: [published]이벤트가 다음 워크플로를 트리거하지 않는 GitHub Actions 정책이 원인이 되어,solapi-v6.0.0이후build-docs.yaml이 자동으로 돌지 않았다.workflow_dispatch는GITHUB_TOKEN으로도 정상 기동 가능하므로,release.yml에trigger-docs잡을 추가해publish성공 후gh workflow run build-docs.yaml --ref \$TAG로 명시적 디스패치한다.Changes
.github/workflows/release.yml:trigger-docs잡 추가needs: [release-please, publish]needs.release-please.outputs.release_created == 'true'+needs.publish.result == 'success'+github.ref_name == 'master'permissions: actions: write(최소 권한)--ref \$TAG사용Rationale
workflow_run트리거로 교체concurrency: pages그룹과actions/deploy-pages제약 유지가 불편. 수동 재빌드도 손실. 기각gh workflow run디스패치 (채택)Test plan
python3 yaml.safe_load)lint/test/build)만 검증 — 실제 trigger 경로는 다음 정식 릴리즈에서 확인 필요fix/typedoc-build-errorsPR 머지 후gh workflow run build-docs.yaml --ref solapi-v6.0.0으로 수동 반영 예정Related
🤖 Generated with Claude Code