create-nextblock 0.17.0 → 0.17.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -89,7 +89,7 @@ persisting.
89
89
  ### Scheduled sales, price changes, and promotions
90
90
 
91
91
  Products and variants carry a scheduled-pricing layer (migration
92
- `00000000000025_add_sale_schedule_columns.sql`):
92
+ `libs/db/src/supabase/migrations/02001_baseline_schema.sql` (originally `00000000000025_add_sale_schedule_columns`, folded in by the generation-2 squash)):
93
93
 
94
94
  - `sale_start_at` / `sale_end_at` — the time window during which `sale_price` /
95
95
  `sale_prices` apply. Both null = always-on (back-compat with static sales).
@@ -47,7 +47,7 @@ The authoritative type list is `apps/nextblock/lib/blocks/blockTypes.ts`
47
47
  A `section` block can contain nested column block arrays, so the page builder
48
48
  supports multi-column compositions instead of only flat block lists. Legacy
49
49
  `hero` blocks were folded into `section` (carrying an `is_hero` flag) by
50
- migration `00000000000021_migrate_hero_blocks_to_sections.sql`, so `hero` is no
50
+ migration `libs/db/src/supabase/migrations/02004_baseline_seed.sql` (originally `00000000000021_migrate_hero_blocks_to_sections`, folded in by the generation-2 squash), so `hero` is no
51
51
  longer a standalone registered block type.
52
52
 
53
53
  ### How the CMS uses the registry