Skip to content

fix(publish.yml): add dispatch to ORDER build list#96

Merged
kjgbot merged 1 commit into
mainfrom
fix/publish-yml-dispatch-order
May 23, 2026
Merged

fix(publish.yml): add dispatch to ORDER build list#96
kjgbot merged 1 commit into
mainfrom
fix/publish-yml-dispatch-order

Conversation

@kjgbot
Copy link
Copy Markdown
Contributor

@kjgbot kjgbot commented May 23, 2026

Summary

One-line fix to .github/workflows/publish.yml's ORDER= build list so dispatch's dist/ exists when the upload step copies it. Phase 0 PR #95 added dispatch to the PACKAGES matrix and to package.json workspaces, but missed this second list further down in the same file.

Failed run

https://github.com/AgentWorkforce/agent-assistant/actions/runs/26327788454 — "Build, validate, and version" / "Upload build artifacts" step failed with:

cp: cannot stat 'packages/dispatch/dist': No such file or directory

Test plan

  • After merge: re-trigger publish via gh workflow run publish.yml -f package_group=runtime-core -f version=minor. Confirm @agent-assistant/persona@0.5.0 + @agent-assistant/dispatch@0.1.0 ship to npm.

🤖 Generated with Claude Code

The Phase 0 PR added @agent-assistant/dispatch to the runtime-core
PACKAGES matrix but missed the ORDER= list further down in the same
workflow file. As a result the publish job built every other package
but skipped dispatch, then failed at "Upload build artifacts" with
`cp: cannot stat 'packages/dispatch/dist': No such file or directory`.

This fix inserts `dispatch` after `persona` in ORDER (same position as
in PACKAGES), so the dist directory exists when the upload step copies
it. Both packages are types-only with zero runtime deps; build order
between them doesn't matter.

Failed run: https://github.com/AgentWorkforce/agent-assistant/actions/runs/26327788454

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 23, 2026

Warning

Review limit reached

@kjgbot, we couldn't start this review because you've used your available PR reviews for now.

Your plan currently allows 1 review/hour. Refill in 32 minutes and 39 seconds.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more review capacity refills, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than trial, open-source, and free plans. In all cases, review capacity refills continuously over time.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 3167eda7-0683-4f56-a13a-7e1d78e7f9db

📥 Commits

Reviewing files that changed from the base of the PR and between 38c3dcf and bd46a2d.

📒 Files selected for processing (1)
  • .github/workflows/publish.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/publish-yml-dispatch-order

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@kjgbot kjgbot merged commit a1b5389 into main May 23, 2026
3 checks passed
@kjgbot kjgbot deleted the fix/publish-yml-dispatch-order branch May 23, 2026 08:17
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