ci: release-tag workflow を release にリネーム#58
Merged
Conversation
tag 作成・npm publish・stackblitz 更新を担うようになり、 release-tag という名前が実態より狭くなったため release に変更する。 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
tomoemon
force-pushed
the
ci/rename-release-workflow
branch
from
May 17, 2026 07:44
b34762b to
9707ef7
Compare
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/workflows/release-tag.yamlをrelease.yamlにリネーム（workflow 名release-tag→release）CONTRIBUTING.md/ リリース skill のリリースフロー記述を実態に合わせて更新job id は
release-tagのまま維持する（GitHub の概念上のリリースタグを作る job であるため）。設計の背景
PR #55 / #57 で npm publish と stackblitz 更新を同一 workflow の後続ジョブに統合した結果、この workflow は tag 作成・GitHub release・npm publish・stackblitz ブランチ更新を担うようになった。
release-tagという workflow 名は「tag を打つだけ」という実態より狭い印象を与えるため、releaseにリネームする。npm Trusted Publishing への影響
npm Trusted Publishing は workflow ファイル名を完全一致で固定するため、リネーム後は npmjs.org 側の Trusted Publisher 設定を
release.yamlに更新する必要がある。この PR のマージ自体はリリース処理をトリガーしない（
releaseworkflow はpackage.jsonの変更でのみ発火）。そのため、マージ後に npmjs.org の設定をrelease.yamlへ変更しておけば、次回リリースから問題なく publish される。検討した代替案
release-tag.yamlのまま維持する案: 命名が実態と乖離するため見送り。Test plan
releaseworkflow が tag 作成 → publish → stackblitz 更新まで完走することを確認release.yamlに更新済みであることを確認🤖 Generated with Claude Code