YAML values like '1.0' (unquoted) parse as double, not String.
Changed parseStringList to use string interpolation ('$e') instead
of 'e as String', so numeric YAML scalars in labels/milestones
don't crash ticket parsing.
Also quote all '1.0' label values in existing ticket files so they
are unambiguously strings in YAML.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
574 B
574 B
| id | title | type | created | milestones | labels | |||
|---|---|---|---|---|---|---|---|---|
| DEW-0016 | Verify pub.dev name availability for all four packages | spike | 2026-04-25T19:51:54.776993Z |
|
|
Check that all four package names are available on pub.dev before we invest in publishing prep:
- https://pub.dev/packages/dew
- https://pub.dev/packages/dew_core
- https://pub.dev/packages/dew_kanban
- https://pub.dev/packages/dew_mcp
If any name is taken, we need to decide on alternatives (e.g. dew_cli, dew_board, etc.) and update package names + imports throughout the codebase.