ci: add publish_only dispatch to republish stuck npm versions#23
Conversation
The publish job only runs when release-please cuts a release, so the versions already tagged but never landed on npm (eslint-config 0.0.4, code-style 0.0.3, prettier-config 0.0.1 — the publish that failed under the old bun publish) had no way to be (re)published. Add a workflow_dispatch publish_only path (mirrors pleaseai/ask): - release-please job is skipped on publish_only - publish job + each step also run on workflow_dispatch - npm view guard keeps it idempotent (already-published versions skip) Also give @pleaseai/prettier-config a version field (0.0.1, matching the release-please manifest) — it had none, so pack/publish couldn't resolve a version.
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request adds a version field to the package.json of the Prettier configuration package. The reviewer identified a typo in the directory name, 'perttier-config' instead of 'prettier-config', and recommended renaming it to ensure consistency with the package name.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
| @@ -1,5 +1,6 @@ | |||
| { | |||
| "name": "@pleaseai/prettier-config", | |||
| "version": "0.0.1", | |||
There was a problem hiding this comment.
현재 패키지가 위치한 디렉터리 경로가 packages/perttier-config로 되어 있어 prettier에 오타(perttier)가 존재합니다. 패키지 명인 @pleaseai/prettier-config 및 실제 도구 이름인 Prettier와 일치하도록 디렉터리명을 prettier-config로 변경하는 것을 권장합니다.
Satisfies the yaml/plain-scalar lint rule.
Deploying code-style with
|
| Latest commit: |
3d0652f
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://a156c1f2.code-style.pages.dev |
| Branch Preview URL: | https://ci-publish-only-dispatch.code-style.pages.dev |
1 participant
배경
#21로 발행 워크플로우를
bun pm pack+npm publish(tokenless OIDC)로 고쳤지만, 이미 태그된 채 npm에 안 올라간 버전들을 발행할 경로가 없습니다:@pleaseai/eslint-config@pleaseai/code-style@pleaseai/prettier-configpublishjob은 release-please가 새 릴리스를 cut할 때만 돌기 때문에, 위 버전들(옛bun publish로 시도하다 실패한 것들)을 다시 발행할 방법이 없습니다. 실패한 옛 런을 re-run하면 그 커밋 시점의 옛 워크플로우로 돌아 또 실패합니다.변경
자매 repo
pleaseai/ask와 동일하게workflow_dispatchpublish_only경로를 추가합니다:publish_only디스패치 시release-pleasejob은 skippublishjob과 각 스텝이workflow_dispatch에서도 실행 (always()+inputs.publish_only)npm view가드로 멱등성 유지 → 이미 올라간 버전은 자동 skip, 현재package.json버전만 발행@pleaseai/prettier-config에version필드(0.0.1, manifest와 일치) 추가 — 없어서 pack/publish가 버전을 못 잡던 문제 해결머지 후 트리거
trusted publisher 설정은 완료된 상태이므로, 머지 후:
→ 현재 버전(eslint 0.0.4 / code-style 0.0.3 / prettier 0.0.1)이 OIDC로 발행됩니다.
검증
bun pm pack --dry-run→pleaseai-prettier-config-0.0.1.tgz등 tarball 이름 확인