You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
test: move server-channel integration to server and fix client typechecks (#410)
## Summary
- move server-as-channel integration tests from
`packages/client/test/client.spec.js` to
`packages/server/test/client-channel.spec.js`
- keep client tests package-local (no `@ucanto/server` /
`@ucanto/validator` imports)
- add local client execute/decode tests to restore `packages/client`
100% coverage gates
- run package workflows on pushes to all branches (`push.branches:
["**"]`) for `client`, `core`, `interface`, `principal`, `server`,
`transport`, and `validator`
## Why
The previous client test changes mixed server integration concerns into
the client package, which caused fragile TypeScript behavior in isolated
package checks.
This PR keeps boundaries clear:
- server package owns server-channel integration behavior
- client package keeps self-contained tests and coverage
## Why checks failed after merge previously
On PR #407, package CI typecheck jobs did not run on the PR head commit
(only `Validate PR title` was recorded). On merge commit `60c70da`, push
workflows ran package typechecks and surfaced failures.
So the issue was check coverage/enforcement at PR time (branch
protection/ruleset/settings), not new source changes introduced between
PR creation and merge.
## Remark
This PR now also removes `main`-only `push.branches` constraints for
package workflows by switching them to `"**"`. Combined with
`pull_request` checks and required status checks on `main`, this reduces
merge-time surprises by surfacing failures earlier on feature-branch
pushes.
---
Co-Authored-By: Oz <oz-agent@warp.dev>
0 commit comments