Packages
@agentworkforce/events@4.1.49(tag:events-v4.1.49)@agentworkforce/persona-kit@4.1.49(tag:persona-kit-v4.1.49)@agentworkforce/runtime@4.1.49(tag:runtime-v4.1.49)@agentworkforce/compose@4.1.49(tag:compose-v4.1.49)@agentworkforce/delivery@4.1.49(tag:delivery-v4.1.49)@agentworkforce/workload-router@4.1.49(tag:workload-router-v4.1.49)@agentworkforce/persona-registry@4.1.49(tag:persona-registry-v4.1.49)@agentworkforce/deploy@4.1.49(tag:deploy-v4.1.49)@agentworkforce/review-kit@4.1.49(tag:review-kit-v4.1.49)@agentworkforce/turn-kit@4.1.49(tag:turn-kit-v4.1.49)@agentworkforce/mcp-workforce@4.1.49(tag:mcp-workforce-v4.1.49)@agentworkforce/daytona-runner@4.1.49(tag:daytona-runner-v4.1.49)@agentworkforce/local-surface@4.1.49(tag:local-surface-v4.1.49)@agentworkforce/cli@4.1.49(tag:cli-v4.1.49)agentworkforce@4.1.49(tag:agentworkforce-v4.1.49)
Changes
None. This release carries the same code as 4.1.48 — the two publish runs
were dispatched 38 seconds apart, and the second bumped every package a
version while publishing identical artifacts.
The fix people are looking for, #325
(authored persona.ts files resolving @agentworkforce/* imports on a fresh
global install), shipped in 4.1.48 and is present here.
4.1.49 is what npm serves as latest, so this release exists to keep the
releases page consistent with the registry. Its release commit could not be
pushed at the time (the concurrent run won the race), which is why this was
published by hand; #326
makes the publish workflow reconcile instead of failing there.