Skip to content

fix: use test:unit in publish workflow and restore CI memory limits#325

Merged
Kewton merged 1 commit intomainfrom
fix/publish-test-command
Feb 20, 2026
Merged

fix: use test:unit in publish workflow and restore CI memory limits#325
Kewton merged 1 commit intomainfrom
fix/publish-test-command

Conversation

@Kewton
Copy link
Owner

@Kewton Kewton commented Feb 20, 2026

Summary

  • Publish workflow (publish.yml) の npm testnpm run test:unit に変更
  • vitest.config.ts にCI向けメモリ制限設定を復元

Background

v0.2.12のnpm publishが失敗した原因:

  1. Issue #304で npm testNODE_ENV=test vitest に変更され、テスト失敗時に正しくexit code 1を返すようになった
  2. Publish環境にはブラウザ/tmuxがなく、E2E/integrationテストが失敗する
  3. Issue #304で vitest.config.ts からCI向けメモリ制限設定が削除され、OOMリスクが復活

Changes

  • publish.yml: npm testnpm run test:unit(CIと同じくunit testのみ実行)
  • vitest.config.ts: maxConcurrency/fileParallelism のCI設定を復元

🤖 Generated with Claude Code

- Change publish.yml test step from `npm test` to `npm run test:unit`
  (E2E/integration tests lack browser/tmux in publish environment)
- Restore CI memory optimization settings removed in Issue #304
  (maxConcurrency: 1, fileParallelism: false on CI)

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@Kewton Kewton merged commit 4e48171 into main Feb 20, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant