Upgrading Pulsar
Use the package's ordered upgrade guide for the version you are leaving. Review the diff and run the consuming application's test suite before deployment.
Required order
| Release line | Required work |
|---|---|
| 0.4.1 | Replace each direct Controller-to-Query call with a read-only UseCase that delegates to the Query; refresh a published skill if the application uses one. |
| 0.4.0 | Preserve existing API surfaces; add --web or the documented browser-route wiring only when needed; refresh a published skill after review. |
| 0.3.0 | Rename Operation handle() declarations and call sites, run pulsar install, move concrete Contract implementations to Infrastructure, then optionally adopt the new Event shape. |
Safe installer use
Preview installer changes with pulsar install --dry-run before applying them. Do not use --force as a first response: it replaces the generated provider, so review local customizations first.
FAQ
Is every migration required? No. The 0.3.0 Operation rename is the strict generated-code convention; installer and other migration steps apply when adopting the named conventions. The package guide defines the complete conditions.