release: v0.6.1

Patch release per Eric's live-testing finding: Snowflake least-privilege
roles (e.g. DAGSTER_RUNNER with USAGE on the database) can't read
INFORMATION_SCHEMA views for some new-feature objects even when they
can perform the action on those objects (REFRESH / EXECUTE / ALTER).

This release swaps the materialize-time metadata-read blocks across
the Snowflake surface to use SHOW ... LIKE '<name>' IN SCHEMA <db>.<schema>
instead, with try/except so the action wins even if the metadata read
also fails. Affected components:

  - snowflake_workspace (multi-entity):
      _dynamic_table_asset, _task_asset, _snowpipe_asset, _mv_asset,
      _external_table_asset, _alert_asset, observation sensor's DT block
  - snowflake_dynamic_table_refresh_asset (single-entity, Wave 3)
  - snowflake_task_execute_asset (single-entity, Wave 3)
  - snowflake_task_completion_sensor (single-entity, Wave 3) —
      improved skip_reason error message pointing at MONITOR grant

No new components; no API changes. The demos that worked before
continue to work; the demos that hit "does not exist or not authorized"
on INFORMATION_SCHEMA queries now succeed (or fall back to basic
metadata with a clear log warning).

L1 validation harness scorecard unchanged from v0.6.0:
    PASS:  562  WARN:    0  FAIL:   41

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

Author: eric-thomas-dagster

dagster_community_components/__init__.py

@@ -21,7 +21,7 @@
 import importlib.util
 from pathlib import Path
 
-__version__ = "0.6.0"
+__version__ = "0.6.1"
 
 _PACKAGE_ROOT = Path(__file__).resolve().parent
 

pyproject.toml

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