feat(cron_schedule): opt-in time-partitioned-job support (v0.8.2)

ScheduleDefinition errors on every tick against a partitioned asset job
with "no partition key provided". Add an opt-in path that switches to
build_schedule_from_partitioned_job when any time-based partition field
is set, so each tick auto-targets the most-recent finished partition.

  - New fields (mirroring the synthetic_data_generator + sinks shape):
    partition_type, partition_start, partition_values,
    partition_dimensions, dynamic_partition_name.
  - cron_expression becomes Optional in the partitioned path — Dagster
    infers cadence from partitions_def. If supplied, validated against
    the partitions_def cadence (raises ValueError on mismatch instead
    of silently misfiring).
  - partition_type='static' / 'dynamic' raise ValueError in the
    partitioned path — build_schedule_from_partitioned_job is
    time-only.

No change to the un-partitioned path: when neither partition_type nor
partition_dimensions is set, behavior is byte-for-byte identical.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: eric-thomas-dagster

pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "dagster-community-components"
-version = "0.8.1"
+version = "0.8.2"
 description = "Community-maintained Dagster components — ingestion, transforms, IO managers, sensors, sinks, resources, and more."
 readme = "README.md"
 requires-python = ">=3.10"

schedules/cron_schedule/README.md

@@ -11,7 +11,6 @@ Defines a `ScheduleDefinition` + an underlying asset job that materializes the c
 | Field | Type | Description |
 |---|---|---|
 | `schedule_name` | `str` | Unique schedule name shown in the UI. |
-| `cron_expression` | `str` | Cron expression (5 fields: m h dom mon dow). E.g. '0 9 * * *' = daily 09:00. |
 | `asset_keys` | `List[str]` | Slash-separated asset keys to materialize on each tick. |
 
 ### Catalog metadata
@@ -20,6 +19,15 @@ Defines a `ScheduleDefinition` + an underlying asset job that materializes the c
 |---|---|---|---|
 | `tags` | `Dict[str, str]` | — | Tags applied to runs created by this schedule. |
 
+### Partitions
+
+| Field | Type | Default | Description |
+|---|---|---|---|
+| `partition_type` | `str` | — | Partition type: 'daily', 'weekly', 'monthly', 'hourly', 'static', 'multi', 'dynamic', or None for unpartitioned. Note: only time-based types ('daily'/'weekly'/'monthly'/'hourly') work with this schedule's partitioned-job path — 'static' / 'dynamic' raise ValueError. |
+| `partition_start` | `str` | — | Partition start in ISO format (e.g. '2024-01-01' or '2024-01-01-00:00' for hourly). Required for time-based types. |
+| `partition_values` | `str` | — | Comma-separated values for static or multi partitioning. Only used if you also set partition_type='multi' (and even then the schedule rejects pure static — see partition_type). |
+| `partition_dimensions` | `List[Dict[str, Any]]` | — | Multi-axis partition spec: list of {name, type, start, values, dynamic_partition_name} dicts. Overrides flat fields when set. |
+
 ### Sensor configuration
 
 | Field | Type | Default | Description |
@@ -31,7 +39,9 @@ Defines a `ScheduleDefinition` + an underlying asset job that materializes the c
 
 | Field | Type | Default | Description |
 |---|---|---|---|
+| `cron_expression` | `str` | — | Cron expression (5 fields: m h dom mon dow). E.g. '0 9 * * *' = daily 09:00. REQUIRED when no partition fields are set; OPTIONAL in the partitioned-job path (cadence is inferred from the partitions_def). If supplied in the partitioned path, validated against the partitions_def cadence. |
 | `execution_timezone` | `str` | `"UTC"` | IANA timezone for cron evaluation, e.g. 'America/Los_Angeles'. |
+| `dynamic_partition_name` | `str` | — | Name for DynamicPartitionsDefinition (when partition_type='dynamic'). NOTE: the schedule rejects dynamic-only partitions. |
 
 <!-- FIELDS:END -->
 
@@ -47,3 +57,33 @@ attributes:
   tags:
     team: data-platform
 ```
+
+### Partitioned-job mode
+
+When any time-based partition field (`partition_type`,
+`partition_dimensions`) is set, the component switches from
+`ScheduleDefinition` to `build_schedule_from_partitioned_job`. Each
+tick auto-targets the most-recent finished partition — without this
+switch, `ScheduleDefinition` against a partitioned asset job errors
+with "no partition key provided" on every tick.
+
+`cron_expression` is OPTIONAL in this mode (Dagster infers cadence
+from the partitions_def). If you supply one, it's validated against
+the partitions_def cadence — a daily cron paired with hourly
+partitions raises `ValueError` at load time rather than failing
+silently.
+
+```yaml
+type: dagster_component_templates.CronScheduleComponent
+attributes:
+  schedule_name: hourly_orders_pipeline
+  asset_keys: [python_hourly_orders_for_pipe, orders_to_s3]
+  partition_type: hourly
+  partition_start: "2026-05-26-00:00"
+  default_status: RUNNING
+```
+
+`partition_type: static` and `partition_type: dynamic` raise
+`ValueError` in this path — `build_schedule_from_partitioned_job`
+needs a time-based partitions_def. For non-time partitions, use the
+un-partitioned schedule and select keys downstream.