We are using the Snowflake offline store/provider which is currently failing on a feast apply because it hardcodes RUNTIME_VERSION = '3.9' (see here). As of April 30 2026, Snowflake has officially decommissioned the Python 3.9 runtime environment. Snowflake's query engine now strictly rejects any SQL statements attempting to register or execute objects using this runtime, resulting in a hard block that cannot be bypassed via Snowflake account configuration:

snowflake.connector.errors.ProgrammingError: 391569 (22023): 01c5be5e-040b-1f4a-0003-890423b60d6b: SQL compilation error: Python runtime version 3.9 is decommissioned. Please update your code to Python runtime version 3.10 or later.

Expected Behavior

feast apply to complete successfully.

Current Behavior

Snowflake returns a compilation error stating that the requested Python runtime version is decommissioned or unsupported, blocking any feast apply.

snowflake.connector.errors.ProgrammingError: 391569 (22023): 01c5be5e-040b-1f4a-0003-890423b60d6b: SQL compilation error: Python runtime version 3.9 is decommissioned. Please update your code to Python runtime version 3.10 or later.

Steps to reproduce

Use Snowflake as offline store.

Example feature view/data source:

driver_stats_source = SnowflakeSource(
    database="DRIVER_DEV",
    schema="FEAST_TEST_RAW",
    table="DRIVER_EXAMPLE",
    name="driver_stats",
    timestamp_field="TIMESTAMP_UTC",
)
driver_stats_fv = FeatureView(
    name="driver_hourly_stats",
    entities=[driver],
    ttl=timedelta(days=1),
    schema=[
        Field(name="CONV_RATE", dtype=Float32),
        Field(name="ACC_RATE", dtype=Float32),
        Field(name="AVG_DAILY_TRIPS", dtype=Int64, description="Average daily trips"),
    ],
    online=True,
    source=driver_stats_source,
    tags={"team": "driver_performance"},
)

Run feast apply.

Specifications

• Version: 0.64.0

Possible Solution

Feast to use a supported Python runtime version (such as 3.12+) when creating server-side objects in Snowflake. Snowflake's Python runtime support roadmap can be seen here. Ideally either default to a newer version (3.12 seems to be supported up to 02 Oct 2028) or be exposed as a configurable property in feature_store.yaml?