SNOWFLAKE DOCS DIFF
本日は全8537ページ中100ページが改訂され、削除はありませんでした。主な動きは Cortex AI のモデルライフサイクルとMCPの通信仕様変更で、既存のクライアントやモデル利用への影響が大きい更新です。加えて、Snowflake App Runtime の一般提供化や app.yml への移行、Feature policiesの記法拡張など、開発者向け機能の仕様整理も進みました。重要度はBの実質更新が58件と最多ですが、S 3件・A 6件の変更は早急な確認が必要です。
tools/call応答がSSEストリームになり、単一JSONを前提とするクライアントは対応が必要です。snow app setupの生成物もsnowflake.ymlからapp.yml manifestへ変更されました。$IS_TEMPORARYなどの短縮記法が追加され、Boolean評価や適用対象外プロパティのエラー挙動が明確化されました。case_sensitive／max_batch_size、Feature StoreのOnline Serviceサイズ指定、Experiment TrackingのMLジョブID記録が追加されました。モデルのライフサイクル（legacy／end-of-life）に関する仕様が追加され、legacy 化後は legacy 日以前の利用実績があるアカウントのみ継続利用でき、end-of-life 後は全アカウントで利用不可となりました。SHOW CORTEX BASE MODELS の lifecycle_status、legacy_date、eol_date で状態を確認でき、llama4-maverick など複数モデルに [legacy] 表示が追加されています。
影響: 利用中の legacy モデルは end-of-life 日までに移行する必要があり、新規利用開始や期限後のクエリ・API 呼び出しは失敗します。
判定根拠: 追加行に「behavior change」
--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/aisql-regional-availability+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/aisql-regional-availability@@ -9,5 +9,6 @@ Snowflake Cortex AI Functions support a range of language and embedding models with varying capabilities, context-window sizes, and regional availability. Use this reference to choose a model for your workload, check its input and output-limits, confirm that it's available in your region, and identify previous model versions that are still supported.+limits, confirm that it's available in your region, understand [legacy and end-of-life access](#label-cortex-model-lifecycle),+and identify previous model versions that are still supported. <a id="label-cortex-llm-choosing"></a>@@ -131,4 +132,39 @@ | TRANSLATE | Snowflake managed model | 100,000 (input only) | 100,000 | +<a id="label-cortex-model-lifecycle"></a>++## Model lifecycle: legacy and end-of-life++Snowflake retires Cortex models in two stages: **legacy**, then **end-of-life**. A model marked+legacy is not yet unavailable to every account. Access depends on whether your **account** already+used that model.++### Legacy++After a model's legacy date:++- If your account used the model anywhere before the legacy date, the account can continue to use+ it in every supported application until the model's end-of-life date. Supported applications+ include AI_COMPLETE, CORTEX.COMPLETE, the Agents API, Cortex Inference, and %sf-intelligence%.+- If your account had not used the model anywhere before the legacy date, the account can't start+ using it. Queries and API calls that name the model fail.++Any usage of the model in the account before the legacy date means that the account can continue+to use the model until end-of-life, including in applications that had not called that model+before.++Snowflake recommends that you migrate to a supported model before the end-of-life date, even if+your account can still call the legacy model.++### End-of-life++After a model's end-of-life date, the model is no longer available to any account, regardless of+prior usage. Queries and API calls that name the model fail.++Use [SHOW CORTEX BASE MODELS](/sql-reference/sql/show-cortex-base-models) to see each model's+`lifecycle_status`, `legacy_date`, and `eol_date`. Deprecation dates for specific models are+announced in unbundled behavior change releases, such as+[Cortex model deprecations for August 2026](/release-notes/bcr-bundles/un-bundled/bcr-august-model-deprecations).+ <a id="label-cortex-llm-availability"></a> @@ -374,5 +410,5 @@ </tr> <tr>- <td>`llama4-maverick`</td>+ <td>`llama4-maverick [legacy]`</td> <td>%cm%</td> <td>%cm%</td>@@ -406,5 +442,5 @@ </tr> <tr>- <td>`llama3.1-70b`</td>+ <td>`llama3.1-70b [legacy]`</td> <td>%cm%</td> <td>%cm%</td>@@ -550,21 +586,21 @@ </tr> <tr>- <td>`openai-gpt-4.1`</td>- <td>%cm%</td>- <td></td>- <td></td>- <td></td>- <td></td>- <td></td>- <td></td>- <td></td>- <td></td>- <td>%cm%</td>- <td></td>- <td></td>- <td></td>- </tr>- <tr>- <td>`mistral-large2`</td>+ <td>`openai-gpt-4.1 [legacy]`</td>+ <td>%cm%</td>+ <td></td>+ <td></td>+ <td></td>+ <td></td>+ <td></td>+ <td></td>+ <td></td>+ <td></td>+ <td>%cm%</td>+ <td></td>+ <td></td>+ <td></td>+ </tr>+ <tr>+ <td>`mistral-large2 [legacy]`</td> <td>%cm%</td> <td>%cm%</td>@@ -598,21 +634,21 @@ </tr> <tr>- <td>`mixtral-8x7b`</td>- <td>%cm%</td>- <td>%cm%</td>- <td>%cm%</td>- <td></td>- <td></td>- <td>%cm%</td>- <td>%cm%</td>- <td>%cm%</td>- <td>%cm%</td>- <td>%cm%</td>- <td></td>- <td>%cm%</td>- <td></td>- </tr>- <tr>- <td>`mistral-7b`</td>+ <td>`mixtral-8x7b [legacy]`</td>+ <td>%cm%</td>+ <td>%cm%</td>+ <td>%cm%</td>+ <td></td>+ <td></td>+ <td>%cm%</td>+ <td>%cm%</td>+ <td>%cm%</td>+ <td>%cm%</td>+ <td>%cm%</td>+ <td></td>+ <td>%cm%</td>+ <td></td>+ </tr>+ <tr>+ <td>`mistral-7b [legacy]`</td> <td>%cm%</td> <td>%cm%</td>@@ -1143,5 +1179,5 @@ </tr> <tr>- <td>`llama4-maverick`</td>+ <td>`llama4-maverick [legacy]`</td> <td>%cm%</td> <td></td>@@ -1167,5 +1203,5 @@ </tr> <tr>- <td>`llama3.1-70b`</td>+ <td>`llama3.1-70b [legacy]`</td> <td>%cm%</td> <td>%cm%</td>@@ -1191,41 +1227,41 @@ </tr> <tr>- <td>`openai-gpt-4.1`</td>- <td></td>- <td></td>- <td></td>- <td>%cm%</td>- <td></td>- <td></td>- <td></td>- <td></td>- <td></td>- </tr>- <tr>- <td>`mistral-large2`</td>- <td>%cm%</td>- <td>%cm%</td>- <td>%cm%</td>- <td>%cm%</td>- <td></td>- <td></td>- <td></td>- <td></td>- <td></td>- </tr>- <tr>- <td>`mixtral-8x7b`</td>- <td>%cm%</td>- <td>%cm%</td>- <td>%cm%</td>- <td>%cm%</td>- <td></td>- <td></td>- <td></td>- <td></td>- <td></td>- </tr>- <tr>- <td>`mistral-7b`</td>+ <td>`openai-gpt-4.1 [legacy]`</td>+ <td></td>+ <td></td>+ <td></td>+ <td>%cm%</td>+ <td></td>+ <td></td>+ <td></td>+ <td></td>+ <td></td>+ </tr>+ <tr>+ <td>`mistral-large2 [legacy]`</td>+ <td>%cm%</td>+ <td>%cm%</td>+ <td>%cm%</td>+ <td>%cm%</td>+ <td></td>+ <td></td>+ <td></td>+ <td></td>+ <td></td>+ </tr>+ <tr>+ <td>`mixtral-8x7b [legacy]`</td>+ <td>%cm%</td>+ <td>%cm%</td>+ <td>%cm%</td>+ <td>%cm%</td>+ <td></td>+ <td></td>+ <td></td>+ <td></td>+ <td></td>+ </tr>+ <tr>+ <td>`mistral-7b [legacy]`</td> <td>%cm%</td> <td>%cm%</td>@@ -1574,12 +1610,12 @@ | AI_COMPLETE | | | | | \| `claude-4-sonnet [legacy]` | | | |-| \| `llama4-maverick` | | | |+| \| `llama4-maverick [legacy]` | | | | | \| `llama3.1-8b` | %cm% | %cm% | %cm% |-| \| `llama3.1-70b` | %cm% | %cm% | %cm% |+| \| `llama3.1-70b [legacy]` | %cm% | %cm% | %cm% | | \| `llama3.3-70b` | | | |-| \| `openai-gpt-4.1` | | | |-| \| `mistral-large2` | %cm% | %cm% | %cm% |-| \| `mixtral-8x7b` | %cm% | %cm% | %cm% |-| \| `mistral-7b` | %cm% | %cm% ... (truncated)
差分が長いため、途中まで表示しています。
Version 1.54.0（2026-08-31）で、Registry の log_model に全メソッドへ適用する case_sensitive／max_batch_size オプション、Feature Store の create_online_service(size=...)、Experiment Tracking の ML ジョブ ID 記録が追加されました。Feature View の未知メタデータキー処理や、Registry の quoted owner role、既存 Feature View のオンラインストレージ有効化に関する不具合も修正されています。
影響: Feature Store の Online Service サイズを指定・確認できるようになり、既存コードでは Registry オプションの適用範囲と Feature View 更新動作に関する修正の影響を確認してください。
判定根拠: 追加行に「behavior change」
--- ahttps://docs.snowflake.com/en/release-notes/clients-drivers/snowpark-ml-2026+++ bhttps://docs.snowflake.com/en/release-notes/clients-drivers/snowpark-ml-2026@@ -44,4 +44,35 @@ Use the `imports` argument instead. - The `snowflake.ml.model.models.huggingface_pipeline.HuggingfacePipelineModel` class has been deprecated and will be removed in a future release.++## Version 1.54.0 (2026-08-31)++### New Features++- Registry: `log_model(..., options={"case_sensitive": True})` and+ `options={"max_batch_size": N}` apply those settings to all methods. Per-method+ `method_options` still override the global values.+- Feature Store: `create_online_service` accepts a `size` kwarg naming the size to+ provision the Online Service at, one of `"XS"`, `"S"`, `"M"`, `"L"`, `"XL"`,+ `"2XL"`, `"3XL"` (case-insensitive). When omitted, the server-side default applies;+ accounts that cap the available size provision at their cap.+ `get_online_service_status()` now reports the provisioned `size`, which is `None`+ for services created before sizes were recorded.+- Experiment Tracking: Source provenance now also records the id of the enclosing ML+ job when a run is created from inside one.++### Bug Fixes++- Feature Store: Feature View metadata tags carrying unknown keys (including a legacy+ `refresh_mode`) no longer fail to deserialize; unknown keys are ignored on read and+ the tag still does not persist `refresh_mode`.+- Registry: Fixed `ModelVersion.load()` failing with `ValueError: ... is not a valid+ SQL identifier` when the model's owner role is a quoted identifier.+- Feature Store: Fixed `FeatureStore.update_feature_view()` failing with `SQL compilation+ error: invalid value 'ADAPTIVE' for property 'REFRESH_MODE'` when enabling online+ storage for an existing feature view.++### Behavior Changes++### Deprecations ## Version 1.53.0 (2026-08-24)
2026年8月20日に、Snowflake の managed MCP server が tools/call の応答を単一の JSON payload ではなく Server-Sent Events（SSE）ストリームで返す変更がリリース済みとなりました。これは 無効化できない behavior change で、単一 JSON として解析するクライアントは SSE 対応と Accept ヘッダーへの text/event-stream 追加が必要です。
影響: 公式仕様準拠の MCP クライアントは原則対応不要ですが、単一 JSON 応答を前提とするクライアントは tools/call の SSE ストリームを消費するよう更新が必要です。
判定根拠: 追加行に「behavior change」
--- ahttps://docs.snowflake.com/en/release-notes/bcr-bundles/un-bundled/bcr-2405+++ bhttps://docs.snowflake.com/en/release-notes/bcr-bundles/un-bundled/bcr-2405@@ -1,7 +1,7 @@-# MCP: Streaming responses for tool calls (August 2026) (Pending)+# MCP: Streaming responses for tool calls (August 2026) -Starting August 20, 2026, Snowflake's managed MCP server returns tool call responses as Server-Sent Events (SSE) streams instead of single JSON payloads. This aligns Snowflake's MCP implementation with the MCP specification (2025-11-25), which requires clients to support SSE as a transport. MCP clients that follow the official specification are already compliant and require no changes. Clients that parse the `tools/call` response as a single JSON body must be updated to consume an SSE stream.+As of August 20, 2026, Snowflake's managed MCP server returns tool call responses as Server-Sent Events (SSE) streams instead of single JSON payloads. This aligns Snowflake's MCP implementation with the MCP specification (2025-11-25), which requires clients to support SSE as a transport. MCP clients that follow the official specification are already compliant and require no changes. Clients that parse the `tools/call` response as a single JSON body must be updated to consume an SSE stream. -All information in this notice, including the planned date, is subject to change.+This behavior change was released on August 20, 2026. It isn't part of a behavior change bundle, so it can't be disabled. ## Behavior change@@ -54,5 +54,5 @@ ## What you should do -If your MCP client parses the `tools/call` response as a single JSON body, update it before August 20, 2026:+If your MCP client parses the `tools/call` response as a single JSON body, update it as follows: 1. **Update the Accept header.** Add `text/event-stream` to the `Accept` header on all requests to the Snowflake MCP endpoint:
ページタイトルが 「Optional app.yml manifest」から「app.yml manifest」へ変更され、App Runtime 関連ページへのナビゲーションリンクが追加されました。一方、app.yml のトップレベル構造、install・build・run・artifacts などのキー説明および YAML コード例を含む詳細リファレンスが削除されています。
影響: app.yml の具体的な構文やパラメータをこのページ内で確認できなくなり、移転先は diff からは詳細不明です。
判定根拠: SQL 構文/コードブロックの増減 (+0/-20)
--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-app-runtime/app-yml+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-app-runtime/app-yml@@ -1,8 +1,15 @@-# Optional app.yml manifest for Snowflake App Runtime--Available to all accounts.+<a id="label-snowflake-apps-app-yml"></a>++# app.yml manifest for Snowflake App Runtime - [](/developer-guide/snowflake-app-runtime/getting-started)+- [](/developer-guide/snowflake-app-runtime/runtime-environment)+- [](/developer-guide/snowflake-app-runtime/query-snowflake)+- [](/developer-guide/snowflake-app-runtime/migrate-to-app-yml)+- [](/developer-guide/snowflake-app-runtime/deploy-targets) - [](/developer-guide/snowflake-app-runtime/deploy)+- [](/developer-guide/snowflake-app-runtime/scale-and-suspend)+- [](/developer-guide/snowflake-app-runtime/secure-development)+- [](/developer-guide/snowflake-app-runtime/security) - [](/user-guide/cortex-code/cortex-code-cli) - [](/user-guide/cortex-code/cortex-code-desktop/building-apps)@@ -10,376 +17,40 @@ - [](/sql-reference/commands-snowflake-apps) -The optional **`app.yml`** manifest tells Snowflake **how to install, build,-run, and package** your application, along with optional display metadata-(`profile`) and runtime configuration such as environment variables, secrets,-and external access integrations.--When you don't provide it, Snowflake **auto-detects** build and run behavior-from your project layout (for example, `package.json` for Node.js). Hand-edit-`app.yml` when you need to customize those install, build, run, or packaging-steps, or to set the app's display profile, environment variables, secrets,-or external access integrations. Name the file **`app.yml`** and place it in-your application source.--Cortex Code CLI and Cortex Code Desktop generate this file automatically when-scaffolding Snowflake App Runtime projects.--For deploy configuration, the Snowflake CLI uses a separate **`snowflake.yml`**-project file that `snow app setup` creates and `snow app deploy` reads. See-[](/developer-guide/snowflake-app-runtime/getting-started) and-[](/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/setup).--<a id="label-snowflake-apps-app-yml"></a>--## `app.yml` reference--<a id="label-snowflake-apps-manifest-top-level-structure"></a>--### Top-level structure--```yaml-install:- commands:- - [<command>, <arg>, ...]-build:- commands:- - [<command>, <arg>, ...]-run:- command: [<command>, <arg>, ...]-artifacts:- - src: <glob_pattern>- dest: <destination_path>-profile:- icon: <relative_path_to_icon>- label: <display_label>- description: <description_text>-environment_variables:- - name: <var_name>- value: <var_value>-secrets:- - name: <mount_name>- secret: <fully_qualified_secret_name>-external_access_integrations:- - <integration_name>-min_instances: <num>-max_instances: <num>-```--All top-level keys are optional. Snowflake ignores unknown keys.--<a id="label-snowflake-apps-manifest-keys"></a>--<a id="label-snowflake-apps-manifest-install"></a>--### Keys--#### install--Commands Snowflake runs during the install phase, before the build. Each-entry under `commands` is an argv-style list, passed directly without a-shell. Use `install` for setup steps such as installing dependencies.--```yaml-install:- commands:- - [npm, ci]-```--<a id="label-snowflake-apps-manifest-build"></a>--#### build--Commands Snowflake runs during the build phase. Each entry under `commands`-is an argv-style list.--```yaml-build:- commands:- - [npm, run, build]-```--<a id="label-snowflake-apps-manifest-run"></a>--#### run--The entry-point command that starts the application container. `command`-is an argv-style list.--```yaml-run:- command: [node, server.js]-```--<a id="label-snowflake-apps-manifest-artifacts"></a>--#### artifacts--Copy rules that move files produced by the build into the final package. Each-entry has these fields:--- `src`: Glob pattern, relative to the build working directory, that- matches the files to copy. The pattern supports `**` for recursive- matching (provided by the- [doublestar](https://github.com/bmatcuk/doublestar) library). For example,- `dist/**` matches every file under `dist` at any depth.-- `dest`: Destination path within the package. Set `dest` to `.` to- flatten matched files into the package root by basename. Set `dest` to- any other path to preserve the directory structure of the matched files- relative to the glob base, rooted at `dest`.--Only files that match the glob are copied; directories themselves aren't-copied. To include a directory tree, use `**`.--```yaml-artifacts:- - src: "dist/**"- dest: "."- - src: "package.json"- dest: "."-```--<a id="label-snowflake-apps-manifest-profile"></a>--#### profile--Presentation metadata surfaced alongside the deployed service.--- `icon`: Relative path to a `.png`, `.svg`, or `.webp` file inside the package.- The path must not contain `..`, and it can't be an absolute path.-- `label`: Short display label.-- `description`: Longer human-readable description.--The `label` and `description` values appear in the-`additional_properties` column of SHOW APPLICATION SERVICES.--```yaml-profile:- icon: assets/logo.png- label: Customer Portal- description: Web UI for the customer-facing portal.-```--<a id="label-snowflake-apps-manifest-environment-variables"></a>--#### environment_variables--Non-sensitive configuration values that Snowflake exposes as environment-variables inside the application container. Each entry has:--- `name`: Environment variable name. Must match the POSIX pattern- `[A-Z_][A-Z0-9_]*` (uppercase letters, digits, and underscores; must start- with a letter or underscore). Duplicate names aren't allowed.-- `value`: String value.--Some environment variable names are reserved for the platform and can't be set-here: any name starting with `SF_SNOWFS_`, plus `SNOWFLAKE_AUTH_MODE`,-`SNOWFLAKE_INSECURE_MODE`, `NODE_ENV`, `NEXT_PRIVATE_STANDALONE`, `PORT`, and-`HOSTNAME`. Setting a reserved name fails validation or is dropped at deploy.--```yaml-environment_variables:- - name: LOG_LEVEL- value: "INFO"- - name: APP_REGION- value: "us-west-2"-```--Read them like any other environment variable in your application code:--```javascript-const logLevel = process.env.LOG_LEVEL ?? "INFO";-```--```python-log_level = os.getenv("LOG_LEVEL", "INFO")-```--Beyond the names you set here, Snowflake provides built-in environment variables-(such as `SNOWFLAKE_DATABASE`, `SNOWFLAKE_SCHEMA`, and `SNOWFLAKE_SERVICE_NAME`)-that identify the Application Service at runtime. Snowflake sets those only when-you don't define them yourself, so a name you set here always wins. See-[Built-in environment variables](/developer-guide/snowflake-app-runtime/getting-started#label-getting-started-builtin-env-vars).--<a id="label-snowflake-apps-manifest-secrets"></a>--#### secrets--Snowflake [secret](/sql-reference/sql/create-secret) objects to make available-to the application at runtime. Each entry has:--- `name`: Mount name used to locate the secret files inside the container. Must- match the POSIX pattern `[A-Z_][A-Z0-9_]*`. Duplicate names aren't allowed.-- `secret`: Fully qualified name of an existing Snowflake secret- (`<database>.<schema>.<secret_name>`).--```yaml-secrets:- - name: API_KEY- secret: db.schema.api_key_secret-```--Snowflake mounts each secret as one or more files under `/secrets/<name>/`.-The application reads secret values from these files. File-based delivery-lets Snowflake rotate a secret while the container runs; the file content-updates in place.--The files written depend on the secret type:--<div className="colwidths-given">-- <colgroup>- <col style={{ width: "30.0%" }} ... (truncated)
差分が長いため、途中まで表示しています。
Snowflake App Runtime のプレビュー表記が削除され、AWS・Azure・Google Cloudの商用リージョンで利用可能（政府リージョン・trial accountsは対象外）と明記されました。また、snow app setup の生成物が snowflake.yml から app.yml manifest に変更され、水平スケーリングの詳細（MIN_INSTANCES／MAX_INSTANCES の設定例）は専用ページへの案内に置き換えられました。
影響: 新規・既存プロジェクトでは app.yml への移行を確認し、スケーリング設定は専用ドキュメントを参照する必要があります。
判定根拠: SQL 構文/コードブロックの増減 (+0/-5)
--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-app-runtime/about-snowflake-app-runtime+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-app-runtime/about-snowflake-app-runtime@@ -1,7 +1,6 @@ # Snowflake App Runtime -In preview in Amazon Web Services (AWS), Microsoft Azure, and Google Cloud commercial regions.- - [](/developer-guide/snowflake-app-runtime/getting-started)+- [](/developer-guide/snowflake-app-runtime/query-snowflake) - [](/developer-guide/snowflake-app-runtime/deploy) - [](/developer-guide/snowflake-cli/installation/installation)@@ -10,4 +9,7 @@ - [](/user-guide/cortex-code/cortex-code-desktop) - [](/developer-guide/snowflake-app-runtime/app-yml)+- [](/developer-guide/snowflake-app-runtime/migrate-to-app-yml)+- [](/developer-guide/snowflake-app-runtime/deploy-targets)+- [](/developer-guide/snowflake-app-runtime/scale-and-suspend) - [](/sql-reference/commands-snowflake-apps) @@ -22,6 +24,9 @@ deploys to a live URL. -During public preview, App Runtime builds **Node.js** apps (with a focus on-**Next.js**). **Python** support is **planned**.+Snowflake App Runtime builds **Node.js** apps (with a focus on **Next.js**).+**Python** support is **planned**. It's available in Amazon Web Services+(AWS), Microsoft Azure, and Google Cloud commercial regions. It isn't+available in government regions or on+[trial accounts](/user-guide/admin-trial-account). <a id="label-snowflake-app-runtime-about-why-build"></a>@@ -96,5 +101,6 @@ ``` -`snow app setup` generates a `snowflake.yml` project definition. `snow app deploy`+`snow app setup` generates an [`app.yml`](/developer-guide/snowflake-app-runtime/app-yml)+manifest. `snow app deploy` runs the upload, build, and deploy phases and returns a live Application Service URL. See@@ -123,114 +129,21 @@ <a id="label-snowflake-app-runtime-about-horizontal-scaling"></a> -## Horizontal scaling--By default, an Application Service runs as a single instance. Set-`MIN_INSTANCES` and `MAX_INSTANCES` if you want Snowflake to add and remove-instances based on CPU use. For how that scaling works, see-[](/developer-guide/snowpark-container-services/scaling-services#label-spcs-working-with-services-enabling-autoscaling).--In `app.yml`:--```yaml-min_instances: 2-max_instances: 5-```--Or change them on a running service with SQL:--```sql-ALTER APPLICATION SERVICE my_db.my_schema.my_app- SET MIN_INSTANCES = 2 MAX_INSTANCES = 5;-```--Running more instances doesn't necessarily increase credit usage; a new node-is provisioned only when existing nodes are full. See [](/developer-guide/snowflake-app-runtime/cost).--For more information, see-[CREATE APPLICATION SERVICE](/sql-reference/sql/create-application-service) and-[ALTER APPLICATION SERVICE](/sql-reference/sql/alter-application-service).+For more about scaling apps and suspending them, see+[](/developer-guide/snowflake-app-runtime/scale-and-suspend). <a id="label-snowflake-app-runtime-about-related-content"></a> -## Related content+## Where to go next -The table below lists this doc set in sidebar order. For installs and your first-deploy, start with-[Getting started with Snowflake App Runtime](/developer-guide/snowflake-app-runtime/getting-started).+- Install the tools and deploy your first app:+ [](/developer-guide/snowflake-app-runtime/getting-started).+- Set shared deploy defaults and role grants for a team (account+ administrators): [](/developer-guide/snowflake-app-runtime/account-admin-setup).+- Configure the deploy in `app.yml`:+ [](/developer-guide/snowflake-app-runtime/app-yml).+- Query your data from the running app:+ [](/developer-guide/snowflake-app-runtime/query-snowflake).+- Check current limits:+ [](/developer-guide/snowflake-app-runtime/limitations). -<div className="colwidths-given">-- <colgroup>- <col style={{ width: "40.0%" }} />- <col style={{ width: "60.0%" }} />- </colgroup>- <thead>- <tr>- <th>Guide</th>- <th>Description</th>- </tr>- </thead>- <tbody>- <tr>- <td>[](/developer-guide/snowflake-app-runtime/getting-started)</td>- <td>- Install tools, build with Cortex Code or the CLI, and deploy your first- app.- </td>- </tr>- <tr>- <td>[](/developer-guide/snowflake-app-runtime/deploy)</td>- <td>- Upload, build, and deploy phases of <code>snow app deploy</code>.- </td>- </tr>- <tr>- <td>[](/developer-guide/snowflake-app-runtime/account-admin-setup)</td>- <td>- Shared deploy defaults and role grants in Snowsight (account- administrators).- </td>- </tr>- <tr>- <td>[](/developer-guide/snowflake-app-runtime/observability)</td>- <td>App status and container logs.</td>- </tr>- <tr>- <td>[](/developer-guide/snowflake-app-runtime/cost)</td>- <td>Cost and credit usage for Snowflake App Runtime.</td>- </tr>- <tr>- <td>[](/developer-guide/snowflake-app-runtime/app-yml)</td>- <td>- Optional <code>app.yml</code> build manifest.- </td>- </tr>- <tr>- <td>[](/developer-guide/snowflake-app-runtime/access-control)</td>- <td>Share apps and delegate operations.</td>- </tr>- <tr>- <td>[](/developer-guide/snowflake-app-runtime/privileges)</td>- <td>Grants for deploy and day-to-day operations.</td>- </tr>- <tr>- <td>[](/developer-guide/snowflake-app-runtime/limitations)</td>- <td>Public preview limitations.</td>- </tr>- <tr>- <td>- [](/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/overview)- </td>- <td>- <code>snow app</code> command reference (Snowflake CLI section).- </td>- </tr>- <tr>- <td>[](/sql-reference/commands-snowflake-apps)</td>- <td>- Application Service SQL and log functions (SQL command reference).- </td>- </tr>- </tbody>--</div>+The sidebar lists the rest of the doc set, grouped by task.
$ 変数短縮記法（例: $IS_TEMPORARY、$IS_TRANSIENT、$WAREHOUSE）が追加され、Boolean プロパティは文字列ではなく Boolean として評価されることが明記されました。従来の SYS_CONTEXT 形式についても、Boolean 比較には = 'TRUE' が必要で、対象ドメインに適用できないプロパティは実行時に NULL を返す一方、短縮記法ではポリシー作成・変更時にコンパイルエラーになるという挙動の違いが追記されました。
影響: 既存の SYS_CONTEXT 構文は引き続き利用できますが、$ 短縮記法へ移行する場合は Boolean の比較方法と、対象 object_type に適用可能なプロパティかどうかを確認する必要があります。
判定根拠: SQL 構文/コードブロックの増減 (+3/-0)
--- ahttps://docs.snowflake.com/en/user-guide/feature-policies+++ bhttps://docs.snowflake.com/en/user-guide/feature-policies@@ -424,27 +424,27 @@ #### Available context -Refer to attributes of the object being created with-`SYS_CONTEXT('SNOWFLAKE$REQUEST', 'GET_OBJECT_PROPERTY', '<property>')`. The-function returns a string, so compare against `'TRUE'` or `'FALSE'` for Boolean-properties.+Access attributes of the object being created using either the `$` variable shorthand or the `SYS_CONTEXT` function:++- **`$`**: a shorthand that resolves the property directly. Boolean properties (`$IS_TEMPORARY`, `$IS_TRANSIENT`) evaluate to an actual boolean, so write `"$IS_TRANSIENT"` rather than `"... = 'TRUE'"`. Using a name that isn't a recognized property, or a property inapplicable to the rule's `object_type`, causes a compilation error when the policy is created or altered.+- **`SYS_CONTEXT('SNOWFLAKE$REQUEST', 'GET_OBJECT_PROPERTY', '<property>')`**: the full form. Always returns a string, so Boolean comparisons require `= 'TRUE'`. A property inapplicable to the domain returns `NULL` at runtime rather than an error at create time. <div className="colwidths-auto"> -| Property | Type | Returns |-| ----------------- | ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |-| `IS_TEMPORARY` | Boolean | `'TRUE'` for `CREATE TEMPORARY ...` of `TABLE`, `VIEW`, `STAGE`, `FILE_FORMAT`, `FUNCTION`, `PROCEDURE`, `SECRET`, `AGENT`; `'FALSE'` otherwise. |-| `IS_TRANSIENT` | Boolean | `'TRUE'` for `CREATE TRANSIENT ...` of `TABLE`, `ICEBERG_TABLE`, `DYNAMIC_TABLE`, `MATERIALIZED_VIEW`, `SCHEMA`, `DATABASE`, `APPLICATION_PACKAGE`; `'FALSE'` otherwise. |-| `WAREHOUSE` | String | For `TASK`: the warehouse named in the request, or `NULL` if none (serverless task). `NULL` for other object types. |-| `EXTERNAL_VOLUME` | String | For `ICEBERG_TABLE`: the external volume resolved for the request (table, schema, database, or account level), or `NULL` if none. `NULL` for other object types. |-| `DATABASE` | String | The name of the database containing the object being created. `NULL` for account-level object types. |-| `SCHEMA` | String | The name of the schema containing the object being created. `NULL` for account-level and database-level object types (those not contained in a schema, including `SCHEMA` itself). |+| Property | $ shorthand | Type | Returns |+| ----------------- | ------------------ | ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |+| `IS_TEMPORARY` | `$IS_TEMPORARY` | Boolean | `'TRUE'` for `CREATE TEMPORARY ...` of `TABLE`, `VIEW`, `STAGE`, `FILE_FORMAT`, `FUNCTION`, `PROCEDURE`, `SECRET`, `AGENT`; `'FALSE'` otherwise. |+| `IS_TRANSIENT` | `$IS_TRANSIENT` | Boolean | `'TRUE'` for `CREATE TRANSIENT ...` of `TABLE`, `ICEBERG_TABLE`, `DYNAMIC_TABLE`, `MATERIALIZED_VIEW`, `SCHEMA`, `DATABASE`, `APPLICATION_PACKAGE`; `'FALSE'` otherwise. |+| `WAREHOUSE` | `$WAREHOUSE` | String | For `TASK`: the warehouse named in the request, or `NULL` if none (serverless task). `NULL` for other object types. |+| `EXTERNAL_VOLUME` | `$EXTERNAL_VOLUME` | String | For `ICEBERG_TABLE`: the external volume resolved for the request (table, schema, database, or account level), or `NULL` if none. `NULL` for other object types. |+| `DATABASE` | `$DATABASE` | String | The name of the database containing the object being created. `NULL` for account-level object types. |+| `SCHEMA` | `$SCHEMA` | String | The name of the schema containing the object being created. `NULL` for account-level and database-level object types (those not contained in a schema, including `SCHEMA` itself). | </div> -Boolean properties always return `'TRUE'` or `'FALSE'` for every object type,-so a single `IS_TEMPORARY` or `IS_TRANSIENT` rule applied across mixed object-types behaves predictably: the property is `'FALSE'` for object types that-can't be temporary or transient (for example, `IS_TRANSIENT` is `'FALSE'` for-`STAGE`).+Boolean properties (`$IS_TEMPORARY`, `$IS_TRANSIENT`) always evaluate to `TRUE` or+`FALSE` for every object type, so a single rule applied across mixed object types+behaves predictably: the property is `FALSE` for types that don't support that+creation option (for example, `$IS_TRANSIENT` is `FALSE` for `STAGE`). When accessed+with `SYS_CONTEXT`, the same properties return the strings `'TRUE'` or `'FALSE'`. String properties return `NULL` when the rule's `object_type` doesn't carry@@ -453,5 +453,6 @@ [NULL handling](#label-feature-policy-rules-null-handling)). Guard string-property comparisons so they evaluate to `TRUE` or `FALSE` for every `object_type` the-rule covers.+rule covers. With the `$` shorthand, a string property that doesn't apply to the+rule's `object_type` is instead rejected as a compilation error at create time. #### Validation rules@@ -467,4 +468,7 @@ - Expressions that name an unsupported `object_type` or call a function that doesn't exist.+- Expressions that use `$` where `` is not a recognized property, or+ where the property doesn't apply to the rule's `object_type` (for example,+ `$WAREHOUSE` in a `TABLE` rule). <a id="label-feature-policy-rules-null-handling"></a>@@ -488,5 +492,14 @@ ```sql+-- Using the $ variable shorthand: CREATE FEATURE POLICY block_temp_tables+ AS $$+ blocked_creation_rules:+ - object_type: TABLE+ block_when: "$IS_TEMPORARY"+ $$;++-- Equivalent using SYS_CONTEXT:+CREATE FEATURE POLICY block_temp_tables_sys_context AS $$ blocked_creation_rules:@@ -503,5 +516,14 @@ ```sql+-- Using the $ variable shorthand: CREATE FEATURE POLICY block_transient_tables+ AS $$+ blocked_creation_rules:+ - object_type: TABLE+ block_when: "$IS_TRANSIENT"+ $$;++-- Equivalent using SYS_CONTEXT:+CREATE FEATURE POLICY block_transient_tables_sys_context AS $$ blocked_creation_rules:@@ -515,5 +537,14 @@ ```sql+-- Using the $ variable shorthand: CREATE FEATURE POLICY require_permanent_tables+ AS $$+ blocked_creation_rules:+ - object_type: TABLE+ block_when: "$IS_TEMPORARY OR $IS_TRANSIENT"+ $$;++-- Equivalent using SYS_CONTEXT:+CREATE FEATURE POLICY require_permanent_tables_sys_context AS $$ blocked_creation_rules:@@ -527,5 +558,5 @@ A single named condition can be reused across object types, including object types that don't support `TRANSIENT` (such as `STAGE`, `VIEW`, `FUNCTION`,-`PROCEDURE`). For those types, `IS_TRANSIENT` is `'FALSE'`, so the rule fires+`PROCEDURE`). For those types, `$IS_TRANSIENT` is `FALSE`, so the rule fires only on temporary creations: @@ -535,7 +566,7 @@ conditions: - name: is_transient- expression: "SYS_CONTEXT('SNOWFLAKE$REQUEST', 'GET_OBJECT_PROPERTY', 'IS_TRANSIENT') = 'TRUE'"+ expression: "$IS_TRANSIE... (truncated)
差分が長いため、途中まで表示しています。
2026年8月12日から対象モデルはlegacy状態となり、同日以前にアカウント内で使用実績がある場合のみ、AI_COMPLETE、CORTEX.COMPLETE、Agents API、Cortex Inference、%sf-intelligence% などでEOLまで継続利用できます。未使用アカウントでは新規利用ができず、Managed functions（AI_CLASSIFY、AI_FILTER、AI_AGGなど）は影響を受けません。 影響: 対象モデルの利用実績がないアカウントではクエリやAPI呼び出しが失敗し、EOL後はlegacy期間中に許可されたアカウントを含む全アカウントで失敗するため、EOL前に置換モデルへ移行する必要があります。
判定根拠: 追加行に「deprecated」
--- ahttps://docs.snowflake.com/en/release-notes/bcr-bundles/un-bundled/bcr-august-model-deprecations+++ bhttps://docs.snowflake.com/en/release-notes/bcr-bundles/un-bundled/bcr-august-model-deprecations@@ -1,8 +1,21 @@ # Cortex model deprecations for August 2026 -The following models enter the legacy state on August 12, 2026. Customers using these models in-AI_COMPLETE, CORTEX.COMPLETE, the Agents API, Cortex Inference, or %sf-intelligence% can continue-to use them until each model's end-of-life (EOL) date, but are expected to transition to a-replacement model in advance to avoid disruption.+The following models enter the **legacy** state on August 12, 2026. Legacy is not the same as+end-of-life. After the legacy date, Snowflake limits which accounts can call the model:++- If your **account** used the model anywhere before August 12, 2026, the account can continue to+ use it in every supported application (including AI_COMPLETE, CORTEX.COMPLETE, the Agents API,+ Cortex Inference, and %sf-intelligence%) until that model's end-of-life (EOL) date.+- If your account had not used the model anywhere before August 12, 2026, the account can't start+ using it. Queries and API calls that name the model fail.++Any usage of the model in the account before the legacy date means that the account can continue+to use it until EOL.++Transition to a replacement model before the EOL date to avoid disruption. For the full+definitions of legacy and end-of-life, see+[Model lifecycle: legacy and end-of-life](/user-guide/snowflake-cortex/aisql-regional-availability#label-cortex-model-lifecycle).++[Managed functions](/user-guide/snowflake-cortex/aisql#cortex-ai-functions) are not impacted by these model deprecations. Snowflake manages and optimizes inference of the underlying models used by functions such as AI_CLASSIFY, AI_FILTER, and AI_AGG. <div className="colwidths-given">@@ -106,5 +119,6 @@ If the named model parameter is not updated, queries or API calls that reference the model fail-after its end-of-life date.+after its end-of-life date for every account, including accounts that were allowed to use the+model during the legacy period. Ref: 2388
2026年8月20日以降、tools/call の応答が単一のJSON本文から Server-Sent Events (SSE) ストリームに変更され、クライアントは Accept: application/json, text/event-stream の両方を指定する必要があります。ストリームは data: [DONE] で終了し、従来の「非ストリーミング応答のみ対応」という記述が削除されました。
影響: クライアント実装では SSE対応と Accept ヘッダーの更新が必要ですが、MCP仕様（2025-11-25）準拠クライアントは自動処理できます。
判定根拠: SQL 構文/コードブロックの増減 (+2/-0)
--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-mcp+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-mcp@@ -969,4 +969,17 @@ To discover or invoke tools, issue a POST call as shown in the [tools/list request](https://modelcontextprotocol.io/specification/2025-11-25/server/tools#calling-tools): +As of August 20, 2026, the server returns `tools/call` responses as a+[Server-Sent Events (SSE)](https://modelcontextprotocol.io/specification/2025-11-25/basic/transports)+stream rather than a single JSON body. Your client must list both content types in the `Accept` header:++```text+Accept: application/json, text/event-stream+```++The response examples in this section show the JSON payload that the server sends in each `data:` event.+The stream closes with a `data: [DONE]` event. Clients that follow the MCP specification (2025-11-25)+handle this automatically. For details, see+[](/release-notes/bcr-bundles/un-bundled/bcr-2405).+ For the Analyst tool, your client passes messages in the request. The SQL statement is listed in the output. You must pass the name of the tool that you're invoking in the request in the `name` parameter. @@ -1045,6 +1058,4 @@ Snowflake-managed MCP server does not support the following constructs in the MCP protocol: resources, prompts, roots, notifications, version negotiations, life cycle phases, and sampling. -Only non-streaming responses are supported.- Each MCP server supports a maximum of 50 tools. This limit includes all tool types: Cortex Search, Cortex Analyst, Cortex Agents, SQL execution, and custom (generic) tools. If you need more tools, create additional MCP servers. Higher tool counts can degrade tool-selection accuracy.
モデルの利用可能性に関する説明が追加され、legacy date 後は、すでにそのモデルを使用していたアカウントのみが end-of-life まで呼び出しを継続できることが明記されました。未使用のアカウントは、legacy date 後にそのモデルの利用を開始できません。 影響: legacy date 前に利用実績がないアカウントは新規利用できないため、対象モデルを使う予定のアカウントは事前に利用を開始しておく必要があります。
判定根拠: SQL 構文/コードブロックの増減 (+1/-0)
--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-rest-api+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-rest-api@@ -310,5 +310,7 @@ ## Model availability -The following tables show the models available in the Cortex REST API for each region:+The following tables show the models available in the Cortex REST API for each region.+After a model's legacy date, only accounts that already used the model can continue to+call it until end-of-life; accounts that had not used it can't start. **Cross-region and Cross-cloud:**
app.yml マニフェストを中心とした構成に整理され、snowflake.yml の生成・参照に関する説明が削除されました。また、CLI の確認手順が snow --version／snow app setup --help から snow helpers check-version に変更され、関連する App Runtime のページ（runtime-environment、deploy-targets、query-snowflake など）が追加されました。デプロイ後は「新しいパッケージバージョン」が作成され、実行中サービスを更新するという表現にも変更されています。
影響: 既存手順を利用する場合は、snowflake.yml 前提の初期化手順から app.yml へ移行し、CLI のバージョン確認方法も更新する必要があります。
変更内容: 本文を更新（78行追加・295行削除）
--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-app-runtime/getting-started+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-app-runtime/getting-started@@ -1,5 +1,3 @@ # Getting started with Snowflake App Runtime--Available to all accounts. - [](/developer-guide/snowflake-app-runtime/about-snowflake-app-runtime)@@ -8,12 +6,15 @@ - [](/user-guide/cortex-code/cortex-code-cli) - [](/user-guide/cortex-code/cortex-code-desktop/building-apps)+- [](/developer-guide/snowflake-app-runtime/app-yml)+- [](/developer-guide/snowflake-app-runtime/migrate-to-app-yml)+- [](/developer-guide/snowflake-app-runtime/query-snowflake)+- [](/developer-guide/snowflake-app-runtime/runtime-environment)+- [](/developer-guide/snowflake-app-runtime/deploy-targets) - [](/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/overview) -This guide walks you through setting up your environment and deploying your-first app on Snowflake. Start with the setup section below, then choose your-path: use [Cortex Code CLI](/user-guide/cortex-code/cortex-code-cli) or+Install [Cortex Code CLI](/user-guide/cortex-code/cortex-code-cli) or [Cortex Code Desktop](/user-guide/cortex-code/cortex-code-desktop/building-apps)-to build from a description, or use the Snowflake CLI directly if you already-have code.+and the Snowflake CLI, then deploy your first app. Use Cortex Code to build+from a description, or the Snowflake CLI if you already have code. <a id="label-getting-started-setup"></a>@@ -52,14 +53,14 @@ Install the Snowflake CLI using [](/developer-guide/snowflake-cli/installation/installation). -Use the latest version of the Snowflake CLI. After install, verify that Snowflake-Apps commands are available:+Confirm you're on the latest version with+[`snow helpers check-version`](/developer-guide/snowflake-cli/command-reference/helpers-commands/check-version): ```bash-snow --version-snow app setup --help-```--If `snow app setup --help` fails, reinstall or upgrade the Snowflake CLI using-the installation guide linked above.+snow helpers check-version+```++If that command isn't recognized, your CLI is too old: follow the installation+guide and upgrade. The command reports the version you have, the latest+published version, and whether an upgrade is available. <a id="label-getting-started-setup-other-requirements"></a>@@ -118,5 +119,6 @@ The assistant scaffolds a Next.js project with a working UI, Snowflake data-access, an `app.yml` manifest, and a `snowflake.yml` project definition.+access, and an [`app.yml`](/developer-guide/snowflake-app-runtime/app-yml)+manifest. <a id="label-getting-started-cortex-code-test-locally"></a>@@ -190,6 +192,6 @@ ### Step 6: Iterate -Make changes and redeploy. Each deploy produces a new version and upgrades the-running service in place. The URL stays the same.+Make changes and redeploy. Each deploy produces a new package version and+alters the running service in place. The URL stays the same. ```text@@ -206,6 +208,7 @@ ### Step 1: Initialize your project -From your project directory, run `snow app setup` to generate a-`snowflake.yml` project definition:+From your project directory, run `snow app setup` to generate an+[`app.yml`](/developer-guide/snowflake-app-runtime/app-yml)+manifest: ```bash@@ -216,61 +219,51 @@ instead of the name derived from the current directory. To target a specific destination, pass `--database`, `--schema`, or `--warehouse`. Setup writes those-values into `snowflake.yml` as explicit overrides.--This creates a `snowflake.yml` in the current directory with a-`snowflake-app` entity that uses defaults from+values into `app.yml` as explicit overrides.++This creates an `app.yml` in the current directory that uses defaults from [account administrator setup](/developer-guide/snowflake-app-runtime/account-admin-setup).-After setup, the file typically references the shared `SNOWFLAKE_APPS` database-and uses a **code workspace** for uploaded source when your role can create-workspaces. For example:+After setup, the file typically references the shared `SNOWFLAKE_APPS` database.+Leave `code_stage` and `code_workspace` unset unless you need to pin a backend;+the CLI picks a workspace or stage at deploy time. For example: ```yaml-definition_version: "2"--entities:- my_app_name:- type: snowflake-app- identifier:- name: MY_APP_NAME- database: SNOWFLAKE_APPS- schema: PUBLIC- artifacts:- - src: ./*- dest: ./- ignore:- - node_modules- - .env*- - __pycache__- - "*.pyc"- - .next- - .git- - snowflake.log- query_warehouse: SNOWFLAKE_APPS_QUERY_WH- code_workspace: SNOWFLAKE_APPS.PUBLIC.SNOWFLAKE_APPS-```--If your role can't create a workspace in the destination database, setup falls-back to a per-app **code stage** (for example `code_stage: MY_APP_NAME_CODE`)-instead.+version: 2++name: MY_APP_NAME+database: SNOWFLAKE_APPS+schema: PUBLIC+query_warehouse: SNOWFLAKE_APPS_QUERY_WH++ignore:+ - node_modules+ - .env*+ - __pycache__+ - "*.pyc"+ - .next+ - .git+ - snowflake.log+``` Setup resolves `database`, `schema`, and `query_warehouse` in this order: the explicit `--database`, `--schema`, and `--warehouse` options; then account defaults from administrator setup; then the personal database default (when-account defaults aren't set); then your current connection settings. After-account setup, you normally don't pick these manually. The `artifacts` section-controls which files are uploaded, and the `ignore` list excludes build output-and local-only files.+account defaults aren't set). After account setup, you normally don't pick+these manually. `app.yml` does **not** fill an unset `database` from the+active CLI connection. The `ignore` list excludes build output and local-only+files from upload. Run with `--dry-run` to preview the resolved configuration without writing the file. -For the full `snowflake.yml` structure and the `snowflake-app` entity schema,-see the-[snowflake.yml reference](/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/snowflake-yml).-For the `snow app setup` options, see the+If the project already has a `snowflake.yml`, see+[](/developer-guide/snowflake-app-runtime/migrate-to-app-yml). Named `targets`+are optional; add them when one project needs more than one deploy+configuration, whether that's a development, stage, and production lifecycle,+several accounts with slightly different configuration, or variants of the app+for different audiences. For a walkthrough, see+[](/developer-guide/snowflake-app-runtime/deploy-targets). For the+`snow app setup` options, see the [snow app setup](/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/setup)-command reference. For identifier rules, mixins, and other project-definition-patterns the CLI applies to `snowflake.yml`, see-[Specify entities](/developer-guide/snowflake-cli/project-definitions/specify-entities).+command reference. ### Step 2: Deploy@@ -291,6 +284,6 @@ ``` -This URL is stable across redeploys. It doesn't change when you upgrade to a-new version.+This URL is stable across redeploys. It doesn't change when you deploy a+new package version. ### Step 3: Open your app@@ -307,6 +300,6 @@ Grant `USAGE` on the database, schema, and Application Service so another role-can open the app. Use the database and schema from your `snowflake.yml`-identifier (for example `SNOWFLAKE_APPS.PUBLIC`):+can open the app. Use the database and schema from your `app.yml` (for example+`SNOWFLAKE_APPS.PUBLIC`): ```sql@@ -321,8 +314,8 @@ <a id="label-getting-started-under-the-hood"></a> -## What happens under the hood+## What deploy does [`snow app deploy`](/developer-guide/snowflake-cli/comm... (truncated)
差分が長いため、途中まで表示しています。
デプロイ設定が snowflake.yml から app.yml に統合され、app.yml でデプロイ先（名前付き targets を含む）とインストール・ビルド・実行コマンドを定義し、対象選択時は --target を指定する構成に変更されました。また、アップロード対象は app.yml の ignore を除くプロジェクトルートとなり、Application Service の操作表現も「upgrade」から「alter」に変更されています。
影響: 既存プロジェクトでは snowflake.yml の設定移行が必要となる可能性があり、詳細な移行手順は追加された migrate-to-app-yml ページを確認する必要があります。
変更内容: 本文を更新（235行追加・89行削除）
--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-app-runtime/deploy+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-app-runtime/deploy@@ -1,10 +1,9 @@ # Deploying with Snowflake App Runtime--Available to all accounts. - [](/developer-guide/snowflake-app-runtime/getting-started) - [](/developer-guide/snowflake-app-runtime/app-yml)+- [](/developer-guide/snowflake-app-runtime/migrate-to-app-yml)+- [](/developer-guide/snowflake-app-runtime/deploy-targets) - [](/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/deploy)-- [](/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/snowflake-yml) - [](/developer-guide/snowflake-app-runtime/account-admin-setup) - [](/sql-reference/sql/create-artifact-repository)@@ -13,5 +12,5 @@ When you're ready to deploy your app to Snowflake, run [`snow app deploy`](/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/deploy).-The command uploads your source, builds it remotely, and creates or upgrades the+The command uploads your source, builds it remotely, and creates or alters the [Application Service](/sql-reference/sql/create-application-service) that serves your app at a stable live URL. Use `--upload-only`, `--build-only`, or@@ -20,9 +19,10 @@ The build job and the Application Service are separate workloads with different-compute, database placement, and outbound access rules.-[`app.yml`](/developer-guide/snowflake-app-runtime/app-yml) defines install,-build, and run commands; [`snowflake.yml`](/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/snowflake-yml)-controls upload paths, deploy destination, and optional settings such as-`artifact_repository`.+compute, database placement, and outbound access rules. A single+[`app.yml`](/developer-guide/snowflake-app-runtime/app-yml) file+defines both the deploy destination (including optional named+[`targets`](/developer-guide/snowflake-app-runtime/app-yml#label-snowflake-apps-manifest-targets))+and the install, build, and run commands. If you declare targets, pass+`--target` to select one. <a id="label-deploy-overview"></a>@@ -48,6 +48,7 @@ <td>Upload</td> <td>- Syncs local source files to an internal stage or workspace (from{" "}- <code>snowflake.yml</code> <code>artifacts</code>).+ Syncs local source files to an internal stage or workspace (the project+ root minus <code>ignore</code> in{" "}+ <code>app.yml</code>). </td> <td><code>--upload-only</code></td>@@ -65,5 +66,5 @@ <td>Deploy</td> <td>- Creates or upgrades the Application Service from that package (typically{" "}+ Creates or alters the Application Service from that package (typically{" "} <code>LATEST</code>). </td>@@ -81,19 +82,17 @@ ## Upload phase -The upload phase copies project files named in your-[`snowflake.yml`](/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/snowflake-yml)-`artifacts` section to Snowflake storage. When your `snowflake.yml` sets-`code_workspace`, uploaded source goes to that **workspace**. When it sets-`code_stage` instead, uploaded source goes to an internal **stage**. Personal-databases don't support stages, so personal database deploys use a workspace.--`snow app setup` usually writes `code_workspace` as the default. For a standard-database, it falls back to `code_stage` only when your role can't create a-workspace in the destination schema. Specifying an existing `code_workspace` in-`snowflake.yml` doesn't require that create privilege by itself; you need access-to write to that workspace at deploy time.--The `ignore` list in `snowflake.yml` excludes local-only paths such as-`node_modules` and `.next` from upload.+The upload phase copies the project root to Snowflake storage, minus the+`ignore` list in [`app.yml`](/developer-guide/snowflake-app-runtime/app-yml).+When the resolved target sets `code_workspace`, uploaded source goes to that+**workspace**. When it sets `code_stage` instead, uploaded source goes to an+internal **stage**. Prefer leaving both unset so the CLI can pick: a workspace+for a [personal database](/user-guide/personal-databases) (personal databases+don't support stages), or a stage when the role can't create a workspace.++Specifying an existing `code_workspace` doesn't require `CREATE WORKSPACE` by+itself; you need access to write to that workspace at deploy time.++The `ignore` list excludes local-only paths such as `node_modules` and `.next`+from upload. <a id="label-deploy-build-phase"></a>@@ -139,5 +138,5 @@ <code>*.snowflakecomputing.app</code> URL (Snowflake terminates TLS on port 443). See{" "}- [ingress](/developer-guide/snowpark-container-services/working-with-services#label-snowpark-containers-service-communicating-ingress).+ [Listen address](/developer-guide/snowflake-app-runtime/runtime-environment#label-runtime-environment-listen-address). </td> </tr>@@ -158,11 +157,11 @@ <td>Lifetime</td> <td>Completes when the build finishes</td>- <td>Runs until suspended, upgraded, or dropped</td>- </tr>- </tbody>--</div>--Build-time outbound access does not carry over to the running app. Each phase+ <td>Runs until suspended, altered, or dropped</td>+ </tr>+ </tbody>++</div>++Build-time outbound access doesn't carry over to the running app. Each phase has its own egress policy. @@ -186,9 +185,47 @@ land in different places: -| Workload | Where it runs |-| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |-| Build job (install/build) | Your [personal database](/user-guide/personal-databases) (`USER$<login_name>`). This placement is fixed for the build phase and does not follow your deploy destination. |-| Application Service | Your **deploy destination**: the entity `identifier.database` and `identifier.schema` in `snowflake.yml` (or [account administrator setup](/developer-guide/snowflake-app-runtime/account-admin-setup) defaults). See [CREATE APPLICATION SERVICE](/sql-reference/sql/create-application-service). |-| Artifact repository | Where you configure [`artifact_repository`](/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/snowflake-yml#label-snowflake-yml-fields) (`name`, and optional `database` and `schema`). If you omit location fields, it defaults to `<app-name>_REPO` in the deploy destination. Independent of where the Application Service runs. |+<div className="colwidths-given">++ <colgroup>+ <col style={{ width: "28.0%" }} />+ <col style={{ width: "72.0%" }} />+ </colgroup>+ <thead>+ <tr>+ <th>Workload</th>+ <th>Where it runs</th>+ </tr>+ </thead>+ <tbody>+ <tr>+ <td>Build job (install/build)</td>+ <td>+ Your [personal database](/user-guide/personal-databases) (+ <code>US... (truncated)
差分が長いため、途中まで表示しています。
GET_LINEAGE (SNOWFLAKE.CORE) に namespace、object_type、external_id、column_name の引数が追加され、Snowflake 外部オブジェクト（EXTERNAL／EXTERNAL_COLUMN）のリネージ取得に対応しました。対象ドメインには CORTEX_AGENT も追加され、戻り値の SOURCE_OBJECT_DOMAIN にも反映されます。
影響: 外部カタログのオブジェクトや Cortex Agents を含むリネージを取得できるようになり、呼び出し時には外部オブジェクトの種類に応じて必須引数を指定する必要があります。
変更内容: 本文を更新（135行追加・4行削除）
--- ahttps://docs.snowflake.com/en/sql-reference/functions/get_lineage-snowflake-core+++ bhttps://docs.snowflake.com/en/sql-reference/functions/get_lineage-snowflake-core@@ -26,5 +26,9 @@ '<direction>', [ <max_distance>, ]- [ '<object_version>' ]+ [ '<object_version>', ]+ [ '<namespace>', ]+ [ '<object_type>', ]+ [ '<external_id>', ]+ [ '<column_name>' ] ) ```@@ -46,9 +50,17 @@ The domain of the object. Supported domains are 'COLUMN', 'TABLE' (which includes all table-like objects including-views and dynamic tables), 'SEMANTIC_VIEW' (for [semantic views](/user-guide/views-semantic/overview)), and 'STAGE'.+views and dynamic tables), 'SEMANTIC_VIEW' (for [semantic views](/user-guide/views-semantic/overview)), 'STAGE', and+'CORTEX_AGENT' (for [Cortex Agents](/user-guide/snowflake-cortex/cortex-agents)).++Specify an agent as 'CORTEX_AGENT'. 'AGENT' isn't a valid domain, even though the object type is displayed as **Agent**+in %sf-web-interface%. For ML lineage, use *TABLE* for feature views (which are dynamic tables and views internally), 'DATASET', or 'MODULE' for models. +To retrieve lineage for an object that isn't in Snowflake, use 'EXTERNAL', or 'EXTERNAL_COLUMN' for a column of such an+object. Both require the `namespace` argument. For more information, see+[Lineage for objects outside Snowflake](#label-get-lineage-external-objects).+ </dd> <dt><code className="samp">'<em>direction</em>'</code></dt>@@ -74,4 +86,32 @@ For versioned objects, such as datasets and models, the version of the object for which lineage is retrieved. If not specified, the default version is used.++</dd>+<dt><code className="samp">'<em>namespace</em>'</code></dt>+<dd>++The namespace of the object, which identifies the system the object comes from. Required when `object_domain` is+'EXTERNAL' or 'EXTERNAL_COLUMN', and not valid for any other domain.++</dd>+<dt><code className="samp">'<em>object_type</em>'</code></dt>+<dd>++The specific type of the object within its namespace, such as the type a data catalog assigns it. Only valid when+`object_domain` is 'EXTERNAL' or 'EXTERNAL_COLUMN'.++</dd>+<dt><code className="samp">'<em>external_id</em>'</code></dt>+<dd>++The identifier that the originating system assigns to the object. Only valid when `object_domain` is 'EXTERNAL' or+'EXTERNAL_COLUMN'.++</dd>+<dt><code className="samp">'<em>column_name</em>'</code></dt>+<dd>++The name of the column to retrieve lineage for. Required when `object_domain` is 'EXTERNAL_COLUMN', and not valid for+any other domain. </dd>@@ -88,5 +128,5 @@ | `SOURCE_OBJECT_SCHEMA` | VARCHAR | The schema that contains the source object. | | `SOURCE_OBJECT_NAME` | VARCHAR | The unqualified name of the source object. |-| `SOURCE_OBJECT_DOMAIN` | VARCHAR | The domain of the target object. Possible values are 'COLUMN', 'TABLE', 'SEMANTIC_VIEW', 'DATASET', 'MODULE' (for ML models), and 'STAGE'. |+| `SOURCE_OBJECT_DOMAIN` | VARCHAR | The domain of the target object. Possible values are 'COLUMN', 'TABLE', 'SEMANTIC_VIEW', 'DATASET', 'MODULE' (for ML models), 'STAGE', and 'CORTEX_AGENT'. | | `SOURCE_OBJECT_VERSION` | VARCHAR | The version of the source object, for versioned objects such as datasets and models. NULL if the source object is not versioned. | | `SOURCE_COLUMN_NAME` | VARCHAR | The name of the source column, if the source object is a column. NULL if the source object is not a column. |@@ -95,5 +135,5 @@ | `TARGET_OBJECT_SCHEMA` | VARCHAR | The schema that contains the target object. | | `TARGET_OBJECT_NAME` | VARCHAR | The unqualified name of the target object. |-| `TARGET_OBJECT_DOMAIN` | VARCHAR | The domain of the target object. Possible values are 'COLUMN', 'TABLE', 'SEMANTIC_VIEW', 'DATASET', 'MODULE' (for ML models), and 'STAGE'. |+| `TARGET_OBJECT_DOMAIN` | VARCHAR | The domain of the target object. Possible values are 'COLUMN', 'TABLE', 'SEMANTIC_VIEW', 'DATASET', 'MODULE' (for ML models), 'STAGE', and 'CORTEX_AGENT'. | | `TARGET_OBJECT_VERSION` | VARCHAR | The version of the target object, for versioned objects such as datasets and models. NULL if the target object is not versioned. | | `TARGET_COLUMN_NAME` | VARCHAR | The name of the target column, if the target object is a column. NULL if the target object is not a column. |@@ -101,4 +141,20 @@ | `DISTANCE` | INTEGER | The distance of the target object from the source object in the lineage path. A direct relationship has a distance of 1. | | `PROCESS` | VARIANT | Provides details about how lineage between the source object and target object was established. For example, it might include the query ID of a SQL query or the name of a stored procedure that moved data from the source object to the target object. |+| `SOURCE_DETAILS` | VARIANT | Additional details about the source object. See [Object details](#label-get-lineage-object-details). |+| `TARGET_DETAILS` | VARIANT | Additional details about the target object. See [Object details](#label-get-lineage-object-details). |++<a id="label-get-lineage-object-details"></a>++## Object details++The `SOURCE_DETAILS` and `TARGET_DETAILS` columns are populated for every object in the lineage path. Keys with no value+for a given object are omitted. Each column contains the following keys:++| Key | Description |+| -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------... (truncated)
差分が長いため、途中まで表示しています。
snow app setup の説明が更新され、app.yml は CLI フラグ、Snowsight のアカウント既定値、接続設定の順で生成され、未設定時は個人データベースが対象になり得ることが明記されました。--database・--schema・--warehouse は生成された app.yml の明示的な上書き値（--warehouse は query_warehouse）となり、通常のリモートビルドでは build_eai の追加は不要と説明されています。
影響: 既存の snowflake.yml を使う Native App プロジェクトには適用されず、App Runtime の新規セットアップでは指定先と設定の優先順位を確認する必要があります。
変更内容: 本文を更新（31行追加・28行削除）
--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/setup+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/setup@@ -1,18 +1,17 @@ # snow app setup--Available to all accounts. - [](/developer-guide/snowflake-app-runtime/about-snowflake-app-runtime) - [](/developer-guide/snowflake-app-runtime/getting-started) - [](/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/overview)-- [](/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/snowflake-yml)+- [](/developer-guide/snowflake-app-runtime/migrate-to-app-yml) - [](/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/deploy) - [](/developer-guide/snowflake-app-runtime/app-yml)--Initializes an `app.yml` for a Snowflake App Runtime project. Creates an-`app.yml` in the current directory: a flat `version: 2` manifest whose `name`,-`database`, `schema`, and `query_warehouse` are preconfigured from account-parameters and the current connection. This command does not apply to Native App-projects.+- [](/developer-guide/snowflake-app-runtime/deploy-targets)++Initializes an [`app.yml`](/developer-guide/snowflake-app-runtime/app-yml)+manifest for a Snowflake App Runtime project. Creates an `app.yml`+file in the current directory with deployment fields preconfigured from+command-line flags, then Snowsight account defaults, then your personal+database. This command doesn't apply to Snowflake Native Apps projects. ## Syntax@@ -66,5 +65,5 @@ <dd> -Only print the resolved configuration values without writing app.yml. Default: False.+Only print the resolved configuration values without writing `app.yml`. Default: False. </dd>@@ -146,5 +145,7 @@ <dd> -Database to use. Overrides the value specified for the connection.+Database to use. In `snow app setup`, this value is written to the generated+`app.yml` as an explicit override, taking precedence over account+parameters and connection defaults. </dd>@@ -152,5 +153,7 @@ <dd> -Database schema to use. Overrides the value specified for the connection.+Database schema to use. In `snow app setup`, this value is written to the+generated `app.yml` as an explicit override, taking precedence over+account parameters and connection defaults. </dd>@@ -164,5 +167,7 @@ <dd> -Warehouse to use. Overrides the value specified for the connection.+Warehouse to use. In `snow app setup`, this value is written to the generated+`app.yml` as the `query_warehouse` override, taking precedence over+account parameters and connection defaults. </dd>@@ -241,12 +246,13 @@ The `snow app setup` command bootstraps a new Snowflake App Runtime project by-generating an `app.yml` file: a flat `version: 2` manifest that contains the-default deployment details. Setup resolves the destination database, schema,-and warehouse in this order: the explicit `--database`, `--schema`, and-`--warehouse` options, then Snowsight account defaults from+generating an [`app.yml`](/developer-guide/snowflake-app-runtime/app-yml)+file with default deployment details. Setup resolves the destination+database, schema, and warehouse in this order: the explicit `--database`,+`--schema`, and `--warehouse` options, then Snowsight account defaults from [account administrator setup](/developer-guide/snowflake-app-runtime/account-admin-setup),-then your current connection settings. Remote builds use the shared external-access integration from Snowsight setup; you don't add one in `app.yml`-for the usual path.+then your current connection settings. If those aren't set, setup may target+your personal database. Remote builds use the shared external access+integration from Snowsight setup; you don't add `build_eai` in `app.yml` for+the usual path. Existing projects that use a `snowflake.yml` with a `snowflake-app` entity keep@@ -270,7 +276,5 @@ map to `DEFAULT_SNOWFLAKE_APPS_DESTINATION_DATABASE`, `DEFAULT_SNOWFLAKE_APPS_DESTINATION_SCHEMA`, and-`DEFAULT_SNOWFLAKE_APPS_QUERY_WAREHOUSE`. For the full resolution order and the-complete list of account parameters, see-[How field values are resolved](/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/snowflake-yml#label-snowflake-yml-resolution).+`DEFAULT_SNOWFLAKE_APPS_QUERY_WAREHOUSE`. Setup leaves `code_stage` and `code_workspace` out of the generated `app.yml`, so@@ -278,8 +282,8 @@ provisions temporary code storage for the build and drops it afterward. Set `code_stage` or `code_workspace` in `app.yml` to keep a persisted stage or-workspace instead.+workspace instead. Personal databases use a workspace. If `app.yml` already exists in the current directory (and you aren't using-`--dry-run`), setup prints a message and does not overwrite the file.+`--dry-run`), setup prints a message and doesn't overwrite the file. If you omit `--app-name`, setup uses the current directory name, converting@@ -294,7 +298,6 @@ For a concrete example after setup, see [Getting started with Snowflake App Runtime](/developer-guide/snowflake-app-runtime/getting-started).-For entity keys, identifiers, mixins, and other patterns the CLI applies to-project files, see-[Specify entities](/developer-guide/snowflake-cli/project-definitions/specify-entities).+If the project still uses `snowflake.yml`, see+[](/developer-guide/snowflake-app-runtime/migrate-to-app-yml). ## Examples
Alerts in Snowsight に Dynamic tables と Iceberg catalog-linked databases のアラートが追加され、それぞれの前提条件（イベントログ設定、カタログ統合済みデータベース）が新設されました。また、「Available to all accounts.」の記載が削除され、アラートテンプレート表も改訂されていますが、diff からは詳細不明です。 影響: 対象機能を監視する場合、dynamic table のイベントログやcatalog integrationの事前設定が必要です。
変更内容: 本文を更新（40行追加・14行削除）
--- ahttps://docs.snowflake.com/en/user-guide/alerts-ui+++ bhttps://docs.snowflake.com/en/user-guide/alerts-ui@@ -1,5 +1,3 @@ # Alerts in %sf-web-interface%--Available to all accounts. - [](/user-guide/alerts)@@ -21,4 +19,6 @@ - [Openflow](/user-guide/data-integration/openflow/about) - [Data quality](/user-guide/data-quality-intro)+ - [Dynamic tables](/user-guide/dynamic-tables/overview)+ - [Iceberg tables](/user-guide/tables-iceberg-catalog-linked-database) (catalog-linked databases) - **Proactive monitoring of Snowflake features:** You can easily configure notifications for failures, latency, or data anomalies@@ -34,4 +34,6 @@ - [Prerequisites for Openflow alerts](#prerequisites-for-openflow-alerts) - [Prerequisites for data quality alerts](#prerequisites-for-data-quality-alerts)+- [Prerequisites for dynamic table alerts](#prerequisites-for-dynamic-table-alerts)+- [Prerequisites for Iceberg catalog-linked database alerts](#prerequisites-for-iceberg-catalog-linked-database-alerts) - [Setting up notifications for alerts](#setting-up-notifications-for-alerts) - [Creating a role for accessing alerts in %sf-web-interface%](#creating-a-role-for-accessing-alerts-in-sf-web-interface)@@ -98,4 +100,24 @@ For information, see [](/user-guide/data-quality-working).++<a id="label-alerts-center-prerequisites-dynamic-tables"></a>++### Prerequisites for dynamic table alerts++The [dynamic table](/user-guide/dynamic-tables/overview) alerts monitor refresh status events that are recorded to an event+table. Make sure that event logging is configured for the dynamic tables that you want to monitor, including the severity+level needed for refresh failures and upstream failures.++For information, see [](/user-guide/dynamic-tables/monitoring#label-dynamic-tables-monitor-event-table-alerts).++<a id="label-alerts-center-prerequisites-iceberg"></a>++### Prerequisites for Iceberg catalog-linked database alerts++The Iceberg alerts monitor events from [catalog-linked databases](/user-guide/tables-iceberg-catalog-linked-database). Make sure+that you have a catalog-linked database with a catalog integration configured. Generic Iceberg tables that aren't part of a+catalog-linked database don't emit the events that these alerts monitor.++For information, see [](/user-guide/tables-iceberg-catalog-linked-database). <a id="label-alerts-center-prerequisites-notification"></a>@@ -254,16 +276,20 @@ <div className="colwidths-auto multi-row-table"> -| Template group | Template | Description |-| ---------------- | ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |-| **DATA_QUALITY** | **Anomaly detection alert** | Monitors for [anomalies detected in data quality metrics](/user-guide/data-quality-anomaly), triggering an alert when unusual patterns or outliers are identified. |-| | **Expectation violations alert** | Monitors for [data quality expectation violations](/user-guide/data-quality-expectations), triggering an alert when defined expectations are violated. |-| **OPENFLOW** | **Connector backpressure (object count)** | Monitors the connector queue count to determine if it exceeds the backpressure threshold, which can indicate that the downstream system can't keep up with the data flow rate. |-| | **Connector backpressure (bytes)** | Monitors the connector queued bytes to determine if it exceeds the backpressure threshold, which can indicate that there is memory pressure in the data pipeline. |-| | **High queued bytes alert** | Monitors the connector queue bytes to determine if it approaches the backpressure threshold (>80%), which can provide an early warning before backpressure occurs. |-| | **High queued count alert** | Monitors the connector queue object count to determine if it approaches the backpressure threshold (>80%), which can provide an early warning before backpressure occurs. |-| | **No data alert** | Monitors for connectors that have an active processing time but are not receiving or sending any data, which can indicate potential data flow issues. |-| | **Runtime high error rate alert** | Monitors the Openflow runtime processors for a high volume of ERROR-level logs, which can indicate processing failures. |-| | **Table replication failure alert** | Monitors for table replication transitions to a FAILED state, which can indicate a critical data synchronization issue. |-| **TASKS** | **Error rate alert** | Triggers an alert when the cumulative task error rate exceeds a specified threshold. |+| Template group | Template | Description |+| ------------------ | ----------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |+| **DATA_QUALITY** | **Anomaly detection alert** | Monitors for [anomalies detected in data quality metrics](/user-guide/data-quality-anomaly), triggering an alert when unusual patterns or outliers are identified. |+| | **Expectation violations alert** | Monitors for [data quality expectation violations](/user-guide/data-quality-expectations), triggering an alert when defined expectations are violated. |+| **DYNAMIC_TABLES** | **Refresh failure alert** | Monitors [dynamic table](/user-guide/dynamic-tables/overview) refresh failures, triggering an alert when a dynamic table's own refresh fails. |+| | **Upstream failure alert** | Monitors [dynamic table](/user-guide/dynamic-tables/overview) upstream failures, triggering an alert when a refresh fails because of an upstream dependency. |+| **ICEBERG** | **Refresh status alert** | Monitors auto-refresh status changes for tables in a [catalog-linked database](/user-guide/tables-iceberg-catalog-linked-database), triggering an alert when refresh leaves a healthy state. |+| | **Discovery failure alert** | Monitors discovery and sync failures for a [catalog-linked database](/user-guide/tables-iceberg-catalog-linked-database), triggering an alert when catalog objects fail to sync. |+| **OPENFLOW** | **Connector backpressure (object count)** | Monitors the connector queue count to determine if it exceeds the backpressure threshold, which can indicate that the downstream system can't keep up with the data flow rate. |+| | **Connector backpressure (bytes)** | Monitors the connector queued bytes to determine if it exceeds the backpressure threshold, which can indicate that there is memory pressure in the data pipeline. ... (truncated)
差分が長いため、途中まで表示しています。
Snowflake App Runtime の設定対象が snowflake.yml の snowflake-app エンティティから app.yml 前提に整理され、旧形式は移行ガイドへ案内されるようになりました。また、--target は未指定時にトップレベルの default_target を使い、未設定で targets がある場合は必須となり、デプロイは Application Service を app.yml の仕様へ収束させます。Database・schema・warehouse の接続上書きは、アプリの配置先や query_warehouse を変更しないことも明記されました。
影響: 旧形式の App Runtime プロジェクトでは app.yml への移行と、default_target または --target の設定確認が必要です。
変更内容: 本文を更新（27行追加・20行削除）
--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/deploy+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/deploy@@ -1,5 +1,3 @@ # snow app deploy--Available to all accounts. - [](/developer-guide/snowflake-app-runtime/about-snowflake-app-runtime)@@ -8,15 +6,19 @@ - [](/developer-guide/snowflake-app-runtime/deploy) - [](/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/setup)-- [](/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/snowflake-yml)+- [](/developer-guide/snowflake-app-runtime/migrate-to-app-yml) - [](/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/teardown)--Uploads your project source to Snowflake, builds it remotely, and starts or-upgrades the Application Service. This is the primary command for shipping+- [](/developer-guide/snowflake-app-runtime/app-yml)+- [](/developer-guide/snowflake-app-runtime/deploy-targets)++Uploads your project source to Snowflake, builds it remotely, and creates or+alters the Application Service. This is the primary command for shipping changes to a Snowflake App Runtime project. By default it runs three phases in order: upload, build, and deploy. -When the project `snowflake.yml` contains a `snowflake-app` entity, `snow app-deploy` runs the Snowflake App Runtime flow (upload, build, deploy). When it-contains a Native App entity, the command runs the Native App flow instead.+When the project has an `app.yml`, `snow app deploy` runs the Snowflake App+Runtime flow (upload, build, deploy). When `snowflake.yml` contains a Native+App entity, the command runs the Native App flow instead. Older App Runtime+projects that still use `snowflake.yml` are covered in+[](/developer-guide/snowflake-app-runtime/migrate-to-app-yml). ## Syntax@@ -77,5 +79,5 @@ <dd> -Create or upgrade the Application Service without re-uploading or rebuilding. Only one of `--upload-only`, `--build-only`, or `--promote-only` can be used at a time. Default: False.+Create or alter the Application Service without re-uploading or rebuilding. Only one of `--upload-only`, `--build-only`, or `--promote-only` can be used at a time. Default: False. </dd>@@ -83,5 +85,5 @@ <dd> -(Snowflake App Runtime only) Name of the target (environment) to deploy, as declared in the `targets` block of `app.yml` (version 2 or higher). Defaults to `targets.default`.+(Snowflake App Runtime only) Name of the target (environment) declared in the `targets` block of `app.yml`. If you omit `--target`, the CLI uses the top-level `default_target`. Required when `targets` are declared and `default_target` is unset. </dd>@@ -155,5 +157,6 @@ <dd> -Database to use. Overrides the value specified for the connection.+Database to use. Overrides the value specified for the connection. This+doesn't change the Application Service destination in `app.yml`. </dd>@@ -161,5 +164,6 @@ <dd> -Database schema to use. Overrides the value specified for the connection.+Database schema to use. Overrides the value specified for the connection. This+doesn't change the Application Service destination in `app.yml`. </dd>@@ -173,5 +177,6 @@ <dd> -Warehouse to use. Overrides the value specified for the connection.+Warehouse to use. Overrides the value specified for the connection. This+doesn't change `query_warehouse` in `app.yml`. </dd>@@ -255,6 +260,7 @@ that produces an immutable package version in the application's artifact repository.-3. **Deploy phase**: Creates or upgrades the Application Service from that- package (typically the `LATEST` version).+3. **Deploy phase**: Creates or alters the Application Service from that+ package (typically the `LATEST` version). The command converges the service+ to the `app.yml` specification. The command name covers all three phases. **Deploy phase** means publishing the@@ -269,5 +275,6 @@ [Getting started with Snowflake App Runtime](/developer-guide/snowflake-app-runtime/getting-started). -Run `snow app setup` to generate `snowflake.yml` for your deploy destination.+Run `snow app setup` to generate `app.yml` for your deploy destination.+With named targets, pass `--target` or set `default_target` in `app.yml`. If a deploy fails partway through, retry just the failed phase:@@ -275,9 +282,9 @@ - `snow app deploy --upload-only`: Re-upload source files without rebuilding or redeploying. - `snow app deploy --build-only`: Re-trigger the build without re-uploading or redeploying.-- `snow app deploy --promote-only`: Create or upgrade the service without re-uploading or rebuilding.+- `snow app deploy --promote-only`: Create or alter the service without re-uploading or rebuilding. Only one phase flag can be used at a time. -`snow app deploy` is not idempotent. Running it again restarts the selected+`snow app deploy` isn't idempotent. Running it again restarts the selected phase sequence. If upload and build have already succeeded, use `--promote-only` instead of rerunning the full pipeline.@@ -312,5 +319,5 @@ When your uploaded source includes [`app.yml`](/developer-guide/snowflake-app-runtime/app-yml), Snowflake validates-the manifest during the build phase. Syntax errors, invalid `profile.icon`+the manifest during the build phase. Syntax errors, invalid `icon` paths, or other manifest problems fail the build with an error similar to:
Fine-tuning 対応モデルが6種類から llama3.1-8b のみに縮小されました。トークン上限表から他モデル（llama3-8b、llama3-70b、llama3.1-70b、mistral-7b、mixtral-8x7b）の記載も削除され、llama3.1-8b は1 epochで150k、既定の3 epochsで50kのままです。
影響: 新規・既存のファインチューニング対象は llama3.1-8b に限定され、削除されたモデルを利用していた運用への影響や移行手段はdiffからは詳細不明です。
変更内容: 本文を更新（15行追加・30行削除）
--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-finetuning+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-finetuning@@ -86,12 +86,7 @@ <div className="colwidths-auto"> - | Model | 1 epoch | 3 epochs (default) |- | -------------- | ------- | ------------------ |- | `llama3-8b` | 186k | 62k |- | `llama3-70b` | 21k | 7k |- | `llama3.1-8b` | 150k | 50k |- | `llama3.1-70b` | 13.5k | 4.5k |- | `mistral-7b` | 45k | 15k |- | `mixtral-8x7b` | 27k | 9k |+ | Model | 1 epoch | 3 epochs (default) |+ | ------------- | ------- | ------------------ |+ | `llama3.1-8b` | 150k | 50k | </div>@@ -131,12 +126,7 @@ You have the following base models that you can fine-tune. Models available for fine-tuning may be added or removed in the future: -| Name | Description |-| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |-| `llama3-8b` | A large language model from Meta that is ideal for tasks that require low to moderate reasoning like text classification, summarization, and sentiment analysis. |-| `llama3-70b` | An LLM from Meta that delivers state of the art performance ideal for chat applications, content creation, and enterprise applications. |-| `llama3.1-8b` | A large language model from Meta that is ideal for tasks that require low to moderate reasoning. It's a light-weight, ultra-fast model with a context window of 24K. |-| `llama3.1-70b` | An open source model that demonstrates state-of-the-art performance ideal for chat applications, content creation, and enterprise applications. It is a highly performant, cost effective model that enables diverse use cases. |-| `mistral-7b` | 7 billion parameter large language model from Mistral AI that is ideal for your simplest summarization, structuration, and question answering tasks that need to be done quickly. It offers low latency and high throughput processing for multiple pages of text with its 32K context window. |-| `mixtral-8x7b` | A large language model from Mistral AI that is ideal for text generation, classification, and question answering. Mistral models are optimized for low latency with low memory requirements, which translates into higher throughput for enterprise use cases. |+| Name | Description |+| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |+| `llama3.1-8b` | A large language model from Meta that is ideal for tasks that require low to moderate reasoning. It's a light-weight, ultra-fast model with a context window of 24K. | <a id="label-cortex-finetuning-howto"></a>@@ -170,5 +160,5 @@ 'CREATE', 'my_tuned_model',- 'mistral-7b',+ 'llama3.1-8b', 'SELECT a AS prompt, d AS completion FROM train', 'SELECT a AS prompt, d AS completion FROM validation'@@ -195,12 +185,7 @@ <blockquote> - | Model | Context Window | Input Context (prompt) | Output Context (completion) |- | ------------ | -------------- | ---------------------- | --------------------------- |- | llama3-8b | 8k | 6k | 2k |- | llama3-70b | 8k | 6k | 2k |- | llama3.1-8b | 24k | 20k | 4k |- | llama3.1-70b | 8k | 6k | 2k |- | mistral-7b | 32k | 28k | 4k |- | mixtral-8x7b | 32k | 28k | 4k |+ | Model | Context Window | Input Context (prompt) | Output Context (completion) |+ | ----------- | -------------- | ---------------------- | --------------------------- |+ | llama3.1-8b | 24k | 20k | 4k | </blockquote>@@ -216,5 +201,5 @@ #### Use SQL -This example uses the `mistral-7b` model as the base model to create a job with a model output name of `my_tuned_model` and training+This example uses the `llama3.1-8b` model as the base model to create a job with a model output name of `my_tuned_model` and training and validation data querying from the `my_training_data` and `my_validation_data` tables respectively. @@ -226,5 +211,5 @@ 'CREATE', 'my_tuned_model',- 'mistral-7b',+ 'llama3.1-8b', 'SELECT prompt, completion FROM my_training_data', 'SELECT prompt, completion FROM my_validation_data'@@ -238,5 +223,5 @@ 'CREATE', 'mydb.myschema.my_tuned_model',- 'mistral-7b',+ 'llama3.1-8b', 'SELECT prompt, completion FROM mydb2.myschema2.my_training_data', 'SELECT prompt, completion FROM mydb2.myschema2.my_validation_data'@@ -354,7 +339,7 @@ For example,-if you create a fine-tuned model based on `mistral-7b` in your account in the AWS US West 2 region, you can use data sharing to share it+if you create a fine-tuned model based on `llama3.1-8b` in your account in the AWS US West 2 region, you can use data sharing to share it with another account in this region, or you can use database replication to replicate the model to another account in your organization-in a different region that supports the `mistral-7b` model, such as AWS Europe West. For details on replicating objects, see+in a different region that supports the `llama3.1-8b` model, such as AWS Europe West. For details on replicating objects, see [](/user-guide/account-replication-config).
IN SCHEMA SNOWFLAKE.MODELSの指定が推奨され、未指定時は通常のSHOWスコープに従い、別データベースが現行の場合は権限があっても0行になり得ることが明記されました。また、LEGACYモデルの利用条件と移行推奨、EOLモデルは全アカウントで利用不可となりクエリ/API呼び出しが失敗することが具体化されました。
影響: 実務では、確実にモデル一覧を取得するためSHOW CORTEX BASE MODELS IN SCHEMA SNOWFLAKE.MODELSを使用し、LEGACYモデルからサポート対象モデルへ移行する必要があります。
変更内容: 本文を更新（34行追加・8行削除）
--- ahttps://docs.snowflake.com/en/sql-reference/sql/show-cortex-base-models+++ bhttps://docs.snowflake.com/en/sql-reference/sql/show-cortex-base-models@@ -59,6 +59,18 @@ <dd> -Optionally scopes the command to the `SNOWFLAKE.MODELS` schema, where all Cortex Base Model-objects are stored. This is the only scope that applies to Cortex Base Models.+Scopes the command to the `SNOWFLAKE.MODELS` schema, where all Cortex Base Model+objects are stored. Snowflake recommends specifying this clause.++If you omit this clause, the command follows standard SHOW scoping:++- If the session has a current database, the command is scoped to that database+ (and to the current schema, if one is set). Cortex Base Models exist only in+ `SNOWFLAKE.MODELS`, so an unqualified command returns no rows when another+ database is current, even if the current role has the required model privileges.+- If the session has no current database, the command uses account scope and can+ return Cortex Base Models.++To list Cortex Base Models regardless of the session's current database, specify+`IN SCHEMA SNOWFLAKE.MODELS`. </dd>@@ -145,7 +157,12 @@ See [Snowflake Preview Features](/release-notes/preview-features) for details. - `PRPR`: Private preview. The model is available to accounts that have been specifically enabled.- - `LEGACY`: The model has entered its legacy period. Using this model is not- recommended. Migrate to a supported model before its end-of-life.- - `EOL`: End of life. The model is no longer available.+ - `LEGACY`: The model has entered its legacy period. Accounts that used the+ model before the legacy date can continue to use it until end-of-life.+ Accounts that had not used the model can't start using it. Using this+ model is not recommended. Migrate to a supported model before its+ end-of-life. For details, see+ [Model lifecycle: legacy and end-of-life](/user-guide/snowflake-cortex/aisql-regional-availability#label-cortex-model-lifecycle).+ - `EOL`: End of life. The model is no longer available to any account.+ Queries and API calls that name the model fail. </td> </tr>@@ -202,6 +219,8 @@ The output is filtered based on the user's model RBAC grants. Only models for-which the current role has been granted access appear in the results. For-information about granting access to Cortex Base Models, see+which the current role has been granted access appear in the results. If the+command is scoped to a database other than `SNOWFLAKE`, the result can be empty+even when those grants exist. For information about granting access to Cortex+Base Models, see [Model access and privileges](/user-guide/snowflake-cortex/aisql-privileges-and-access). @@ -218,4 +237,9 @@ ## Usage notes +- Cortex Base Models exist only in `SNOWFLAKE.MODELS`. Use+ `SHOW CORTEX BASE MODELS IN SCHEMA SNOWFLAKE.MODELS` so the command isn't+ scoped to the session's current database. Omitting `IN SCHEMA SNOWFLAKE.MODELS`+ can return zero rows even when the current role has the correct+ `CORTEX-MODEL-ROLE-*` grants. - This command returns only Cortex Base Models. To list all model objects in your account, including Cortex Base Models and user models, use@@ -249,5 +273,7 @@ ## Examples -List all Cortex Base Models accessible to the current role:+List all Cortex Base Models accessible to the current role. Specify+`IN SCHEMA SNOWFLAKE.MODELS` so the listing isn't limited to the session's+current database: ```sql
Snowflake-provided tags（cost center、certification status、sensitivity、environment、project、SKIP_TAG_PROPAGATION）が追加され、SKIP_TAG_PROPAGATION は Enterprise Edition 以上が必要と記載されました。一方、Second generation Openflow、Azure の Stable egress IP addresses、Snowflake App Runtime、Alerts in Snowsight、External lineage のプレビュー項目が一覧から削除されました。
影響: プレビュー機能一覧では、Snowflake-provided tagsの案内が追加された一方、削除された機能の提供状況や廃止を意味するかはdiff からは詳細不明です。
変更内容: 本文を更新（5行追加・36行削除）
--- ahttps://docs.snowflake.com/en/release-notes/preview-features+++ bhttps://docs.snowflake.com/en/release-notes/preview-features@@ -79,18 +79,9 @@ <tbody> <tr>- <td>[Second generation Openflow](/user-guide/data-integration/openflow/gen2/index)</td>- <td>Open</td>- <td>August 2026</td>- <td>[](/user-guide/data-integration/openflow/gen2/index)</td>- <td>Gen 2 Openflow deployments, runtimes, and connectors are first-class Snowflake SQL objects with versioned connector configuration and standard RBAC. Supported connectors at Public Preview: PostgreSQL CDC, MySQL/MariaDB CDC. Migration from gen 1 to gen 2 is separately available in Private Preview.</td>- </tr>- <tr>- <td>Stable egress IP addresses on Azure</td>- <td>Open</td>- <td>August 2026</td>- <td>[](/user-guide/egress-ip/network-egress), [](/sql-reference/functions/system_get_snowflake_egress_ip_ranges)</td>- <td>- Generate Snowflake egress IP address ranges to allowlist on external servers. This preview covers Azure deployments. The feature is generally available on AWS Commercial deployments.- </td>+ <td>[Snowflake-provided tags](/user-guide/object-tagging/snowflake-provided-tags)</td>+ <td>Open</td>+ <td>August 2026</td>+ <td>[](/user-guide/object-tagging/snowflake-provided-tags)</td>+ <td>Use predefined tags in the `SNOWFLAKE.TAGS` schema for cost center, certification status, sensitivity, environment, project, and pausing tag propagation. `SKIP_TAG_PROPAGATION` requires Enterprise Edition or higher.</td> </tr> <tr>@@ -354,11 +345,4 @@ </tr> <tr>- <td>Snowflake App Runtime</td>- <td>Open</td>- <td>June 2026</td>- <td>[](/developer-guide/snowflake-app-runtime/about-snowflake-app-runtime), [](/developer-guide/snowflake-app-runtime/getting-started), [](/developer-guide/snowflake-app-runtime/security)</td>- <td>Build and deploy Node.js web applications (with a focus on Next.js) directly on Snowflake using Cortex Code or the Snowflake CLI. Describe an app in natural language, test it locally, and deploy to a live, SSO-backed URL. Python support is planned.</td>- </tr>- <tr> <td>Optimized refresh for account replication</td> <td>Open</td>@@ -443,11 +427,4 @@ </tr> <tr>- <td>Alerts in Snowsight</td>- <td>Open</td>- <td>April 2026</td>- <td>[](/user-guide/alerts-ui)</td>- <td>Create, monitor, and edit alerts in Snowsight using templates and configurable parameters.</td>- </tr>- <tr> <td>Create tags in Snowsight (Tags & policies)</td> <td>Open</td>@@ -539,12 +516,4 @@ <td>April 2026</td> <td>[](/user-guide/snowflake-cortex/cortex-agents-sharing)</td>- <td></td>- </tr>-- <tr>- <td>External lineage</td>- <td>Open</td>- <td>January 2026</td>- <td>[](/user-guide/external-lineage)</td> <td></td> </tr>
querySnowflake（lib/snowflake.ts）を使ってモードを切り替える説明に更新され、関連ページへの導線が追加されました。また、app.yml の secrets は環境変数ではなく /secrets/<name>/ 配下のファイルとしてマウントされること、トークンの参照先、external_access_integrations の宣言方法が明記されました。
影響: シークレットの読み取り方法が環境変数からファイルアクセスへ変更されたため、アプリケーション実装と app.yml の外部アクセス統合設定を見直す必要があります。
変更内容: 本文を更新（24行追加・14行削除）
--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-app-runtime/secure-development+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-app-runtime/secure-development@@ -1,7 +1,7 @@ # Developing secure Snowflake App Runtime applications -Available to all accounts.- - [](/developer-guide/snowflake-app-runtime/security)+- [](/developer-guide/snowflake-app-runtime/query-snowflake)+- [](/developer-guide/snowflake-app-runtime/runtime-environment) - [](/developer-guide/snowflake-app-runtime/access-control) - [](/developer-guide/snowflake-app-runtime/app-yml)@@ -49,5 +49,7 @@ [Enforce application-level access control](#label-snowflake-app-runtime-secure-development-app-acl)). -With the scaffolded SDK, switching between modes is one parameter:+With `querySnowflake` from `lib/snowflake.ts` (see+[](/developer-guide/snowflake-app-runtime/query-snowflake)), switching between+modes is one parameter: ```typescript@@ -65,5 +67,5 @@ caller's rights queries have no access to the caller's data. An account administrator sets these up. See-[Securing Snowflake App Runtime applications](/developer-guide/snowflake-app-runtime/security#label-snowflake-app-runtime-security-callers-rights-controls)+[Scoping caller's rights](/developer-guide/snowflake-app-runtime/security#label-snowflake-app-runtime-security-callers-rights-controls) for details. @@ -214,9 +216,12 @@ ### Declare secrets in app.yml, not in source code -If your application uses external credentials, declare them as secrets in-[`app.yml`](/developer-guide/snowflake-app-runtime/app-yml). Snowflake injects-them into your application at runtime as environment variables. They're never-embedded in your source tree, committed to version control, or visible in the-container image.+If your application uses external credentials, declare them under+[`secrets`](/developer-guide/snowflake-app-runtime/app-yml#label-snowflake-apps-manifest-secrets)+in [`app.yml`](/developer-guide/snowflake-app-runtime/app-yml). Snowflake mounts+each secret as files under `/secrets/<name>/`, not as environment variables.+They're never embedded in your source tree, committed to version control, or+visible in the container image. For the files each secret type produces and how+to read them, see+[Secret files](/developer-guide/snowflake-app-runtime/runtime-environment#label-runtime-environment-secret-files). Hardcoded credentials in source code are a persistent breach risk: anyone with read@@ -239,7 +244,10 @@ Snowflake handles authentication automatically for App Runtime: an OAuth token is available inside the container and rotates automatically. You don't manage Snowflake-credentials at all. For external services, the same principle applies: request-short-lived credentials through the service's OAuth or credential rotation tooling,-rather than embedding a long-lived secret.+credentials at all. For the token paths and how to combine them with a caller token,+see+[Session and caller tokens](/developer-guide/snowflake-app-runtime/runtime-environment#label-runtime-environment-tokens).+For external services, the same principle applies: request short-lived credentials+through the service's OAuth or credential rotation tooling, rather than embedding a+long-lived secret. Static long-lived credentials remain valid until manually rotated. If one is ever@@ -361,6 +369,8 @@ ### Minimize external access scope -If your application makes outbound network calls, declare exactly the hostnames it-contacts in the network rules for your external access integration. An overly+If your application makes outbound network calls, declare the integrations under+[`external_access_integrations`](/developer-guide/snowflake-app-runtime/app-yml#label-snowflake-apps-manifest-external-access-integrations)+in `app.yml`, and list exactly the hostnames the app contacts in the network+rules for those integrations. An overly permissive rule is a risk multiplier: any code running in your process, including npm dependencies and their transitive dependencies, can make outbound requests to
Snowflake App Runtime のプロジェクト定義が snowflake.yml から app.yml に変更され、migrate-to-app-yml と deploy-targets の案内が追加されました。最新 CLI の利用と snow helpers check-version による確認が必要で、名前付き targets を定義した場合のみ --target を指定します。
影響: 旧 CLI は app.yml のデプロイキーを無視して snowflake.yml を要求するため、App Runtime プロジェクトでは CLI の更新と app.yml への移行が実務上必要です。
変更内容: 本文を更新（18行追加・15行削除）
--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/overview+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/overview@@ -1,5 +1,3 @@ # Snowflake Apps CLI commands--Available to all accounts. - [](/developer-guide/snowflake-app-runtime/about-snowflake-app-runtime)@@ -8,4 +6,6 @@ - [](/user-guide/cortex-code/cortex-code-desktop/building-apps) - [](/developer-guide/snowflake-app-runtime/app-yml)+- [](/developer-guide/snowflake-app-runtime/migrate-to-app-yml)+- [](/developer-guide/snowflake-app-runtime/deploy-targets) - [](/sql-reference/commands-snowflake-apps) @@ -17,16 +17,20 @@ skill runs `snow app` commands for you as you scaffold, deploy, or manage apps from chat. -Starting with %sf-cli% version 3.17.0, `snow app` commands support both Snowflake Native Apps and Snowflake App Runtime.-The CLI selects the correct flow automatically based on the entity type in-`snowflake.yml`.+The CLI selects the correct flow automatically. -The CLI infers the target entity from `snowflake.yml`. If your project defines-more than one `snowflake-app` entity, you can pass `--entity-id <entity_id>` on-any `snow app` command to select a specific one explicitly.+Use the latest Snowflake CLI. Confirm with+[`snow helpers check-version`](/developer-guide/snowflake-cli/command-reference/helpers-commands/check-version).+If that command isn't recognized, upgrade before you rely on `app.yml`. An older+CLI ignores the deployment keys in `app.yml` and still expects `snowflake.yml`. -These pages document the Snowflake App Runtime behavior of each command. For the-Snowflake Native App behavior, see+For Snowflake App Runtime, use [`app.yml`](/developer-guide/snowflake-app-runtime/app-yml).+Named `targets` are optional; pass `--target` only when the file defines them.+Native App projects use `snowflake.yml`; see [snow app commands](/developer-guide/snowflake-cli/command-reference/native-apps-commands/overview).+If the project still has a `snowflake-app` entity, see+[](/developer-guide/snowflake-app-runtime/migrate-to-app-yml).++These pages document the Snowflake App Runtime behavior of each command. <a id="label-snowflake-apps-cli-project-definition"></a>@@ -34,7 +38,6 @@ ## Project definition -For the structure and schema of the `snowflake.yml` project definition for-`snowflake-app` entities, see the-[snowflake.yml reference](/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/snowflake-yml).+For the structure of `app.yml`, see the+[app.yml reference](/developer-guide/snowflake-app-runtime/app-yml). <a id="label-snowflake-apps-cli-project-setup"></a>@@ -42,5 +45,5 @@ ## Project setup -- [snow app setup](/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/setup): Initialize a `snowflake.yml` for a new Snowflake App Runtime project+- [snow app setup](/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/setup): Initialize an `app.yml` for a new Snowflake App Runtime project <a id="label-snowflake-apps-cli-deployment"></a>@@ -48,5 +51,5 @@ ## Deployment -- [snow app deploy](/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/deploy): Upload source, build remotely, and start or upgrade the Application Service+- [snow app deploy](/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/deploy): Upload source, build remotely, and create or alter the Application Service - [snow app bundle](/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/bundle): Copy resolved artifacts into a local output directory for inspection - [snow app validate](/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/validate): Check that the project can be bundled and the target database and schema exist
ページが legacy と明示され、従来の snowflake.yml（type: snowflake-app）とビルド専用 app.yml の構成を説明する内容に整理されました。現行プロジェクトは単一の app.yml を使用し、移行手段として migrate-to-app-yml が追加され、app.yml に version: 2 がある場合はこの snowflake.yml が無視されること、Native App のスキーマは別ページで扱うことが追記されました。
影響: 既存プロジェクトは app.yml への移行を検討する必要があり、version: 2 の app.yml が存在する場合は Snowflake App Runtime の処理で snowflake.yml が使われません。
変更内容: 本文を更新（20行追加・13行削除）
--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/snowflake-yml+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/snowflake-yml@@ -1,5 +1,3 @@-# snowflake.yml project definition for Snowflake App Runtime--Available to all accounts.+# snowflake.yml project definition for Snowflake App Runtime (legacy) - [](/developer-guide/snowflake-app-runtime/about-snowflake-app-runtime)@@ -8,9 +6,19 @@ - [](/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/setup) - [](/developer-guide/snowflake-app-runtime/app-yml)+- [](/developer-guide/snowflake-app-runtime/migrate-to-app-yml) - [](/developer-guide/snowflake-cli/project-definitions/specify-entities) -The `snowflake.yml` project definition tells the Snowflake CLI **where and how-to deploy** your app. This page documents the schema for a Snowflake App Runtime-project, where the entity is `type: snowflake-app`.+This page documents the older Snowflake App Runtime layout: a `snowflake.yml`+with a `type: snowflake-app` entity, plus a build-only `app.yml` for install,+build, and run. Current projects use a single+[`app.yml`](/developer-guide/snowflake-app-runtime/app-yml). To move an existing+project, see [](/developer-guide/snowflake-app-runtime/migrate-to-app-yml).++Native App projects still use `snowflake.yml`. That schema is documented with+[snow app commands](/developer-guide/snowflake-cli/command-reference/native-apps-commands/overview),+not here.++If the project root contains an `app.yml` with `version: 2`, the CLI ignores+this `snowflake.yml` for the Snowflake App Runtime flow. A `snowflake.yml` is a Snowflake CLI project definition. For entity keys,@@ -18,11 +26,10 @@ project files, see [Specify entities](/developer-guide/snowflake-cli/project-definitions/specify-entities).-The rest of this page covers only the Snowflake App Runtime specifics.--`snowflake.yml` is separate from the optional-[`app.yml`](/developer-guide/snowflake-app-runtime/app-yml) build manifest.-`snowflake.yml` controls deployment (destination, code storage, warehouse, and-compute). `app.yml` controls the remote build (install, build, run, artifacts,-and display profile).+The rest of this page covers only the Snowflake App Runtime `snowflake-app`+entity.++In this layout, `snowflake.yml` controls deployment (destination, code storage,+warehouse, and compute). The build-only `app.yml` controls the remote build+(install, build, run, artifacts, and display `profile`). <a id="label-snowflake-yml-example"></a>
Cortex Agents のデータリネージュが追加され、エージェントの仕様で参照する semantic view や Cortex Search service からエージェントまでの依存関係を追跡できるようになりました。関係は CREATE AGENT または ALTER AGENT ... COMMIT VERSION 実行時に記録・更新され、列レベルのリネージュには非対応、エージェントより下流のオブジェクトや OBJECT_DEPENDENCIES には表示されないなどの制約があります。
影響: エージェントがどのデータに到達できるかをオブジェクト単位で確認できますが、既存エージェントは新しいバージョンをコミットするまでリネージュに現れず、参照解決不可のオブジェクトも対象外です。
変更内容: 本文を更新（32行追加・0行削除）
--- ahttps://docs.snowflake.com/en/user-guide/ui-snowsight-lineage+++ bhttps://docs.snowflake.com/en/user-guide/ui-snowsight-lineage@@ -253,4 +253,23 @@ - [Models](/developer-guide/snowflake-ml/model-registry/overview) +### Lineage for Cortex Agents++Data lineage tracks the objects that a [](/user-guide/snowflake-cortex/cortex-agents) can reach through the tools+declared in its specification, so you can see which data reaches an agent. The agent appears as a downstream consumer+of those objects:++- A [semantic view](/sql-reference/sql/create-semantic-view) that a %cortex-analyst% tool references is upstream of the+ agent.+- A [Cortex Search service](/user-guide/snowflake-cortex/cortex-search/cortex-search-overview) that a Cortex Search+ tool references is upstream of the agent.++Because a semantic view is itself downstream of the tables it references, lineage shows the whole path from a table,+through the semantic view, to the agent.++Snowflake records these relationships when you run [](/sql-reference/sql/create-agent) or+[ALTER AGENT ... COMMIT VERSION](/sql-reference/sql/alter-agent), and reconciles them with the agent's active version+each time you commit a new version. If you remove a tool from the specification, the corresponding relationship is+removed the next time you commit a version.+ <a id="label-lineage-privileges"></a> @@ -330,2 +349,15 @@ - You cannot use the [](/sql-reference/functions/get_lineage-snowflake-core) function to obtain lineage information related to a stored procedure.++- Lineage for Cortex Agents has the following limitations:+ - Relationships are recorded when you create an agent or commit a version. An agent whose most recent version was+ committed before agent lineage was introduced doesn't appear in lineage until you commit a new version.+ - A %cortex-analyst% tool that uses a semantic model file on a stage, rather than a semantic view object, doesn't+ produce a lineage relationship.+ - A tool reference that can't be resolved, because the object doesn't exist or because the role committing the+ version can't access it, is skipped.+ - Agent lineage is tracked at the object level. Column lineage isn't available for agents.+ - An agent is a leaf in the lineage graph. No objects currently appear downstream of an agent.+ - Agent lineage is recorded only in the account that owns the agent. A shared or replicated agent doesn't have+ lineage in other accounts.+ - Agent relationships don't appear in [](/sql-reference/account-usage/object_dependencies).
バージョン履歴の最新エントリが v1.21.1 から v1.21.2（2026年8月）に更新され、ハイライトとして 4種類の新しいチャート、Automation 作成時のローカル／クラウド選択、制限付きセッションスコープの再設計が追加されました。最後の項目は diff からは詳細不明です。 影響: Cortex Code Desktop の最新リリースとして、チャート機能と Automation の実行先選択、セッションスコープ設定の変更点を確認できます。
変更内容: 本文を更新（15行追加・14行削除）
--- ahttps://docs.snowflake.com/en/user-guide/cortex-code/cortex-code-desktop/release-notes/index+++ bhttps://docs.snowflake.com/en/user-guide/cortex-code/cortex-code-desktop/release-notes/index@@ -12,16 +12,17 @@ ## Version history -| Version | Date | Highlights |-| ---------------------------------------------------------------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------ |-| [v1.21.1](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-21-1) | August 2026 | Monthly automation schedules, native HTML report publishing, a right-click menu for chat sessions, and reliability fixes |-| [v1.21.0](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-21-0) | August 2026 | Enterprise MDM enforcement on macOS, more file previews in agent mode, and a fix for repeated SSO sign-in tabs |-| [v1.20.2](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-20-2) | July 2026 | Windows update crash fix, deep-link sharing for skills and plugins, and a Restart menu item |-| [v1.20.0](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-20-0) | July 2026 | Smoother, more reliable chat: preserved drafts, snappier streaming, smoother MCP auto-start, and a memory crash fix |-| [v1.19.1](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-19-1) | July 2026 | Faster and smaller installs and updates, refreshed update UI, subagent inherit model, clone repo, WSL support |-| [v1.19.0](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-19-0) | July 2026 | Token efficiency (tool search + offload), chat threads, dbt enhancements, skills and MCP improvements, security fixes |-| [v1.18.0](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-18-0) | July 2026 | Semantic code search (tgrep), file-changes summary, /compact, tidier chat, Cortex Threads (experimental) |-| [v1.17.0](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-17-0) | June 2026 | Refreshed chat and Plan Mode, clickable file paths, Plugins Catalog, Universal Navigator |-| [v1.16.0](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-16-0) | June 2026 | SSH remote workspaces, Personalization page, reimagined Memory, Brave web search, long-standing fixes |-| [v1.15.1](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-15-1) | May 2026 | Plan Mode pause/resume, dbt Cloud polish, SQL Fix-it button, SSH primitives |-| [v1.15.0](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-15-0) | May 2026 | UX overhaul, Remote-SSH, hierarchical SQL permissions, dbt Cloud Mode, Mermaid diagrams |-| [v1.14.0](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-14-0) | May 2026 | Plugins, App Gallery, chat reliability, security hardening |+| Version | Date | Highlights |+| ---------------------------------------------------------------------------- | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |+| [v1.21.2](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-21-2) | August 2026 | Four new chart types, choosing local or cloud when creating an automation, a redesigned restricted session scope dialog, and a memory leak fix |+| [v1.21.1](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-21-1) | August 2026 | Monthly automation schedules, native HTML report publishing, a right-click menu for chat sessions, and reliability fixes |+| [v1.21.0](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-21-0) | August 2026 | Enterprise MDM enforcement on macOS, more file previews in agent mode, and a fix for repeated SSO sign-in tabs |+| [v1.20.2](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-20-2) | July 2026 | Windows update crash fix, deep-link sharing for skills and plugins, and a Restart menu item |+| [v1.20.0](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-20-0) | July 2026 | Smoother, more reliable chat: preserved drafts, snappier streaming, smoother MCP auto-start, and a memory crash fix |+| [v1.19.1](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-19-1) | July 2026 | Faster and smaller installs and updates, refreshed update UI, subagent inherit model, clone repo, WSL support |+| [v1.19.0](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-19-0) | July 2026 | Token efficiency (tool search + offload), chat threads, dbt enhancements, skills and MCP improvements, security fixes |+| [v1.18.0](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-18-0) | July 2026 | Semantic code search (tgrep), file-changes summary, /compact, tidier chat, Cortex Threads (experimental) |+| [v1.17.0](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-17-0) | June 2026 | Refreshed chat and Plan Mode, clickable file paths, Plugins Catalog, Universal Navigator |+| [v1.16.0](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-16-0) | June 2026 | SSH remote workspaces, Personalization page, reimagined Memory, Brave web search, long-standing fixes |+| [v1.15.1](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-15-1) | May 2026 | Plan Mode pause/resume, dbt Cloud polish, SQL Fix-it button, SSH primitives |+| [v1.15.0](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-15-0) | May 2026 | UX overhaul, Remote-SSH, hierarchical SQL permissions, dbt Cloud Mode, Mermaid diagrams |+| [v1.14.0](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-14-0) | May 2026 | Plugins, App Gallery, chat reliability, security hardening |
2026年8月20日の Cortex Agents — Managed MCP Server では、tools/call の応答が単一の JSON 本文から SSE ストリームへ変更されたことが明記されました。2026年8月12日の Cortex モデル更新では、レガシー状態のモデルについて、既存利用者は各 EOL 日まで継続利用できる一方、未使用のアカウントは新たに利用を開始できない旨が追加され、両項目が一覧の上部へ移動しました。
影響: MCP クライアントの応答処理と、対象モデルを未使用のアカウントで新規採用できない点に影響します。
変更内容: 本文を更新（12行追加・12行削除）
--- ahttps://docs.snowflake.com/en/release-notes/bcr-bundles/un-bundled/unbundled-behavior-changes+++ bhttps://docs.snowflake.com/en/release-notes/bcr-bundles/un-bundled/unbundled-behavior-changes@@ -45,4 +45,16 @@ <tbody> <tr>+ <td>**August 20, 2026**</td>+ <td>Cortex Agents — Managed MCP Server</td>+ <td>[](/release-notes/bcr-bundles/un-bundled/bcr-2405)</td>+ <td>Managed MCP `tools/call` responses changed from a single JSON body to an SSE stream. Spec-compliant clients are unaffected.</td>+ </tr>+ <tr>+ <td>**August 12, 2026**</td>+ <td>Cortex Model Updates for August</td>+ <td>[](/release-notes/bcr-bundles/un-bundled/bcr-august-model-deprecations)</td>+ <td>Listed models enter the legacy state. Accounts that already used a listed model can continue until each model's end-of-life date; accounts that had not used it can't start.</td>+ </tr>+ <tr> <td>**July 24-27, 2026**</td> <td>Billing Entity Deprecation - Account Management SQL and Account View Changes</td>@@ -225,16 +237,4 @@ </tr> <tr>- <td>**August 20, 2026**</td>- <td>Cortex Agents — Managed MCP Server</td>- <td>[](/release-notes/bcr-bundles/un-bundled/bcr-2405)</td>- <td>Managed MCP `tools/call` responses change from a single JSON body to an SSE stream. Spec-compliant clients are unaffected.</td>- </tr>- <tr>- <td>**August 12, 2026**</td>- <td>Cortex Model Updates for August</td>- <td>[](/release-notes/bcr-bundles/un-bundled/bcr-august-model-deprecations)</td>- <td>Listed models enter the legacy state; existing users can continue until each model's end-of-life date.</td>- </tr>- <tr> <td>**August 5, 2026**</td> <td>Snowflake Cortex AI</td>
実行中アプリの Snowflake クエリ方法（owner's rights、caller's rights、caller grants）への案内と、app.yml の database・schema（または named target）による指定方法が追加されました。また、OPERATE 権限の操作例が「upgrade」から「alter」に変更され、ライフサイクル設定の詳細ページへのリンクが追加されています。
影響: app.yml での配置先指定やクエリ権限モデルを確認しやすくなり、OPERATE 権限の利用者は操作内容の記述変更（upgrade から alter）を確認する必要があります。
変更内容: 本文を更新（14行追加・7行削除）
--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-app-runtime/access-control+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-app-runtime/access-control@@ -1,7 +1,8 @@ # Access control for Snowflake App Runtime -Available to all accounts.- - [](/developer-guide/snowflake-app-runtime/getting-started)+- [](/developer-guide/snowflake-app-runtime/query-snowflake)+- [](/developer-guide/snowflake-app-runtime/security)+- [](/developer-guide/snowflake-app-runtime/secure-development) - [](/user-guide/cortex-code/cortex-code-cli) - [](/user-guide/cortex-code/cortex-code-desktop/building-apps)@@ -10,5 +11,7 @@ This topic describes common access control patterns for delegating operations and viewing access on Snowflake App Runtime. For the full list of privileges, see-[](/developer-guide/snowflake-app-runtime/privileges).+[](/developer-guide/snowflake-app-runtime/privileges). For how the running app+queries Snowflake (owner's rights, caller's rights, and caller grants), see+[](/developer-guide/snowflake-app-runtime/query-snowflake). <a id="label-snowflake-app-runtime-access-control-personal-database"></a>@@ -27,5 +30,6 @@ through [account administrator setup](/developer-guide/snowflake-app-runtime/account-admin-setup)-before deploying, or explicitly in your `snowflake.yml` identifier.+before deploying, or explicitly in your [`app.yml`](/developer-guide/snowflake-app-runtime/app-yml)+`database` and `schema` (or a named target). <a id="label-snowflake-app-runtime-access-control-execute-as-role"></a>@@ -80,5 +84,5 @@ ## Share view-only access to a running app -Grant USAGE on the Application Service, plus USAGE on the database and schema+Grant `USAGE` on the Application Service, plus `USAGE` on the database and schema that contain it, to let a role open the app. The service must be in a standard database, not a personal database. In [Cortex Code CLI](/user-guide/cortex-code/cortex-code-cli)@@ -97,5 +101,5 @@ ## Delegate lifecycle control -Grant OPERATE to let a role suspend, resume, upgrade, and configure the+Grant `OPERATE` to let a role suspend, resume, alter, and configure the service without transferring ownership: @@ -104,5 +108,5 @@ ``` -An OPERATE role can run:+An `OPERATE` role can run: ```sql@@ -112,4 +116,7 @@ ALTER APPLICATION SERVICE my_db.my_schema.my_app SET AUTO_SUSPEND_SECS = 900; ```++For what those lifecycle settings do, see+[](/developer-guide/snowflake-app-runtime/scale-and-suspend). <a id="label-snowflake-app-runtime-access-control-delegate-monitoring"></a>
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（9行追加・12行削除）
--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-app-runtime/limitations+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-app-runtime/limitations@@ -1,5 +1,3 @@ # Snowflake App Runtime limitations--Available to all accounts. - [](/developer-guide/snowflake-app-runtime/about-snowflake-app-runtime)@@ -8,6 +6,5 @@ - [](/user-guide/cortex-code/cortex-code-cli) -This topic lists known limitations of Snowflake App Runtime during public-preview.+This topic lists known limitations of Snowflake App Runtime. <a id="label-snowflake-app-runtime-limitations-general"></a>@@ -15,10 +12,11 @@ ## General -- Snowflake App Runtime is in public preview. Features, syntax, and outputs- might change before general availability.+- Snowflake App Runtime is available in Amazon Web Services (AWS), Microsoft+ Azure, and Google Cloud commercial regions. It isn't available in government+ regions. - Snowflake App Runtime isn't available on [trial accounts](/user-guide/admin-trial-account). Use a paid Snowflake account to deploy Application Services.-- During public preview, deployable projects use **Node.js** (typically Next.js).- Support for **Python** is planned.+- Deployable projects use **Node.js** (typically Next.js). Support for+ **Python** is planned. - The `TYPE` of an artifact repository can't be changed after creation. @@ -33,6 +31,6 @@ - When your uploaded source includes an [`app.yml`](/developer-guide/snowflake-app-runtime/app-yml) manifest, Snowflake validates it during the remote build. Invalid YAML,- unsupported `profile.icon` paths, or other manifest errors fail the build- before the service is created or upgraded.+ unsupported `icon` paths, or other manifest errors fail the build+ before the service is created or altered. <a id="label-snowflake-app-runtime-limitations-deployment"></a>@@ -46,6 +44,5 @@ - `UNDROP` isn't supported for Application Services. After a service is dropped, it can't be recovered.-- Transferring ownership of an Application Service isn't supported during- public preview.+- Transferring ownership of an Application Service isn't supported. - Remote builds have a maximum running time after the builder pod becomes ready (containers running). Queueing, scheduling, image pull, and container
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（20行追加・0行削除）
--- ahttps://docs.snowflake.com/en/release-notes/clients-drivers/odbc-2026+++ bhttps://docs.snowflake.com/en/release-notes/clients-drivers/odbc-2026@@ -14,4 +14,24 @@ See [](/developer-guide/odbc/odbc) for documentation.++## Version 4.0.0-rc2 (Sep 1, 2026)++Second public preview release of the ODBC Driver built on the Universal Core. This is a new version line, distributed as a release candidate and downloaded separately from the 3.x driver. See [](/developer-guide/odbc/odbc-universal-core) for installation instructions, the curated list of behavior differences, and migration guidance.++### New features and updates++- Implemented `SQLFreeConnect` (ODBC 2.x) as a thin wrapper around `SQLFreeHandle(SQL_HANDLE_DBC, ...)` for direct-link and ODBC 2.x applications that bypass the Driver Manager.+- Implemented `SQLFreeEnv` (ODBC 2.x) as a thin wrapper around `SQLFreeHandle(SQL_HANDLE_ENV, ...)` for direct-link and ODBC 2.x applications that bypass the Driver Manager.+- Changed `SQLCancel` to cancel through the core operation handle instead of issuing a separate server-side cancel call, so a cancelled statement is aborted server-side by the executing path itself. `SQLCancel` returns as soon as the cancel is signaled rather than waiting for the abort request to be processed; the statement's own call still reports `HY008` and does not return until the abort has been issued.++### Customer-facing bug fixes++- Fixed `SQLColumns` `BUFFER_LENGTH` for `NUMBER`/`DECIMAL` to return precision + 2 (ODBC transfer octet length); query-result `SQLColAttribute` octet/display for `NUMBER` remains 136.+- Fixed `SQLColumns` `COLUMN_SIZE` and `BUFFER_LENGTH` for `VARIANT`/`OBJECT`/`ARRAY` to follow `VARCHAR_AND_BINARY_MAX_SIZE_IN_RESULT` instead of the 128 MB length from `SHOW COLUMNS`.+- Fixed `SQLColumns` `COLUMN_SIZE` and `BUFFER_LENGTH` for unrecognized Snowflake types such as `GEOGRAPHY`/`GEOMETRY` to report the varchar metrics implied by their `SQL_VARCHAR` `DATA_TYPE` instead of `NULL`.+- Fixed `SQLProcedureColumns` `TYPE_NAME` for unsupported types such as `GEOGRAPHY`/`GEOMETRY` to report the Snowflake type name while `DATA_TYPE` remains `SQL_VARCHAR`.+- Fixed `SQLColumns` and `SQLProcedureColumns` `CHAR_OCTET_LENGTH` for unsupported types such as `GEOGRAPHY`/`GEOMETRY` to report a byte length instead of `NULL`, matching the `SQL_VARCHAR` they report as `DATA_TYPE`.+- Fixed `SQLGetTypeInfo` string result columns (`TYPE_NAME`, `LITERAL_PREFIX`/`SUFFIX`, `CREATE_PARAMS`, `LOCAL_TYPE_NAME`) to report `SQL_WVARCHAR` as the IRD concise type, matching `SQLTables`/`SQLColumns`.+- Fixed `SQLGetTypeInfo` `INTERVAL_PRECISION` to report `SQL_SMALLINT` as the IRD concise type, matching the ODBC spec and the reference driver; `NUM_PREC_RADIX` remains `SQL_INTEGER`. ## Version 4.0.0-rc1 (Aug 19, 2026)
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（9行追加・9行削除）
--- ahttps://docs.snowflake.com/en/user-guide/views-semantic/overview+++ bhttps://docs.snowflake.com/en/user-guide/views-semantic/overview@@ -7,5 +7,5 @@ the semantic view enhances data-driven decisions and provides consistent business definitions across enterprise applications. -You can use Semantic Views in [Cortex Analyst](/user-guide/snowflake-cortex/cortex-analyst) and+You can use Semantic Views in [Cortex Agents](/user-guide/snowflake-cortex/cortex-agents) and [query these views](/user-guide/views-semantic/querying) in a SELECT statement. You can also [share Semantic Views](/user-guide/views-semantic/sharing-semantic-views) in [private listings](#label-listings-create), in public listings on the [Snowflake Marketplace](https://app.snowflake.com/_deeplink/marketplace), and in [organizational listings](/user-guide/collaboration/listings/organizational/org-listing-about). @@ -31,5 +31,5 @@ - **For AI applications:** Semantic views improve accuracy by combining LLM reasoning with rule-based definitions. Currently,- [Cortex Analyst](/user-guide/snowflake-cortex/cortex-analyst) reads the information captured in the semantic view+ [Cortex Agents](/user-guide/snowflake-cortex/cortex-agents) reads the information captured in the semantic view definition and generates the SQL against the physical tables directly. - **For business intelligence (BI):** Business users benefit from consistent metrics and dimensions across all tools. They can@@ -84,6 +84,6 @@ You can also upload a [YAML specification](/user-guide/views-semantic/semantic-view-yaml-spec) that defines your semantic view. For information, see [](/user-guide/views-semantic/creating-with-snowsight).-- **Cortex Analyst REST API**: To use a semantic view with %cortex-analyst%, you specify the view in the REST API request. For- information, see [](/user-guide/snowflake-cortex/cortex-analyst/rest-api).+- **Cortex Agents**: To use a semantic view for natural language queries, add it as a tool on an agent. For+ information, see [](/user-guide/snowflake-cortex/cortex-agents-manage#label-snowflake-agents-modify-agents). <a id="label-semantic-views-getting-started"></a>@@ -109,11 +109,11 @@ 4. Use the semantic view in the following ways:- - Use %cortex-analyst% for natural language queries of your semantic view.+ - Use [Cortex Agents](/user-guide/snowflake-cortex/cortex-agents) for natural language queries of your semantic view. - You can use the [Cortex Analyst REST API](/user-guide/snowflake-cortex/cortex-analyst/rest-api) to perform a natural- language query that uses your semantic view.+ Add the semantic view as a tool on an agent. For information, see+ [](/user-guide/snowflake-cortex/cortex-agents-manage#label-snowflake-agents-modify-agents). - If you need to monitor the REST API requests that use your semantic view, see- [](/user-guide/snowflake-cortex/cortex-analyst/admin-observability).+ If you need to monitor the requests that use your semantic view, see+ [](/user-guide/snowflake-cortex/cortex-agents-monitor). - Query the semantic view in a SELECT statement. For information, see [](/user-guide/views-semantic/querying).
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（8行追加・9行削除）
--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-app-runtime/cost+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-app-runtime/cost@@ -1,8 +1,7 @@ # Cost and credit usage for Snowflake App Runtime--Available to all accounts. - [](/developer-guide/snowflake-app-runtime/about-snowflake-app-runtime) - [](/developer-guide/snowflake-app-runtime/observability)+- [](/developer-guide/snowflake-app-runtime/scale-and-suspend) - [](/sql-reference/account-usage/snowflake_app_runtime_compute_history) - [](/sql-reference/account-usage/metering_history)@@ -53,6 +52,6 @@ [Compute pool cost](/developer-guide/snowpark-container-services/accounts-orgs-usage-views#label-compute-pool-cost). -Apps left running while idle still accrue credits. If you deploy an app for-testing or occasional use, suspend it when not needed.+Apps left running while idle still accrue credits. To stop an app you don't+need, see [](/developer-guide/snowflake-app-runtime/scale-and-suspend). <a id="label-snowflake-app-runtime-cost-metering-history"></a>@@ -111,9 +110,7 @@ control cost: -- **Suspend idle apps.** Use- [`ALTER APPLICATION SERVICE ... SUSPEND`](/sql-reference/sql/alter-application-service)- to release compute for apps not in active use. Resume them with- [`ALTER APPLICATION SERVICE ... RESUME`](/sql-reference/sql/alter-application-service)- when needed.+- **Suspend idle apps.** Suspending releases compute for apps not in active+ use. Lowering instance counts doesn't: a running service keeps at least one+ instance. See [](/developer-guide/snowflake-app-runtime/scale-and-suspend). - **Drop unused apps.** Use [`DROP APPLICATION SERVICE`](/sql-reference/sql/drop-application-service)@@ -127,4 +124,6 @@ - [](/developer-guide/snowflake-app-runtime/observability): service state and logs.+- [](/developer-guide/snowflake-app-runtime/scale-and-suspend): instance counts+ and suspend. - [](/sql-reference/account-usage/snowflake_app_runtime_compute_history): hourly App Runtime credit usage view.
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（7行追加・8行削除）
--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/validate+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/validate@@ -1,15 +1,14 @@ # snow app validate--Available to all accounts. - [](/developer-guide/snowflake-app-runtime/about-snowflake-app-runtime) - [](/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/overview)-- [](/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/snowflake-yml)+- [](/developer-guide/snowflake-app-runtime/migrate-to-app-yml) - [](/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/deploy) - [](/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/bundle)+- [](/developer-guide/snowflake-app-runtime/app-yml) Checks that the target database and schema exist and that the project can be-bundled (resolves artifacts from `snowflake.yml`). Run this before deploying to-catch configuration errors early.+bundled. For `app.yml`, pass `--target` when named targets are+declared and `default_target` is unset. ## Syntax@@ -52,5 +51,5 @@ <dd> -(Snowflake App Runtime only) Name of the target (environment) to validate, as declared in the `targets` block of `app.yml` (version 2 or higher). Defaults to `targets.default`.+(Snowflake App Runtime only) Name of the target (environment) declared in the `targets` block of `app.yml`. If you omit `--target`, the CLI uses the top-level `default_target`. Required when `targets` are declared and `default_target` is unset. </dd>@@ -202,5 +201,5 @@ `snow app validate` checks that the configured database and schema, when present, exist and are accessible, then confirms that the project can bundle its-artifacts from `snowflake.yml`. On success, it prints+artifacts from `app.yml`. On success, it prints `Valid Snowflake App Runtime project.` @@ -209,5 +208,5 @@ to catch configuration errors early. For the project file fields that validation reads, see the-[snowflake.yml reference](/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/snowflake-yml).+[app.yml reference](/developer-guide/snowflake-app-runtime/app-yml). ## Examples
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（13行追加・1行削除）
--- ahttps://docs.snowflake.com/en/developer-guide/odbc/odbc-universal-core+++ bhttps://docs.snowflake.com/en/developer-guide/odbc/odbc-universal-core@@ -70,5 +70,5 @@ ### Download -Download the installer from the [Snowflake drivers releases](https://github.com/snowflakedb/drivers/releases) page on GitHub. Preview builds of this driver are tagged `snowflake-odbc/<version>`, and the current version is `4.0.0-rc1`. Each release publishes an installer for every supported platform:+Download the installer from the [Snowflake drivers releases](https://github.com/snowflakedb/drivers/releases) page on GitHub. Preview builds of this driver are tagged `snowflake-odbc/<version>`, and the current version is `4.0.0-rc2`. Each release publishes an installer for every supported platform: - Windows: an `.msi` for `x86_64`, `x86_32`, and `aarch64`.@@ -266,4 +266,16 @@ - **Changed the diagnostic vendor prefix.** ODBC 4.x uses `[Snowflake][Snowflake ODBC Driver]`; ODBC 3.x used `[Snowflake][Support]`. Matches the ODBC requirement for `[vendor][ODBC-component-identifier]`. *(BD#110)* - **Fixed handling of invalid `SQLCancelHandle(SQL_HANDLE_DBC)` call during async or data-at-execution.** ODBC 4.x returns `SQL_ERROR` with SQLSTATE `HY010` (function sequence error); ODBC 3.x returned a no-op `SQL_SUCCESS`. *(BD#111)*+- **Changed when `SQLCancel` returns.** ODBC 4.x cancels through the core operation handle and `SQLCancel` returns as soon as the cancel is signaled; the cancelled statement still reports `HY008` and does not return until the abort has been issued. ODBC 3.x issued a separate server-side cancel call.+- **Implemented `SQLFreeConnect` and `SQLFreeEnv`.** ODBC 4.x exports both as wrappers around `SQLFreeHandle` so direct-link and ODBC 2.x applications that bypass the Driver Manager can free connections and environments. Under iODBC, `SQLGetFunctions` reports both as supported; ODBC 3.x omitted them from the ODBC 3 bitmap. *(BD#127)*++### Catalog functions++- **Fixed `SQLColumns` / `SQLProcedureColumns` `BUFFER_LENGTH` for `NUMBER`/`DECIMAL`.** ODBC 4.x returns precision + 2 (ODBC transfer octet length); ODBC 3.x returned the Snowflake storage width from the precision ladder (for example `16` for `NUMBER(38,0)`). Query-result `SQLColAttribute` octet/display size for `NUMBER` remains 136. *(BD#122)*+- **Fixed `SQLColumns` `COLUMN_SIZE` and `BUFFER_LENGTH` for `VARIANT`/`OBJECT`/`ARRAY`.** ODBC 4.x follows `VARCHAR_AND_BINARY_MAX_SIZE_IN_RESULT`; ODBC 3.x hardcoded 128 MB from `SHOW COLUMNS`. *(BD#130)*+- **Fixed `SQLColumns` `COLUMN_SIZE` and `BUFFER_LENGTH` for unrecognized Snowflake types such as `GEOGRAPHY`/`GEOMETRY`.** ODBC 4.x reports the varchar metrics implied by their `SQL_VARCHAR` `DATA_TYPE` instead of `NULL`.+- **Fixed `SQLProcedureColumns` `TYPE_NAME` for unsupported types such as `GEOGRAPHY`/`GEOMETRY`.** ODBC 4.x reports the Snowflake type name while `DATA_TYPE` remains `SQL_VARCHAR`.+- **Fixed `SQLColumns` and `SQLProcedureColumns` `CHAR_OCTET_LENGTH` for unsupported types such as `GEOGRAPHY`/`GEOMETRY`.** ODBC 4.x reports a byte length instead of `NULL`, matching the `SQL_VARCHAR` they report as `DATA_TYPE`.+- **Fixed `SQLGetTypeInfo` string result columns (`TYPE_NAME`, `LITERAL_PREFIX`/`SUFFIX`, `CREATE_PARAMS`, `LOCAL_TYPE_NAME`).** ODBC 4.x reports `SQL_WVARCHAR` as the IRD concise type, matching `SQLTables`/`SQLColumns`.+- **Fixed `SQLGetTypeInfo` `INTERVAL_PRECISION`.** ODBC 4.x reports `SQL_SMALLINT` as the IRD concise type, matching the ODBC spec; `NUM_PREC_RADIX` remains `SQL_INTEGER`. ### Data type conversion and binding
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（8行追加・5行削除）
--- ahttps://docs.snowflake.com/en/user-guide/external-lineage+++ bhttps://docs.snowflake.com/en/user-guide/external-lineage@@ -1,7 +1,5 @@ # External lineage -Available to all accounts that are Enterprise Edition (or higher).--To inquire about upgrading, please contact [Snowflake Support](https://docs.snowflake.com/user-guide/contacting-support).+This feature requires Enterprise Edition (or higher). To inquire about upgrading, please contact [Snowflake Support](https://docs.snowflake.com/user-guide/contacting-support). - [](/user-guide/ui-snowsight-lineage)@@ -81,4 +79,9 @@ You can select an external object or the line connecting objects to obtain additional information just like you can with native lineage.++You can also query external lineage with SQL. External objects appear in the output of the+[GET_LINEAGE](/sql-reference/functions/get_lineage-snowflake-core) function, and you can retrieve the lineage of an external object by+anchoring the query on it. For more information, see+[Lineage for objects outside Snowflake](/sql-reference/functions/get_lineage-snowflake-core#label-get-lineage-external-objects). <a id="label-external-lineage-privilege"></a>@@ -408,4 +411,6 @@ the object-level lineage is still recorded. +<a id="label-external-lineage-remove"></a>+ ## Send requests to remove lineage @@ -452,6 +457,4 @@ - Every Snowflake object referenced in an event must exist and be visible to the role sending the request, or the event is rejected. See [Access to referenced Snowflake objects](#label-external-lineage-object-access).-- Lineage from external sources doesn't appear in the output of the `GET_LINEAGE` function. The `GET_LINEAGE` function returns native- Snowflake lineage only. - The fully qualified name of a dataset — that is, the input or output — can't exceed 1000 characters. - A single event can't produce more than 15,000 lineage edges. An event produces one edge for each combination of input and output, so an
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（6行追加・7行削除）
--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/teardown+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/teardown@@ -1,10 +1,9 @@ # snow app teardown--Available to all accounts. - [](/developer-guide/snowflake-app-runtime/about-snowflake-app-runtime) - [](/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/overview)-- [](/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/snowflake-yml)+- [](/developer-guide/snowflake-app-runtime/migrate-to-app-yml) - [](/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/deploy)+- [](/developer-guide/snowflake-app-runtime/app-yml) Drops the Application Service and cleans up associated objects (stage or@@ -57,5 +56,5 @@ <dd> -(Snowflake App Runtime only) Name of the target (environment) to tear down, as declared in the `targets` block of `app.yml` (version 2 or higher). Defaults to `targets.default`.+(Snowflake App Runtime only) Name of the target (environment) declared in the `targets` block of `app.yml`. If you omit `--target`, the CLI uses the top-level `default_target`. Required when `targets` are declared and `default_target` is unset. </dd>@@ -210,5 +209,5 @@ - The Application Service (or plain service) named `<database>.<schema>.<app>`.-- Code storage, based on the backend in `snowflake.yml`:+- Code storage, based on the backend in `app.yml`: - **Workspace backend (`code_workspace`)**: Only this app's subdirectory is cleared. The workspace itself is kept, because it can be shared across apps@@ -221,6 +220,6 @@ [`snow app deploy`](/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/deploy) again. -The app's database and schema come from `snowflake.yml`. For those fields, see-the [snowflake.yml reference](/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/snowflake-yml).+The app's database and schema come from `app.yml`. For those fields, see the+[app.yml reference](/developer-guide/snowflake-app-runtime/app-yml). ## Examples
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（8行追加・4行削除）
--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-app-runtime/observability+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-app-runtime/observability@@ -1,5 +1,3 @@ # Observability for Snowflake App Runtime--Available to all accounts. - [](/developer-guide/snowflake-app-runtime/getting-started)@@ -61,5 +59,6 @@ By default, the command returns the 500 most recent log lines for the-Application Service defined in your `snowflake.yml` (`--type log`). Output is+Application Service defined in your `app.yml` (`--type log`). Pass `--target`+when the manifest defines named targets. Output is capped at 100 KB. @@ -143,5 +142,10 @@ receives logs, metrics, and traces emitted by your containers and by Snowflake. For more information, see-[](/developer-guide/logging-tracing/logging-tracing-overview).+[](/developer-guide/logging-tracing/logging-tracing-overview). Treat event table+access as sensitive: anyone with `SELECT` on it can read logs from every+Application Service. Don't log query results, tokens, or secrets. See+[Avoid logging sensitive data](/developer-guide/snowflake-app-runtime/secure-development#label-snowflake-app-runtime-secure-development-logging)+and+[Governing log access](/developer-guide/snowflake-app-runtime/security#label-snowflake-app-runtime-security-observability). ## See also
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（11行追加・0行削除）
--- ahttps://docs.snowflake.com/en/user-guide/views-semantic/creating-with-snowsight+++ bhttps://docs.snowflake.com/en/user-guide/views-semantic/creating-with-snowsight@@ -150,4 +150,5 @@ - `TWBX` - `TDS`+- `TDSX` The file must meet the following constraints:@@ -155,4 +156,5 @@ <blockquote> +- Snowflake Connections Only: The tables in the file must resolve to a direct Snowflake connection. Connections to other databases aren't supported. - File Size: Must be under 250 MB. - No Large Extracts: If using a .twbx file, ensure it does not contain a large extract. If using a .twb file, ensure it does not contain large filters or parameters.@@ -164,4 +166,13 @@ For information about getting a view or workbook from Tableau Online, see [Download Views and Workbooks](https://help.tableau.com/current/pro/desktop/en-us/export.htm).++If a workbook connects to a data source published to Tableau Server or Tableau Cloud rather than embedding its own+connection, the file carries only a server-side reference, so Semantic View Autopilot can't see the Snowflake tables.+Upload the workbook first. Autopilot detects the reference and prompts you for the published data source, which you+download from Tableau as a `TDS` or `TDSX` file and upload as a second file. Only one published data source per workbook+is supported.++Tableau virtual connections, part of Tableau Data Management, aren't supported. Recreate the workbook against a direct+Snowflake connection instead. After you provide the Tableau file to Semantic View Autopilot, autopilot parses it to extract the following metadata:
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（10行追加・0行削除）
--- ahttps://docs.snowflake.com/en/sql-reference/sql/create-external-access-integration+++ bhttps://docs.snowflake.com/en/sql-reference/sql/create-external-access-integration@@ -29,4 +29,5 @@ [ ALLOWED_AUTHENTICATION_SECRETS = { ( <secret_name_1> [, <secret_name_2>, ... ] ) | all | none } ] ENABLED = { TRUE | FALSE }+ [ DATA_CONNECTIVITY_PROXY = <dcp_name> ] [ COMMENT = '<string_literal>' ] ```@@ -102,4 +103,13 @@ For reference information about secrets, refer to [](/sql-reference/sql/create-secret).++</dd>+<dt><code className="samp">DATA_CONNECTIVITY_PROXY = <em>dcp_name</em></code></dt>+<dd>++Associates a [Data Connectivity Proxy](/user-guide/data-connectivity-proxy) object with this integration so that allowed private+destinations are reached through the DCP agent tunnel rather than the public internet or a cloud-provider private endpoint.++For the setup procedure, see [](/user-guide/data-connectivity-proxy-setup). </dd>
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（5行追加・5行削除）
--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/bundle+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/bundle@@ -1,15 +1,15 @@ # snow app bundle--Available to all accounts. - [](/developer-guide/snowflake-app-runtime/about-snowflake-app-runtime) - [](/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/overview)-- [](/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/snowflake-yml)+- [](/developer-guide/snowflake-app-runtime/migrate-to-app-yml) - [](/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/deploy) - [](/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/validate)+- [](/developer-guide/snowflake-app-runtime/app-yml) Copies resolved artifacts into `output/bundle` so you can inspect what a deploy would upload. No Snowflake connection is required because this command operates-entirely locally.+entirely locally. `snow app bundle` doesn't take `--target`; all+targets share one source tree. ## Syntax@@ -70,5 +70,5 @@ deploy. The output directory is `output/bundle` relative to your project root. This is useful for debugging artifact resolution or verifying that your-`snowflake.yml` includes the correct source paths.+`app.yml` `ignore` list and source layout include the correct files. ## Examples
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（7行追加・3行削除）
--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-evaluations+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-evaluations@@ -734,6 +734,8 @@ ##### Versions and model deprecations -A metric version depends on its judge model, so metric versions follow Snowflake model deprecations:-+A metric version depends on its judge model, so metric versions follow Snowflake model deprecations. Snowflake retires models in two stages, **legacy** then **end-of-life**, and a legacy judge model is already restricted:++- **After a judge model's legacy date**, only accounts that used that model before the legacy date can run a metric version that depends on it. If your account had never used the model, a run that resolves to that version fails. This applies to the `v1` default: `claude-4-sonnet` entered the legacy state on August 12, 2026, so accounts with no prior `claude-4-sonnet` usage must pin `v2` or `v3`. For details, see [Cortex Agents models](/user-guide/snowflake-cortex/cortex-agents#label-cortex-agents-models).+- **After a judge model's end-of-life date**, no account can use a metric version that depends on it. - **Unversioned metrics and `auto`** roll forward to the newest supported version when their current version is deprecated. Your evaluations keep running, but scores can shift when the judge model changes. - **Pinned versions** don't roll forward. After the deprecation date, a run that pins a deprecated version fails with an error.@@ -748,5 +750,5 @@ - `name`: The name of the metric.-- (Optional) `model`: The LLM judge that scores this metric, such as `claude-sonnet-4-6`. Custom metrics accept any of the judge models listed in [](#label-agent-evaluation-judge-models). Omitting this key, or setting it to `auto`, uses the model Snowflake selects for your account, which is `claude-4-sonnet` today and rolls forward when that model is deprecated. A model that isn't a supported judge, or that isn't available in your region, fails the run at start with an error.+- (Optional) `model`: The LLM judge that scores this metric, such as `claude-sonnet-4-6`. Custom metrics accept any of the judge models listed in [](#label-agent-evaluation-judge-models). Omitting this key, or setting it to `auto`, uses the model Snowflake selects for your account, which is `claude-4-sonnet` today and rolls forward when that model is deprecated. Because `claude-4-sonnet` is [legacy](/user-guide/snowflake-cortex/cortex-agents#label-cortex-agents-models), an account that never used it before the legacy date can't rely on that default: set `model` explicitly to a supported judge. A model that isn't a supported judge, that your account isn't allowed to use, or that isn't available in your region, fails the run at start with an error. - `score_ranges`: A mapping that defines low, medium, and high-quality score ranges. This mapping uses the keys: - `min_score`: The score range used to identify low-quality results, as a two-element sequence of the inclusive lower bound to exclusive upper bound.@@ -1184,4 +1186,6 @@ The GPT judges let accounts that don't allow Anthropic models, such as Azure-only accounts, still run evaluations. No judge model runs on Google Cloud, so accounts there need `ANY_REGION`. If none of a metric version's models are available to your account, the run fails with an error instead of falling back to another model; select a metric version whose models your account allows. For metric versions, see [](#label-agent-evaluation-metric-versions). +Routing scope isn't the only gate. `claude-4-sonnet`, the `v1` judge, is a [legacy](/user-guide/snowflake-cortex/cortex-agents#label-cortex-agents-models) model: only accounts that used it before its August 12, 2026 legacy date can use it as a judge, and no account can after its end-of-life date. Accounts without that prior usage must use `v2` or `v3`.+ <a id="label-agent-evaluation-limitations"></a>
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（5行追加・5行削除）
--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-skills+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-skills@@ -275,5 +275,5 @@ "spec": { "models": {- "orchestration": "claude-4-sonnet"+ "orchestration": "claude-sonnet-4-6" }, "instructions": {@@ -302,5 +302,5 @@ "spec": { "models": {- "orchestration": "claude-4-sonnet"+ "orchestration": "claude-sonnet-4-6" }, "instructions": {@@ -329,5 +329,5 @@ "spec": { "models": {- "orchestration": "claude-4-sonnet"+ "orchestration": "claude-sonnet-4-6" }, "skills": [@@ -350,5 +350,5 @@ POST /api/v2/cortex/agent:run {- "model": "claude-4-sonnet",+ "model": "claude-sonnet-4-6", "messages": [ { "role": "user", "content": [{ "type": "text", "text": "Forecast Q4 revenue." }] }@@ -415,5 +415,5 @@ "spec": { "models": {- "orchestration": "claude-4-sonnet"+ "orchestration": "claude-sonnet-4-6" }, "instructions": {
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（2行追加・7行削除）
--- ahttps://docs.snowflake.com/en/sql-reference/functions/finetune-create+++ bhttps://docs.snowflake.com/en/sql-reference/functions/finetune-create@@ -73,10 +73,5 @@ A string specifying the base model to fine-tune. This must be one of the following values: -- `'llama3-8b'`-- `'llama3-70b'` - `'llama3.1-8b'`-- `'llama3.1-70b'`-- `'mistral-7b'`-- `'mixtral-8x7b'` For more information see [](#label-cortex-finetune-models).@@ -143,5 +138,5 @@ 'CREATE', 'my_tuned_model',- 'mistral-7b',+ 'llama3.1-8b', 'SELECT prompt, completion FROM train', 'SELECT prompt, completion FROM validation'@@ -155,5 +150,5 @@ 'CREATE', 'my_tuned_model',- 'mistral-7b',+ 'llama3.1-8b', 'SELECT prompt, completion FROM train' );
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（8行追加・0行削除）
--- ahttps://docs.snowflake.com/en/user-guide/security-access-control-privileges+++ bhttps://docs.snowflake.com/en/user-guide/security-access-control-privileges@@ -680,4 +680,12 @@ <td>CREATE DATABASE</td> <td>Enables creating a new [database](/guides-overview-db).</td>+ <td>Must be granted by the ACCOUNTADMIN role.</td>+ </tr>+ <tr>+ <td>CREATE DATA CONNECTIVITY PROXY</td>+ <td>+ Enables creating a [Data Connectivity Proxy](/user-guide/data-connectivity-proxy) object so Snowflake can reach private data+ sources through an outbound agent tunnel.+ </td> <td>Must be granted by the ACCOUNTADMIN role.</td> </tr>
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（6行追加・2行削除）
--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-analyst-evaluations+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-analyst-evaluations@@ -1,3 +1,5 @@ # %cortex-analyst% evaluations++Snowflake recommends transitioning to [Cortex Agents](/user-guide/snowflake-cortex/cortex-agents), which supports every %cortex-analyst% capability with higher answer quality. - [](/user-guide/snowflake-cortex/cortex-analyst)@@ -332,6 +334,8 @@ #### Versions and model deprecations -A metric version depends on its judge model, so metric versions follow Snowflake model deprecations:-+A metric version depends on its judge model, so metric versions follow Snowflake model deprecations. Snowflake retires models in two stages, **legacy** then **end-of-life**, and a legacy judge model is already restricted:++- **After a judge model's legacy date**, only accounts that used that model before the legacy date can run a metric version that depends on it. If your account had never used the model, a run that resolves to that version fails. This applies to the `v1` default: `claude-4-sonnet` entered the legacy state on August 12, 2026, so accounts with no prior `claude-4-sonnet` usage must pin `v2` or `v3`. For details, see [Judge model availability](/user-guide/snowflake-cortex/cortex-agents-evaluations#label-agent-evaluation-judge-models).+- **After a judge model's end-of-life date**, no account can use a metric version that depends on it. - **Unversioned metrics and `auto`** use `v1` today and roll forward to the newest supported version when the current version is deprecated. Evaluations keep running, but scores can shift when the judge model changes. - **Pinned versions** don't roll forward. After the deprecation date, a run that pins a deprecated version fails with an error.
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（4行追加・4行削除）
--- ahttps://docs.snowflake.com/en/user-guide/views-semantic/best-practices-dev+++ bhttps://docs.snowflake.com/en/user-guide/views-semantic/best-practices-dev@@ -254,9 +254,9 @@ and in the following ways: -- Directly through the [](/user-guide/snowflake-cortex/cortex-analyst) user interface+- Through [Cortex Agents](/user-guide/snowflake-cortex/cortex-agents) (semantic views must be added to a new or existing+ [agent](/user-guide/snowflake-cortex/cortex-agents-manage#label-snowflake-agents-modify-agents)) - Through [Streamlit](/developer-guide/streamlit/about-streamlit) or other custom applications that use- the Cortex Analyst API or [generate SELECT FROM SEMANTIC_VIEW statements](/user-guide/views-semantic/querying)-- Through Cortex Agents (semantic views must be added to a new or existing- [agent](#label-snowflake-agents-modify-agents))+ the [Cortex Agents REST API](/user-guide/snowflake-cortex/cortex-agents-rest-api) or+ [generate SELECT FROM SEMANTIC_VIEW statements](/user-guide/views-semantic/querying) Except for comments, you can't add or alter tables, columns, or metadata within existing semantic views, so you must recreate them
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（4行追加・4行削除）
--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/events+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/events@@ -1,5 +1,3 @@ # snow app events--Available to all accounts. - [](/developer-guide/snowflake-app-runtime/about-snowflake-app-runtime)@@ -7,4 +5,6 @@ - [](/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/deploy) - [](/developer-guide/snowflake-app-runtime/observability)+- [](/developer-guide/snowflake-app-runtime/app-yml)+- [](/developer-guide/snowflake-app-runtime/migrate-to-app-yml) Fetches observability data from the Application Service. Use `--type` to select one of three telemetry streams:@@ -175,5 +175,5 @@ <dd> -(Snowflake App Runtime only) Name of the target (environment) to query events for, as declared in the `targets` block of `app.yml` (version 2 or higher). Defaults to `targets.default`.+(Snowflake App Runtime only) Name of the target (environment) declared in the `targets` block of `app.yml`. If you omit `--target`, the CLI uses the top-level `default_target`. Required when `targets` are declared and `default_target` is unset. </dd>@@ -193,5 +193,5 @@ <dd> -(Snowflake App Runtime only) The ID of the snowflake-app entity on which to operate. Required if multiple snowflake-app entities exist.+(Legacy `snowflake.yml` only) The ID of the snowflake-app entity on which to operate. Required if multiple snowflake-app entities exist. For `app.yml`, use `--target` instead. </dd>
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（4行追加・4行削除）
--- ahttps://docs.snowflake.com/en/sql-reference/functions/agent_run-snowflake-cortex+++ bhttps://docs.snowflake.com/en/sql-reference/functions/agent_run-snowflake-cortex@@ -248,5 +248,5 @@ A non-streaming response is always returned. -You can run the agent asynchronously by setting `"background": true` in the request body. When you do:+You can run the agent asynchronously by setting `"background": true` in the request body. Background runs are generally available on AWS and Azure. When you do: - A `thread_id` is required in the request body.@@ -291,5 +291,5 @@ ], "models": {- "orchestration": "claude-4-sonnet"+ "orchestration": "claude-sonnet-4-6" } }$$@@ -319,5 +319,5 @@ "uncached": 67 },- "model_name": "claude-4-sonnet",+ "model_name": "claude-sonnet-4-6", "output_tokens": { "total": 38@@ -350,5 +350,5 @@ ], "models": {- "orchestration": "claude-4-sonnet"+ "orchestration": "claude-sonnet-4-6" } }$$,
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（7行追加・0行削除）
--- ahttps://docs.snowflake.com/en/sql-reference/functions/ai_complete-prompt-object+++ bhttps://docs.snowflake.com/en/sql-reference/functions/ai_complete-prompt-object@@ -80,4 +80,11 @@ </div> +Model availability changes over time. A model in the+[legacy](/user-guide/snowflake-cortex/aisql-regional-availability#label-cortex-model-lifecycle)+state can only be used by accounts that used it before its legacy date, and a model past its+end-of-life date can't be used by any account. Run+[SHOW CORTEX BASE MODELS](/sql-reference/sql/show-cortex-base-models) to see which models are+currently available to your account and their lifecycle status.+ For image inputs, you can use one of the following models:
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（7行追加・0行削除）
--- ahttps://docs.snowflake.com/en/user-guide/object-tagging/propagation+++ bhttps://docs.snowflake.com/en/user-guide/object-tagging/propagation@@ -5,4 +5,5 @@ - [](/user-guide/object-tagging/introduction)+- [](/user-guide/object-tagging/snowflake-provided-tags) Tag propagation automatically assigns an [object tag](/user-guide/object-tagging/introduction) to target objects if it is applied to the@@ -260,4 +261,10 @@ - Materialized views +## Pause future tag propagation++To pause all future automatic tag propagation to an object without removing tags that were already propagated, set+[`SKIP_TAG_PROPAGATION`](/user-guide/object-tagging/snowflake-provided-tags#label-skip-tag-propagation) on the object. This tag+requires Enterprise Edition or higher.+ ## Limitations and considerations
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（6行追加・0行削除）
--- ahttps://docs.snowflake.com/en/sql-reference/snowflake-db+++ bhttps://docs.snowflake.com/en/sql-reference/snowflake-db@@ -129,4 +129,10 @@ </dd>+<dt>TAGS<span className="colon">:</span></dt>+<dd>++Contains [Snowflake-provided tags](/user-guide/object-tagging/snowflake-provided-tags) for common governance use cases.++</dd> <dt>TELEMETRY<span className="colon">:</span></dt> <dd>
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（3行追加・3行削除）
--- ahttps://docs.snowflake.com/en/sql-reference/sql/desc-agent+++ bhttps://docs.snowflake.com/en/sql-reference/sql/desc-agent@@ -107,7 +107,7 @@ <div className="colwidths-auto"> -| Privilege | Object | Notes |-| -------------------------------------------------------- | ------ | ----- |-| Any one of these privileges: OWNERSHIP, USAGE, or MODIFY | Agent | |+| Privilege | Object | Notes |+| ----------------------------------------------------------------- | ------ | ----- |+| Any one of these privileges: OWNERSHIP, USAGE, MODIFY, or MONITOR | Agent | | </div>
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（2行追加・4行削除）
--- ahttps://docs.snowflake.com/en/sql-reference/sql/create-application-service+++ bhttps://docs.snowflake.com/en/sql-reference/sql/create-application-service@@ -1,5 +1,3 @@ # CREATE APPLICATION SERVICE--Available to all accounts. - [](/developer-guide/snowflake-app-runtime/about-snowflake-app-runtime)@@ -74,6 +72,6 @@ be of type `APPLICATION`. -During public preview, you must include `FROM ARTIFACT REPOSITORY`. Omitting-the repository clause isn't supported.+You must include `FROM ARTIFACT REPOSITORY`. Omitting the repository clause+isn't supported. </dd>
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（4行追加・1行削除）
--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents@@ -452,5 +452,8 @@ </div> -Public preview models aren't intended for production workloads. Models marked legacy remain available but have a scheduled end-of-life date; run [SHOW CORTEX BASE MODELS](/sql-reference/sql/show-cortex-base-models) to see legacy and end-of-life dates, and switch to a newer model before then.+Public preview models aren't intended for production workloads. After a model's legacy date, only+accounts that already used the model can continue to call it until end-of-life; accounts that had+not used it can't start. Run [SHOW CORTEX BASE MODELS](/sql-reference/sql/show-cortex-base-models)+to see legacy and end-of-life dates, and switch to a newer model before then. ## How it works
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（2行追加・3行削除）
--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/open+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/open@@ -1,5 +1,3 @@ # snow app open--Available to all accounts. - [](/developer-guide/snowflake-app-runtime/about-snowflake-app-runtime)@@ -7,4 +5,5 @@ - [](/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/deploy) - [](/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/events)+- [](/developer-guide/snowflake-app-runtime/app-yml) Opens the deployed Application Service URL in your default browser. Use this@@ -71,5 +70,5 @@ <dd> -(Snowflake App Runtime only) Name of the target (environment) to open, as declared in the `targets` block of `app.yml` (version 2 or higher). Defaults to `targets.default`.+(Snowflake App Runtime only) Name of the target (environment) declared in the `targets` block of `app.yml`. If you omit `--target`, the CLI uses the top-level `default_target`. Required when `targets` are declared and `default_target` is unset. </dd>
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（4行追加・0行削除）
--- ahttps://docs.snowflake.com/en/user-guide/network-policies+++ bhttps://docs.snowflake.com/en/user-guide/network-policies@@ -4,4 +4,5 @@ - [](/user-guide/network-rules) - [](/sql-reference/parameters)+- [](/user-guide/data-connectivity-proxy-security) You can use network policies to control *inbound* access to the Snowflake service and internal stage.@@ -805,4 +806,7 @@ SCIM, Snowflake OAuth, and External OAuth support integration-level network policies. +You can also set `NETWORK_POLICY` on a [Data Connectivity Proxy](/user-guide/data-connectivity-proxy-security) object to restrict+which source IPs can connect to the DCP control plane.+ A network policy that is activated for a security integration does not restrict access to an internal stage.
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（3行追加・1行削除）
--- ahttps://docs.snowflake.com/en/user-guide/admin-security-privatelink+++ bhttps://docs.snowflake.com/en/user-guide/admin-security-privatelink@@ -7,4 +7,5 @@ - [SnowCD](/user-guide/snowcd) - [](/user-guide/security-disable-public-access-privatelink)+- [](/user-guide/data-connectivity-proxy) <a id="label-what-is-aws-privatelink"></a>@@ -14,5 +15,6 @@ [AWS PrivateLink](https://docs.aws.amazon.com/aws-technical-content/latest/aws-vpc-connectivity-options/aws-privatelink.html) is an AWS service for creating private VPC endpoints that allow direct, secure connectivity between your AWS VPCs and the Snowflake VPC without-traversing the public internet. AWS PrivateLink connectivity supports VPC endpoint services and AWS VPCs that are located in the same or in+traversing the public internet. PrivateLink controls inbound connectivity from your network to Snowflake. To reach private data sources+from Snowflake (outbound), see [](/user-guide/data-connectivity-proxy). AWS PrivateLink connectivity supports VPC endpoint services and AWS VPCs that are located in the same or in different AWS regions. Cross-region connectivity for AWS PrivateLink allows you to use a custom endpoint service to connect a Snowflake account in a region that is different from your AWS VPC region. Cross-region connectivity isn't currently supported for any platform as a service (PaaS)
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（1行追加・3行削除）
--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-app-runtime/privileges+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-app-runtime/privileges@@ -1,5 +1,3 @@ # Snowflake App Runtime privileges--Available to all accounts. - [](/developer-guide/snowflake-app-runtime/getting-started)@@ -90,5 +88,5 @@ completed (or equivalent account defaults and grants). - A deploy role that was selected during that setup (or equivalent privileges).-- A project with a `snowflake.yml` file from `snow app setup`.+- A project with an `app.yml` file. Personal-database deploys don't require administrator setup, but you can't share
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（2行追加・2行削除）
--- ahttps://docs.snowflake.com/en/user-guide/cortex-code/cortex-code-desktop/building-apps+++ bhttps://docs.snowflake.com/en/user-guide/cortex-code/cortex-code-desktop/building-apps@@ -115,5 +115,5 @@ - A complete project with pages, API routes, and a Snowflake data layer - A `lib/snowflake.ts` module providing `querySnowflake` and `querySnowflakeLongRunning` helpers with built-in SPCS OAuth-- A `snowflake.yml` manifest for deployment configuration+- An `app.yml` for deployment and build configuration - Support for both Owner's Rights and Caller's Rights authentication @@ -128,5 +128,5 @@ | **Both** | Some routes use Owner's Rights; others use Caller's Rights. | Apps mixing shared dashboards with personalized views. | -Caller's Rights is available automatically for Application Services. To run a query as the signed-in user, pass `{ callersRights: true }` to your query helper. You don't configure anything in `snowflake.yml`.+Caller's Rights is available automatically for Application Services. To run a query as the signed-in user, pass `{ callersRights: true }` to your query helper. You don't configure anything in `app.yml` for caller's rights. ### Developing locally
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（2行追加・2行削除）
--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-run+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-run@@ -7,5 +7,5 @@ - [](/sql-reference/functions/data_agent_run-snowflake-cortex) -By default, requests to the Cortex Agent REST API time out after 15 minutes. To run longer requests, set the `background` field to `true` in the request body. Background runs time out after 6 hours, and you can reconnect to them with the [Stream Agent Run](#stream-agent-run) endpoint. Background runs are only available when you use threads to manage conversation history.+By default, requests to the Cortex Agent REST API time out after 15 minutes. To run longer requests, set the `background` field to `true` in the request body. Background runs time out after 6 hours, and you can reconnect to them with the [Stream Agent Run](#stream-agent-run) endpoint. Background runs are generally available on AWS and Azure, and they're only available when you use threads to manage conversation history. There are two methods to interact with an Agent:@@ -230,5 +230,5 @@ ```json {- "model": "claude-4-sonnet",+ "model": "claude-sonnet-4-6", "messages": [ {"role":"user", "content": [] }
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（2行追加・2行削除）
--- ahttps://docs.snowflake.com/en/sql-reference/sql/alter-agent+++ bhttps://docs.snowflake.com/en/sql-reference/sql/alter-agent@@ -347,5 +347,5 @@ $$ models:- orchestration: claude-4-sonnet+ orchestration: claude-sonnet-4-6 orchestration:@@ -367,5 +367,5 @@ ```sql ALTER AGENT my_support_agent- MODIFY LIVE VERSION SET SPECIFICATION = '{"models":{"orchestration":"claude-4-sonnet"},"orchestration":{"tool_not_accessible":"accept","budget":{"seconds":45,"tokens":80000}}}';+ MODIFY LIVE VERSION SET SPECIFICATION = '{"models":{"orchestration":"claude-sonnet-4-6"},"orchestration":{"tool_not_accessible":"accept","budget":{"seconds":45,"tokens":80000}}}'; ```
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（4行追加・0行削除）
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/zero-copy/sap-sql/setup-sap-snowflake+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/zero-copy/sap-sql/setup-sap-snowflake@@ -8,4 +8,8 @@ The SAP® Snowflake account provisioned is the Business Critical edition.++SAP® BDC Connect for Snowflake is not available for Snowflake trial accounts. To request a SAP®+Snowflake trial, please contact your SAP account executive, who can submit the request for trial+through SAP's internal process for enterprise trials. As an SAP® administrator, perform the following steps:
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（2行追加・2行削除）
--- ahttps://docs.snowflake.com/en/user-guide/views-semantic/sql+++ bhttps://docs.snowflake.com/en/user-guide/views-semantic/sql@@ -3012,5 +3012,5 @@ This behavior is consistent with [the privileges required to query standard views](#label-views-privileges). -To use a semantic view that you do not own in [Cortex Analyst](/user-guide/snowflake-cortex/cortex-analyst), you must use a+To use a semantic view that you do not own in [Cortex Agents](/user-guide/snowflake-cortex/cortex-agents), you must use a role that has the REFERENCES and SELECT privileges on that view. @@ -3023,5 +3023,5 @@ ``` -If you have a schema containing semantic views that you want to share with %cortex-analyst% users, you can use+If you have a schema containing semantic views that you want to share with Cortex Agents users, you can use [future grants](#label-granting-future-privs-on-schema-objects) to grant the privileges on any semantic view that you create in that schema. For example:
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（1行追加・3行削除）
--- ahttps://docs.snowflake.com/en/sql-reference/sql/show-application-services+++ bhttps://docs.snowflake.com/en/sql-reference/sql/show-application-services@@ -1,5 +1,3 @@ # SHOW APPLICATION SERVICES--Available to all accounts. - [](/developer-guide/snowflake-app-runtime/about-snowflake-app-runtime)@@ -114,5 +112,5 @@ <tr> <td>`compute_pool`</td>- <td>Empty during public preview.</td>+ <td>Empty when the service uses Snowflake-managed compute.</td> </tr> <tr>
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（4行追加・0行削除）
--- ahttps://docs.snowflake.com/en/developer-guide/external-network-access/creating-using-external-network-access+++ bhttps://docs.snowflake.com/en/developer-guide/external-network-access/creating-using-external-network-access@@ -2,4 +2,5 @@ - [](/sql-reference/sql/create-external-access-integration)+- [](/user-guide/data-connectivity-proxy-setup) To enable access to specific external network locations, you create an external access integration that specifies a list of network rules@@ -179,4 +180,7 @@ The integration specifies only those locations and credentials allowed for use by UDFs and procedures that reference the integration. An administrator can also enable or disable the integration to manage access to external locations.++To route traffic to a private data source through Data Connectivity Proxy, set the `DATA_CONNECTIVITY_PROXY` parameter to the DCP object+name when you create the integration. For the setup procedure, see [](/user-guide/data-connectivity-proxy-setup). ### Access control
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（4行追加・0行削除）
--- ahttps://docs.snowflake.com/en/user-guide/private-connectivity-outbound+++ bhttps://docs.snowflake.com/en/user-guide/private-connectivity-outbound@@ -20,8 +20,12 @@ - [](/user-guide/private-manage-endpoints-azure) - [](/user-guide/private-manage-endpoints-gcp)+- [](/user-guide/data-connectivity-proxy) Snowflake features such as external functions and external stages generate outbound network traffic from Snowflake to a cloud platform. For increased security, you can create private endpoints in Snowflake to access the cloud platform by using the platform's private connectivity solution rather than traversing the public Internet. This lets you access cloud platform services privately and securely from Snowflake.++To reach private data sources on your network that aren't accessible through a cloud-provider private endpoint (on-premises, hybrid, or+cross-cloud sources), see [](/user-guide/data-connectivity-proxy). Outbound private connectivity is available for the following Snowflake features:
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（3行追加・1行削除）
--- ahttps://docs.snowflake.com/en/user-guide/object-tagging/introduction+++ bhttps://docs.snowflake.com/en/user-guide/object-tagging/introduction@@ -1,4 +1,5 @@ # Introduction to object tagging +- [](/user-guide/object-tagging/snowflake-provided-tags) - [](/user-guide/object-tagging/multi-value-tags) - [](/user-guide/tag-based-masking-policies)@@ -12,5 +13,6 @@ assigning the tag to a Snowflake object. Snowflake stores the tag and its string value as a key-value pair. The tag must be unique for your schema, and the tag value is always a string. To assign more than one string value to the same tag, use-[](/user-guide/object-tagging/multi-value-tags).+[](/user-guide/object-tagging/multi-value-tags). For common governance use cases, you can assign+[](/user-guide/object-tagging/snowflake-provided-tags) that Snowflake creates in every account. The following are general characteristics of object tagging:
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（4行追加・0行削除）
--- ahttps://docs.snowflake.com/en/developer-guide/external-network-access/creating-using-private-aws+++ bhttps://docs.snowflake.com/en/developer-guide/external-network-access/creating-using-private-aws@@ -7,7 +7,11 @@ - [](/user-guide/private-connectivity-outbound) - [](/user-guide/private-manage-endpoints-aws)+- [](/user-guide/data-connectivity-proxy) You can configure Snowflake for outbound private connectivity to an AWS external service by way of [external network access](/developer-guide/external-network-access/external-network-access-overview).++For data sources behind a firewall that aren't accessible by using AWS PrivateLink (for example, on-premises databases or databases in+non-AWS environments), see [](/user-guide/data-connectivity-proxy). Unlike public connectivity, with private connectivity you must do the following operations:
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（4行追加・0行削除）
--- ahttps://docs.snowflake.com/en/developer-guide/external-network-access/external-network-access-overview+++ bhttps://docs.snowflake.com/en/developer-guide/external-network-access/external-network-access-overview@@ -2,4 +2,5 @@ - [](/sql-reference/sql/create-external-access-integration)+- [](/user-guide/data-connectivity-proxy) You can create secure access to specific network locations external to Snowflake, then use that access from within the handler code for@@ -24,4 +25,7 @@ - [](/developer-guide/external-network-access/creating-using-private-gcp) + For data sources that aren't accessible through a cloud-provider private endpoint (on-premises, cross-cloud, or non-CSP-native+ sources), use [](/user-guide/data-connectivity-proxy).+ ## Get started
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（1行追加・3行削除）
--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-app-runtime/account-admin-setup+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-app-runtime/account-admin-setup@@ -1,5 +1,3 @@ # Account administrator setup for Snowflake App Runtime--Available to all accounts. - [](/developer-guide/snowflake-app-runtime/about-snowflake-app-runtime)@@ -161,3 +159,3 @@ - [](/developer-guide/snowflake-app-runtime/access-control): grant `USAGE`, `OPERATE`, and `MONITOR` on deployed apps - [](/developer-guide/snowflake-app-runtime/security): caller grant restrictions, feature policies, and external access controls-- [](/developer-guide/snowflake-app-runtime/limitations): public preview limits+- [](/developer-guide/snowflake-app-runtime/limitations): known limits
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-app-runtime/security+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-app-runtime/security@@ -1,7 +1,6 @@ # Securing Snowflake App Runtime applications -Available to all accounts.- - [](/developer-guide/snowflake-app-runtime/secure-development)+- [](/developer-guide/snowflake-app-runtime/query-snowflake) - [](/developer-guide/snowflake-app-runtime/access-control) - [](/developer-guide/snowflake-app-runtime/account-admin-setup)
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/user-guide/egress-ip/network-egress+++ bhttps://docs.snowflake.com/en/user-guide/egress-ip/network-egress@@ -23,4 +23,7 @@ - [Snowpark Container Services external access](#label-working-with-services-jobs-egress) and Snowflake Openflow on Snowpark Container Services - [Snowflake Git integration](/developer-guide/git/git-setting-up) with IP-restricted Git servers++When the external resource is on a private network where IP allowlisting isn't feasible (deny-all-inbound environments), use+[](/user-guide/data-connectivity-proxy) instead of stable egress IPs. <a id="label-network-egress-generating-addresses"></a>
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-analyst/analyst-optimization+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-analyst/analyst-optimization@@ -1,3 +1,5 @@ # Optimize an existing semantic view or model with verified queries++Snowflake recommends transitioning to [Cortex Agents](/user-guide/snowflake-cortex/cortex-agents), which supports every %cortex-analyst% capability with higher answer quality. Available to all accounts.
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/sql/desc-application-service+++ bhttps://docs.snowflake.com/en/sql-reference/sql/desc-application-service@@ -1,5 +1,3 @@ # DESCRIBE APPLICATION SERVICE--Available to all accounts. - [](/developer-guide/snowflake-app-runtime/about-snowflake-app-runtime)
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/sql/desc-artifact-repository+++ bhttps://docs.snowflake.com/en/sql-reference/sql/desc-artifact-repository@@ -1,5 +1,3 @@ # DESCRIBE ARTIFACT REPOSITORY--Available to all accounts. - [](/developer-guide/snowflake-app-runtime/about-snowflake-app-runtime)
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/sql/drop-application-service+++ bhttps://docs.snowflake.com/en/sql-reference/sql/drop-application-service@@ -1,5 +1,3 @@ # DROP APPLICATION SERVICE--Available to all accounts. - [](/developer-guide/snowflake-app-runtime/about-snowflake-app-runtime)
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/sql/drop-artifact-repository+++ bhttps://docs.snowflake.com/en/sql-reference/sql/drop-artifact-repository@@ -1,5 +1,3 @@ # DROP ARTIFACT REPOSITORY--Available to all accounts. - [](/developer-guide/snowflake-app-runtime/about-snowflake-app-runtime)
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/sql/show-artifact-repositories+++ bhttps://docs.snowflake.com/en/sql-reference/sql/show-artifact-repositories@@ -1,5 +1,3 @@ # SHOW ARTIFACT REPOSITORIES--Available to all accounts. - [](/developer-guide/snowflake-app-runtime/about-snowflake-app-runtime)
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/account-usage/snowflake_app_runtime_compute_history+++ bhttps://docs.snowflake.com/en/sql-reference/account-usage/snowflake_app_runtime_compute_history@@ -9,6 +9,4 @@ # SNOWFLAKE_APP_RUNTIME_COMPUTE_HISTORY view--Available to all accounts. The SNOWFLAKE_APP_RUNTIME_COMPUTE_HISTORY view in the ACCOUNT_USAGE schema returns
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/user-guide/views-semantic/semantic-models-vs-views+++ bhttps://docs.snowflake.com/en/user-guide/views-semantic/semantic-models-vs-views@@ -3,5 +3,5 @@ - [](/user-guide/views-semantic/overview) - [](/user-guide/views-semantic/yaml-vs-ddl)-- [](/user-guide/snowflake-cortex/cortex-analyst)+- [](/user-guide/snowflake-cortex/cortex-agents) Before semantic views were introduced, the only way to define business semantics for %cortex-analyst% was to
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/zero-copy/about-salesforce-datacloud+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/zero-copy/about-salesforce-datacloud@@ -18,5 +18,5 @@ ## Integration for existing Snowflake customers -The Salesforce Data Cloud Zero-Copy integration is designed for existing Snowflake customers who want to bring Salesforce data products into their Snowflake account. Unlike some partner integrations, there is no greenfield (new account provisioning) path: you use your existing Snowflake account.+The Salesforce Data Cloud Zero-Copy integration is designed for existing Snowflake customers who want to bring Salesforce data products into their Snowflake account. You use your existing Snowflake account to set up the integration. As a Snowflake account administrator, you create a Zerocopy Connector in your account and retrieve an Enrollment ID. You then provide that Enrollment ID to your Salesforce administrator, who creates a Data Share Target in Salesforce Data Cloud to authorize the connection. Once connected, Salesforce administrators can share data products from the Salesforce Data Cloud catalog with your connector, and you can immediately query them in Snowflake.
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-toolsets+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-toolsets@@ -105,5 +105,5 @@ "spec": { "models": {- "orchestration": "claude-4-sonnet"+ "orchestration": "claude-sonnet-4-6" }, "tools": [
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/snowflake-cowork/build-agents+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/snowflake-cowork/build-agents@@ -269,5 +269,5 @@ $$ models:- orchestration: claude-4-sonnet+ orchestration: claude-sonnet-4-6 orchestration:
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/governance-and-availability+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/governance-and-availability@@ -13,4 +13,6 @@ [Model and feature availability](#label-cortex-llm-availability) can vary by region and georegion. Find which models are available where, along with relevant lifecycle and status information to help plan adoption, manage change, and understand whether a feature is available natively in-region or through cross-region inference.+After a model enters the [legacy](/user-guide/snowflake-cortex/aisql-regional-availability#label-cortex-model-lifecycle)+state, only accounts that already used it can continue to call it until end-of-life. ## Cost governance and budgets
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-analyst+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-analyst@@ -1,3 +1,5 @@ # %cortex-analyst%++Snowflake recommends transitioning to [Cortex Agents](/user-guide/snowflake-cortex/cortex-agents), which supports every %cortex-analyst% capability with higher answer quality. This feature is not available in the People's Republic of China.
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-analyst/admin-observability+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-analyst/admin-observability@@ -1,3 +1,5 @@ # %cortex-analyst% administrator monitoring++Snowflake recommends transitioning to [Cortex Agents](/user-guide/snowflake-cortex/cortex-agents), which supports every %cortex-analyst% capability with higher answer quality. To improve the quality of answers provided by %cortex-analyst%, you must continue to refine the semantic model or view.
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-analyst/rest-api+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-analyst/rest-api@@ -1,3 +1,5 @@ # %cortex-analyst% REST API++Snowflake recommends transitioning to [Cortex Agents](/user-guide/snowflake-cortex/cortex-agents), which supports every %cortex-analyst% capability with higher answer quality. - [](/user-guide/snowflake-cortex/cortex-analyst)
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/aisql-privileges-and-access+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/aisql-privileges-and-access@@ -577,5 +577,5 @@ - Access to a model (whether by allowlist or RBAC) does not always mean that it can be used. It may still be subject to- cross-region, deprecation, or other availability constraints. These restrictions can result in error messages that+ cross-region, [legacy or end-of-life](/user-guide/snowflake-cortex/aisql-regional-availability#label-cortex-model-lifecycle), or other availability constraints. These restrictions can result in error messages that seem similar to model access errors. To check which Cortex Base Models are currently available in your account and their lifecycle status, use [SHOW CORTEX BASE MODELS](/sql-reference/sql/show-cortex-base-models).
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-analyst/cortex-analyst-routing-mode+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-analyst/cortex-analyst-routing-mode@@ -1,3 +1,5 @@ # Routing Mode for Cortex Analyst++Snowflake recommends transitioning to [Cortex Agents](/user-guide/snowflake-cortex/cortex-agents), which supports every %cortex-analyst% capability with higher answer quality. Available to all accounts.
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-analyst/tutorials/tutorial-1+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-analyst/tutorials/tutorial-1@@ -1,3 +1,5 @@ # Tutorial: Answer questions about time-series revenue data with Cortex Analyst++Snowflake recommends transitioning to [Cortex Agents](/user-guide/snowflake-cortex/cortex-agents), which supports every %cortex-analyst% capability with higher answer quality. ## Introduction
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/user-guide/views-semantic/verified-query-repository+++ bhttps://docs.snowflake.com/en/user-guide/views-semantic/verified-query-repository@@ -3,5 +3,5 @@ This feature is not available in the People's Republic of China. -- [](/user-guide/snowflake-cortex/cortex-analyst)+- [](/user-guide/snowflake-cortex/cortex-agents) - [](/user-guide/views-semantic/verified-query-suggestions) - [](/user-guide/views-semantic/sql)
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/sql/create-artifact-repository+++ bhttps://docs.snowflake.com/en/sql-reference/sql/create-artifact-repository@@ -1,5 +1,3 @@ # CREATE ARTIFACT REPOSITORY--Available to all accounts. - [](/developer-guide/snowflake-app-runtime/about-snowflake-app-runtime)
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/user-guide/views-semantic/editor+++ bhttps://docs.snowflake.com/en/user-guide/views-semantic/editor@@ -5,5 +5,5 @@ - [](/user-guide/views-semantic/semantic-view-yaml-spec) - [](/user-guide/views-semantic/sql)-- [](/user-guide/snowflake-cortex/cortex-analyst)+- [](/user-guide/snowflake-cortex/cortex-agents) The Semantic View Editor in %sf-web-interface% provides a visual interface for creating and editing
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/user-guide/views-semantic/verified-query-suggestions+++ bhttps://docs.snowflake.com/en/user-guide/views-semantic/verified-query-suggestions@@ -3,5 +3,5 @@ This feature is not available in the People's Republic of China. -- [](/user-guide/snowflake-cortex/cortex-analyst)+- [](/user-guide/snowflake-cortex/cortex-agents) - [](/user-guide/views-semantic/verified-query-repository) - [](/user-guide/views-semantic/sql)
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/user-guide/object-tagging/work+++ bhttps://docs.snowflake.com/en/user-guide/object-tagging/work@@ -2,8 +2,10 @@ - [](/user-guide/object-tagging/introduction)+- [](/user-guide/object-tagging/snowflake-provided-tags) - [](/user-guide/object-tagging/multi-value-tags) - [](/user-guide/object-tagging/monitor) This topic describes how to create a tag and assign it to a Snowflake object. It also contains instructions on how to delete a tag.+To assign a predefined tag that Snowflake creates in every account, see [](/user-guide/object-tagging/snowflake-provided-tags). <a id="label-object-tagging-create-tag-snowsight"></a>
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/sql/alter-artifact-repository+++ bhttps://docs.snowflake.com/en/sql-reference/sql/alter-artifact-repository@@ -1,5 +1,3 @@ # ALTER ARTIFACT REPOSITORY--Available to all accounts. - [](/developer-guide/snowflake-app-runtime/about-snowflake-app-runtime)
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-search/cortex-search-monitor+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-search/cortex-search-monitor@@ -1,5 +1,3 @@ # Monitor Cortex Search requests--Available to all accounts. - [](/user-guide/snowflake-cortex/cortex-search/cortex-search-overview)
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/functions/data_agent_run-snowflake-cortex+++ bhttps://docs.snowflake.com/en/sql-reference/functions/data_agent_run-snowflake-cortex@@ -195,5 +195,5 @@ A non-streaming response is always returned. -You can run the agent asynchronously by setting `"background": true` in the request body. When you do:+You can run the agent asynchronously by setting `"background": true` in the request body. Background runs are generally available on AWS and Azure. When you do: - A `thread_id` is required in the request body.
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/functions/system_get_application_service_logs+++ bhttps://docs.snowflake.com/en/sql-reference/functions/system_get_application_service_logs@@ -1,5 +1,3 @@ # SYSTEM$GET_APPLICATION_SERVICE_LOGS--Available to all accounts. - [](/sql-reference/functions-system)
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/sql/alter-application-service+++ bhttps://docs.snowflake.com/en/sql-reference/sql/alter-application-service@@ -1,5 +1,3 @@ # ALTER APPLICATION SERVICE--Available to all accounts. - [](/developer-guide/snowflake-app-runtime/about-snowflake-app-runtime)
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-mcp-connectors+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-mcp-connectors@@ -417,5 +417,5 @@ }, "models": {- "orchestration": "claude-4-sonnet"+ "orchestration": "claude-sonnet-4-6" }, "mcp_servers": [
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-analyst/cortex-analyst-search-integration+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-analyst/cortex-analyst-search-integration@@ -1,3 +1,5 @@ # Improve literal search to enhance Cortex Analyst responses++Snowflake recommends transitioning to [Cortex Agents](/user-guide/snowflake-cortex/cortex-agents), which supports every %cortex-analyst% capability with higher answer quality. This feature is not available in the People's Republic of China.
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-analyst/suggested-questions-feature+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-analyst/suggested-questions-feature@@ -1,3 +1,5 @@ # Onboarding questions in %cortex-analyst%++Snowflake recommends transitioning to [Cortex Agents](/user-guide/snowflake-cortex/cortex-agents), which supports every %cortex-analyst% capability with higher answer quality. This feature is not available in the People's Republic of China.
| セクション | S | A | B | C | 計 |
|---|---|---|---|---|---|
| Snowflake Cortex (AI & ML) | 1 | 2 | 6 | 14 | 23 |
| User Guide | 0 | 1 | 13 | 6 | 20 |
| Developer Guide | 0 | 2 | 13 | 1 | 16 |
| SQL Commands | 0 | 0 | 6 | 8 | 14 |
| Snowflake CLI | 0 | 0 | 9 | 0 | 9 |
| Release Notes | 2 | 1 | 3 | 0 | 6 |
| SQL Functions | 0 | 0 | 4 | 2 | 6 |
| Cortex Code | 0 | 0 | 2 | 0 | 2 |
| Loading & Unloading Data | 0 | 0 | 1 | 1 | 2 |
| SQL General Reference | 0 | 0 | 1 | 0 | 1 |
| Account Usage | 0 | 0 | 0 | 1 | 1 |