v3.20.0

Deprecations

New additions

• Added a --protocol option (plus matching SNOWFLAKE_PROTOCOL env var and protocol config key) to snow connection add and the global connection overrides. This allows selecting http or https as the connection protocol without editing config.toml, which is primarily useful for local development against http deployments.
• Added snow helpers generate-project-schema command to emit a JSON Schema for the snowflake.yml project definition file. The output follows JSON Schema Draft 2020-12 and can be plugged into supported editors (e.g. VS Code via the YAML extension) or CI pipelines to get completion and to catch structural mistakes (unknown keys, wrong types, missing required fields) before a deploy. The schema is generated from the CLI's own models, so some cross-field and semantic checks are still only applied at load/deploy time. Use --definition-version to select the project definition version (1, 1.1, or 2; defaults to 2) and --output-file/-o to write the schema to a file.

Fixes and improvements

• Fixed TooManyFilesError during snow streamlit deploy when main_file is a descendant of a directory listed in artifacts.
• Upgraded snowflake-connector-python from 4.5.0 to 4.6.0.
• snow dcm list-deployments and snow dcm drop-deployment now wrap the project name in IDENTIFIER(...), matching every other DCM subcommand. Fully-qualified and quoted project names are now handled consistently.
• Fixed snow sql table output rendering as a series of | characters when selecting many columns into a non-terminal destination (e.g. piped or redirected output).
• get_account_identifier() and snow spcs service build-image now raise a clear, user-visible error when CURRENT_ORGANIZATION_NAME() / CURRENT_ACCOUNT_NAME() return no row or a NULL value, instead of a cryptic TypeError: 'NoneType' object is not subscriptable / AttributeError: 'NoneType' object has no attribute 'lower'.
• snow app setup and snow app deploy now verify the current role can deploy to the account-configured destination (the DEFAULT_SNOWFLAKE_APPS_DESTINATION_DATABASE / DEFAULT_SNOWFLAKE_APPS_DESTINATION_SCHEMA account defaults) before using it. When the role is missing the required privileges, the commands fall back to your personal database — as if no account default were set — and print a warning listing the missing grants and pointing you to your account administrator.