t3-code-android-nightly/.repos/effect-smol/.agents/skills/migration-guidance/annotations.md
Julius Marminge e3c85ead63
chore(refs): sync Effect and Alchemy references to rc.115 and beta.78 (#12327)
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
2026-09-17 23:21:25 -07:00

15 lines
547 B
Markdown

# Migration Annotations
Add or update one YAML file per v3 module under `migration/annotations/`. Use
stable API IDs without trailing `#type` or `#value` facets:
```yaml
effect/Effect#async:
replacement: Effect.callback
note: Use the callback constructor.
example: Effect.callback((resume) => resume(Effect.void))
```
Every annotation requires `replacement` and `note`; `example` is optional. Use
`replacement: none` when there is no direct replacement and explain the
supported migration strategy instead of inventing an equivalent API.