SNOWFLAKE DOCS DIFF
総括は生成されていません（claude CLI が利用できなかった可能性があります）。
（この変更は要約対象外です。diff を参照してください）
変更内容: 追加行に「breaking change」を検出
--- ahttps://docs.snowflake.com/en/release-notes/clients-drivers/dotnet-2026+++ bhttps://docs.snowflake.com/en/release-notes/clients-drivers/dotnet-2026@@ -14,4 +14,33 @@ See [](/developer-guide/dotnet/dotnet-driver) for documentation.++## Version 6.0.0 (August 10, 2026)++### Breaking Changes++- Surface-level connection exceptions occurring in `OpenAsync` and `CloseAsync` are now thrown directly, without wrapping inside `AggregateException`.+- Fault occurring during closing a connection leaves it in `Broken` state now, instead of `Closed`.+- Fault occurring during opening a connection with `OpenAsync` no longer leaves the connection stuck in `Connecting` state. Retry patterns on such failures are now possible without recreating the connection object.++### New features and improvements++- Added `CancellationToken` support to chunk download and parsing pipeline. Query result fetching now respects cancellation during both JSON and Arrow chunk parsing.+- Reduced synchronization context capture in the library, minimizing the risk of deadlock occurrence across different code path executions.+- Replaced NUnit tests with Xunit to modernize and stabilize existing CI/CD setup.+- Improved handling of certificates serial number matching and performance of CRL checkup.+- AWS Workload Identity Federation attestation now defaults to a SigV4-presigned `GetCallerIdentity` request and attestation through the STS `GetWebIdentityToken` path (returning a signed JWT) is available as an opt-in by setting the `SNOWFLAKE_ENABLE_AWS_WIF_OUTBOUND_TOKEN=true` environment variable.+- `OpenAsync` method of `SnowflakeDbConnection` now throws the original exception on failure instead of wrapping it in an `AggregateException`.+- `CloseAsync` now throws the original exception on failure instead of wrapping it in an `AggregateException`.+- Upgraded `AWSSDK.S3` dependency. Now getting object header invokes HEAD s3 call instead of GET.+- Added `AllowNumberOverflowAsString` connection property. When set to `true`, numeric values that exceed the range of `System.Decimal` (or a narrower integer type) are returned as strings from `GetValue()` instead of throwing `OverflowException`.++### Bug fixes++- Fixed non-windows builds with added NativeLibrary items in their transitively built projects that were no longer available to copy to output directory.+- `OpenAsync` method of `SnowflakeDbConnection` now resets its state to `Closed` on failures.+- `CloseAsync` method of `SnowflakeDbConnection` now resets its state to `Closed` on cancellation and `Broken` on failures.+- Fixed session creation token leak when `GetSessionAsync` is cancelled.+- Fixed incorrect DateTime conversion for timestamps preceding Unix epoch (1970-01-01) when fractional seconds are present.+- Fixed an unnecessary second PUT (stage re-resolution) per file during GCS uploads when the server scopes upload credentials with an access token. ## Version 5.7.0 (June 12, 2026)
（この変更は要約対象外です。diff を参照してください）
判定根拠: 追加行に「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@@ -46,4 +46,22 @@ 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.51.0 (2026-08-12)++### New Features++- ML Jobs: `artifact_repositories` now accepts a list of repositories, allowing multiple artifact+ repositories to be specified for a job.+- Registry: Added support for logging and running MLflow 3.x models.++### Bug Fixes++- Registry: Fixed a bug where an MLflow model logged with+ `target_platforms=["SNOWPARK_CONTAINER_SERVICES"]` could drop its pip dependencies, leaving the+ deployed model missing required packages.++### Behavior Changes++### Deprecations ## Version 1.50.0 (2026-08-03)
（この変更は要約対象外です。diff を参照してください）
判定根拠: SQL 構文/コードブロックの増減 (+3/-1)
--- ahttps://docs.snowflake.com/en/developer-guide/declarative-sharing/manifest-reference+++ bhttps://docs.snowflake.com/en/developer-guide/declarative-sharing/manifest-reference@@ -5,4 +5,5 @@ - [](/developer-guide/declarative-sharing/about) - [](/developer-guide/declarative-sharing/package)+- [](/developer-guide/declarative-sharing/workspaces) - [](/developer-guide/declarative-sharing/tutorials/getting-started) - [](/developer-guide/declarative-sharing/app-roles)@@ -25,5 +26,5 @@ roles: # optional app roles referenced by shared objects shared_content: # required shared data and logic (databases, schemas, and objects)-application_content: # optional app logic (for example, notebooks) shared by the app+application_content: # optional app logic (for example, workspaces) shared by the app ``` @@ -48,9 +49,9 @@ ### `roles` field -The `roles` field (list, optional) defines a list of [app roles](/developer-guide/declarative-sharing/app-roles). These roles let app owners to provide access to shared objects in an app — such as schemas, tables, views, and notebooks — to their organization.+The `roles` field (list, optional) defines a list of [app roles](/developer-guide/declarative-sharing/app-roles). These roles let app owners provide access to shared objects in an app, such as schemas, tables, views, and workspaces, to their organization. Each named role can optionally contain a `comment`, which appears as a description when the app owner lists the roles in the application. -These roles are referenced in the manifest by shared objects at the named `notebook`, `schema`, `table`, `view`, `semantic_view`, and `cortex_agent` level. For objects in `shared_content` (schemas, tables, views, semantic views, functions, procedures, and Cortex Agents), the roles you assign must be defined in the top-level `roles` list and must be a subset of the roles assigned to the parent schema (either directly on the schema or inherited from the database). For notebooks in `application_content`, the roles must be defined in the top-level `roles` list but are not tied to a shared schema.+These roles are referenced in the manifest by shared objects at the named `workspace`, `notebook`, `schema`, `table`, `view`, `semantic_view`, and `cortex_agent` level. For objects in `shared_content` (schemas, tables, views, semantic views, functions, procedures, and Cortex Agents), the roles you assign must be defined in the top-level `roles` list and must be a subset of the roles assigned to the parent schema (either directly on the schema or inherited from the database). For workspaces and notebooks in `application_content`, the roles must be defined in the top-level `roles` list but are not tied to a shared schema. - All content in the manifest is accessible to the app owner, the ACCOUNTADMIN, and to roles that are granted [IMPORTED PRIVILEGES](#label-dsna-share-access-to-all-data) to the app.@@ -89,9 +90,9 @@ application_content:- notebooks:- - SALESBOOK:+ workspaces:+ - SALES_WORKSPACE:+ source: sales/ roles: [SALES, MARKETING]- main_file: NOTEBOOK1.ipynb- comment: Sales and marketing notebook+ comment: Sales and marketing workspace ``` @@ -264,7 +265,8 @@ The `application_content` field (list, optional) defines bundled content declaratively shared by the app. -This field includes a single `notebooks` field:--- `application_content.notebooks` (List, required): A list of named [notebooks](/user-guide/ui-snowsight/notebooks).+This field includes the following fields:++- `application_content.notebooks` (List, optional): A list of named [notebooks](/user-guide/ui-snowsight/notebooks).+- `application_content.workspaces` (List, optional): A list of named [workspaces](/developer-guide/declarative-sharing/workspaces). <a id="label-dsna-manifest-fields-application-content-notebooks"></a>@@ -308,4 +310,50 @@ ``` +<a id="label-dsna-manifest-fields-application-content-workspaces"></a>++#### `application_content.workspaces.{named workspace}` field++Each named workspace shares a directory of files and folders with consumers as a read-only+[workspace](/user-guide/ui-snowsight/workspaces). Use a workspace to share+[Snowflake Notebooks in Workspaces](/user-guide/ui-snowsight/notebooks-in-workspaces/notebooks-in-workspaces-overview),+documentation, images, and sample data files together.++Each named workspace supports the following name value pairs:++- `source` (string, required): The path to the directory whose files make up the workspace,+ relative to the root of the package version. The path must not start with a slash (`/`), must end+ with a slash (`/`), and must point to a directory that contains at least one file.+- `comment` (string, optional): A comment describing the workspace.+- `roles` (list, optional): A list of app roles that can access the workspace, for example,+ `[SALES, MARKETING]`. When this field is empty (`[]`) or omitted, then only app owners and roles+ with [granted IMPORTED PRIVILEGES](#label-dsna-share-access-to-all-data) receive access. The+ included roles must be defined in the [top-level roles field](#label-dsna-manifest-roles-top).+ Unlike objects in `shared_content`, a workspace isn't tied to a shared schema, so its roles don't+ need to be a subset of a parent schema's roles.++You can't include `.pdf` files in a workspace. The framework rejects them when you build, commit,+or release the application package, and again when a consumer installs the app.++For more information about sharing a workspace, see [](/developer-guide/declarative-sharing/workspaces).++<a id="label-dsna-manifest-fields-application-content-workspaces-example"></a>++##### `application_content.workspaces` field example++In this example, a single workspace, **ANALYSIS_WORKSPACE**, shares every file in the+*workspace_content/* directory of the package version with the **ANALYST** role.++```yaml+roles:+ - ANALYST++application_content:+ workspaces:+ - ANALYSIS_WORKSPACE:+ source: workspace_content/+ roles: [ANALYST]+ comment: Notebooks and reference material for the shared population data+```+ <a id="label-dsna-manifest-example"></a> @@ -372,15 +420,13 @@ application_content:- notebooks:- - intro_notebook:+ workspaces:+ - INTRO_WORKSPACE:+ source: intro/ roles: [VIEWER, ANALYST]- main_file: INTRO_NB.ipynb comment: "Read-only overview of shared population data."- runtime_environment_version: stable-- - analyst_notebook:++ - ANALYST_WORKSPACE:+ source: analysis/notebooks/ roles: [ANALYST]- main_file: ANALYST_NB.ipynb- comment: "Analysis notebook for detailed population metrics."- runtime_environment_version: stable-```+ comment: "Analysis notebooks for detailed population metrics."+```
（この変更は要約対象外です。diff を参照してください）
判定根拠: SQL 構文/コードブロックの増減 (+9/-0)
--- ahttps://docs.snowflake.com/en/sql-reference/data-types-structured+++ bhttps://docs.snowflake.com/en/sql-reference/data-types-structured@@ -979,4 +979,23 @@ ### Using SQL functions to construct structured ARRAY and OBJECT values +To construct a structured ARRAY or OBJECT value directly, use the following functions:++- [](/sql-reference/functions/array_construct_structured)+- [](/sql-reference/functions/object_construct_keep_null_structured)++For example:++```sql+SELECT ARRAY_CONSTRUCT_STRUCTURED(10, 20, 30);+```++```sql+SELECT OBJECT_CONSTRUCT_KEEP_NULL_STRUCTURED(+ 'oname', 'abc',+ 'created_date', NULL::DATE+);+```++You can also construct a semi-structured ARRAY or OBJECT value and explicitly cast the result to a structured type. The following functions construct semi-structured ARRAY values: @@ -993,5 +1012,5 @@ - [](/sql-reference/functions/to_object) -To construct a structured ARRAY or OBJECT value, use these functions and explicitly cast the return value of the function. For example:+For example: ```sql@@ -1011,7 +1030,10 @@ For details, refer to [](#label-structured-types-casting-semi-object). -You can't pass structured ARRAY, structured OBJECT, or MAP values to these functions. Doing so would result in a structured-type being implicitly cast to a semi-structured type, which isn't allowed, as noted in-[](#label-structured-types-casting-implicit).+You can't pass structured ARRAY, structured OBJECT, or MAP values to the semi-structured construction functions+(for example, [](/sql-reference/functions/array_construct) and [](/sql-reference/functions/object_construct)).+Doing so would result in a structured type being implicitly cast to a semi-structured type, which isn't allowed,+as noted in [](#label-structured-types-casting-implicit). To construct a structured value from structured inputs,+use [](/sql-reference/functions/array_construct_structured) or+[](/sql-reference/functions/object_construct_keep_null_structured) instead. <a id="label-structured-types-constructing-constants"></a>@@ -1044,7 +1066,16 @@ ### Constructing a MAP value -To construct a MAP value, construct a semi-structured OBJECT value, and cast the OBJECT value to a MAP value.--For example, the following statements both produce the MAP value `{'city'->'San Mateo','state'->'CA'}`:+To construct a MAP value directly, use [](/sql-reference/functions/map_construct). For example, the following+statement produces the MAP value `{'city'->'San Mateo','state'->'CA'}`:++```sql+SELECT MAP_CONSTRUCT(+ 'city', 'San Mateo',+ 'state', 'CA'+);+```++You can also construct a semi-structured OBJECT value and cast it to a MAP value. For example, the following+statements both produce the same MAP value: ```sql
（この変更は要約対象外です。diff を参照してください）
判定根拠: SQL 構文/コードブロックの増減 (+2/-0)
--- ahttps://docs.snowflake.com/en/user-guide/cleanrooms/v2/troubleshooting+++ bhttps://docs.snowflake.com/en/user-guide/cleanrooms/v2/troubleshooting@@ -538,2 +538,39 @@ </dd> </dl>++---++<dl className="field-list">+<dt>Error<span className="colon">:</span></dt>+<dd>++`ADD_TEMPLATE_REQUEST` fails with:++```+ML job '<ml_job_name>' has no content_manifest. Re-register the code spec to generate the manifest.+```++</dd>+<dt>Cause<span className="colon">:</span></dt>+<dd>++The code spec was registered before content hash validation was added in the+[June 18, 2026 release](/release-notes/2026/other/2026-06-18-dcr) (Clean Rooms API Version 16.3).+ML Jobs code specs registered before that release don't have content hashes and can't be added to a+collaboration. Your account must be running Clean Rooms API Version 16.3 or later for content+hash validation to be enforced.++</dd>+<dt>Solution<span className="colon">:</span></dt>+<dd>++Re-register the code spec as a new version: change the `version` field (for example, from `v1`+to `v2`) and call `REGISTER_CODE_SPEC` again with the same YAML. Re-registration computes+content hashes automatically. Then update the `code_specs` reference in your template to use+the new version and resubmit for approval.++ML Jobs code specs that were already linked to a collaboration before June 18, 2026 continue to work+without re-registration.++</dd>+</dl>
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（96行追加・93行削除）
--- ahttps://docs.snowflake.com/en/sql-reference/functions-semistructured+++ bhttps://docs.snowflake.com/en/sql-reference/functions-semistructured@@ -21,95 +21,98 @@ - Determining the data type for values in semi-structured data (i.e. type predicates). -| Sub-category | Function | Notes |-| ------------------------------------------ | ------------------------------------------------------- | ------------------------------------------------------------------------ |-| **JSON and XML Parsing** | [](/sql-reference/functions/check_json) | |-| | [](/sql-reference/functions/check_xml) | |-| | [](/sql-reference/functions/json_extract_path_text) | |-| | [](/sql-reference/functions/parse_json) | |-| | [](/sql-reference/functions/parse_xml) | |-| | [](/sql-reference/functions/strip_null_value) | |-| **Array/Object Creation and Manipulation** | [](/sql-reference/functions/array_agg) | See also [](/sql-reference/functions-aggregation). |-| | [](/sql-reference/functions/array_append) | |-| | [](/sql-reference/functions/array_cat) | |-| | [](/sql-reference/functions/array_compact) | |-| | [](/sql-reference/functions/array_construct) | |-| | [](/sql-reference/functions/array_construct_compact) | |-| | [](/sql-reference/functions/array_contains) | |-| | [](/sql-reference/functions/array_distinct) | |-| | [](/sql-reference/functions/array_except) | |-| | [](/sql-reference/functions/array_flatten) | |-| | [](/sql-reference/functions/array_generate_range) | |-| | [](/sql-reference/functions/array_insert) | |-| | [](/sql-reference/functions/array_intersection) | |-| | [](/sql-reference/functions/array_max) | |-| | [](/sql-reference/functions/array_min) | |-| | [](/sql-reference/functions/array_position) | |-| | [](/sql-reference/functions/array_prepend) | |-| | [](/sql-reference/functions/array_remove) | |-| | [](/sql-reference/functions/array_remove_at) | |-| | [](/sql-reference/functions/array_repeat) | |-| | [](/sql-reference/functions/array_reverse) | |-| | [](/sql-reference/functions/array_size) | |-| | [](/sql-reference/functions/array_slice) | |-| | [](/sql-reference/functions/array_sort) | |-| | [](/sql-reference/functions/array_to_string) | |-| | [](/sql-reference/functions/array_union_agg) | See also [](/sql-reference/functions-aggregation). |-| | [](/sql-reference/functions/array_unique_agg) | See also [](/sql-reference/functions-aggregation). |-| | [](/sql-reference/functions/arrays_overlap) | |-| | [](/sql-reference/functions/arrays_to_object) | |-| | [](/sql-reference/functions/arrays_zip) | |-| | [](/sql-reference/functions/object_agg) | See also [](/sql-reference/functions-aggregation). |-| | [](/sql-reference/functions/object_construct) | |-| | [](/sql-reference/functions/object_construct_keep_null) | |-| | [](/sql-reference/functions/object_delete) | |-| | [](/sql-reference/functions/object_insert) | ... (truncated)
差分が長いため、途中まで表示しています。
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（52行追加・115行削除）
--- ahttps://docs.snowflake.com/en/user-guide/budgets/per-user-quotas+++ bhttps://docs.snowflake.com/en/user-guide/budgets/per-user-quotas@@ -1,4 +1,2 @@-Available to all accounts.- # Per-user quotas @@ -17,5 +15,5 @@ - Apply the quota to all users in your account, or select specific users using tags to represent teams, cost centers, or business units. - Block users automatically when they reach their daily or monthly limit. Blocks are released automatically when the cycle resets or you raise the limit.-- Configure notifications, based on actual or projected spend against the monthly limit, when users approach or exceed their limits.+- Configure notifications, based on actual or projected spend against the monthly or daily limit, when users approach or exceed their limits. - Automate custom enforcement actions with stored procedures triggered at configurable thresholds, and reset affected states at the start of each quota cycle. - Monitor per-user spending, utilization, and enforcement status in Snowsight.@@ -33,6 +31,5 @@ Quotas operate on a monthly cycle aligned to the UTC calendar month. At the start of each new-calendar month, per-user usage counters reset automatically. Custom quota cycles (such as weekly-or custom start dates) are not supported.+calendar month, per-user usage counters reset automatically. ### Monthly and daily limits@@ -58,5 +55,5 @@ [Block users at the limit](#label-per-user-quota-enforcement). - **Custom action**: A stored procedure that you provide runs when a threshold is crossed, letting- you implement custom enforcement such as suspending a warehouse, revoking a role, or writing an+ you implement custom enforcement such as revoking access based on a role, sending customized notifications, or writing an audit record. For more information, see [Configure custom actions](#label-per-user-quota-custom-actions). @@ -100,5 +97,5 @@ used for hard enforcement. - **Projected spend** (default): Triggers when the user's current spending rate, extrapolated- to the end of the UTC calendar month, indicates they are likely to exceed the threshold. This+ to the end of the UTC calendar month or UTC calendar day, indicates they are likely to exceed the threshold. This is proactive and used for early warning and prevention. @@ -122,5 +119,5 @@ A single quota monitors either warehouse compute or AI domains, but not a mix of the two. The units-of measurement differ (credits for warehouse compute versus AI credits for AI domains), so warehouse+of measurement differ (platform credits for warehouse compute versus AI credits for AI domains), so warehouse and AI domains can't be combined in the same quota. @@ -206,6 +203,6 @@ ## Limitations and considerations -- Quotas operate on a monthly cycle aligned to the UTC calendar month. Custom cycles are not- supported.+- Quotas operate on a monthly cycle aligned to the UTC calendar month. Custom quota cycles, such as weekly+ or custom start dates, are not supported. - By default, a new quota monitors all users in the account. You can narrow the scope with tags, or exclude specific users.@@ -215,13 +212,10 @@ - Collective spending limits across all users in a quota are not supported. Each user's limit is evaluated independently.-- Quota evaluation depends on usage data freshness. By default, evaluations occur approximately- every 6 hours. Notifications and custom actions may be delayed by up to the evaluation interval.- Quota evaluation is separate from [block enforcement](#label-per-user-quota-enforcement), which- uses its own pipeline that evaluates breaches within minutes.+- Quota evaluation is not real time but occurs within minutes. A slight lag might occur between a user being blocked and the data appearing in Snowsight. - Notifications are sent at most once per threshold per user within a 24-hour period for projected spend thresholds. Actual spend thresholds trigger at most once per cycle. - Each email address used for notifications must be verified. If a user's email is not available, an informational event is logged in the event table. By default events are logged in- `snowflake.telemetry.events`, but you can configure your own event table.+ `snowflake.telemetry.events`, but you can configure your own event table. You can verify a whole email domain using [SYSTEM$VERIFY_DNS_DOMAIN] (/sql-reference/functions/system_verify_dns_domain) The following limitations apply to [block enforcement](#label-per-user-quota-enforcement):@@ -234,9 +228,9 @@ they spend in that short window, which is usually small for interactive use. For example, with a 100-credit limit, a user who reaches 100 and spends 30 more before the block takes effect ends at- 130. A large single request, such as an AI function over a big table, can overshoot more.+ 130. A large single request, such as an AI function over a big table, can overshoot more. This should be considered when defining the quota limit. - Daily and monthly cycles reset at UTC midnight. A user who starts spending near a cycle boundary can consume up to one full limit before the reset and a fresh limit after it.-- Limit and scope changes aren't immediate. Changes can take up to approximately 15 minutes to- propagate before enforcement acts on them, including changes to limits and user scope.+- Limit and scope changes aren't immediate. Quota configuration can take up to approximately 5-10 minutes to+ propagate before enforcement acts on them, including changes to limits and scope. <a id="label-per-user-quota-create"></a>@@ -407,16 +401,16 @@ Enforcement runs in a Snowflake-managed pipeline that evaluates breaches within minutes of a spend-event, which is significantly faster than the quota measurement task used for notifications and-custom actions. Enforcement runs in Snowflake's infrastructure, so it doesn't consume credits in-your account.+event. To enable block enforcement: ```sql-CALL my_quota!SET_BLOCK_ENFORCEMENT_ENABLED(TRUE);-```--To disable it, pass `FALSE`. When you disable enforcement, users that this quota has blocked are-automatically unblocked within approximately 15 minutes.+CALL my_quota!SET_BLOCK_ENFORCEMENT_ENABLED(TRUE, TRUE);+```++To disable it, pass `FALSE` in the first argument. When you disable enforcement, users that this quota has blocked are+automatically unblocked within approximately 5-10 minutes.++The second argument determines whether end users should receive notifications once they're blocked. To disable end user notifications when they're blocked, set it to 'FALSE'. ### Enforceable domains@@ -441,8 +435,6 @@ 2. **Evaluation**: The enforcement pipeline compares each user's spend against their per-user limit. If spend meets or exceeds the limit, the pipeline records a block.-3. **Notification**: The blocked user receives an email explaining that their quota is exhausted- and that new AI requests are denied until the cycle resets or the admin raises their limit. The- admin is notified separately through the regular quota measurement task, which runs on a slower- cadence.+3. **Notification**: When quota block enforcement is active and configured to notify end users upon being blocked, an email is sent to the affected user. This notification explains that their quota has been exhausted, resulting in the denial of subsequent AI requests until the limit is increased by an administrator or the cycle resets. The+ admin is notified separately through the regular quota measurement task soon thereafter. 4. **Deny**: The next time the user issues an AI request, the service returns a domain-appropriate error that identifies the cause (quota exhausted) rather than a generic authorization failure.@@ -459,5 +451,5 @@ ```sql-CALL my_quota!GET_ACTIVE_BLOCKS();+CALL my_quota!GET_ACTIVE_BLOCKS_V2(); ``` @@ -473,6 +465,8 @@ [Monitor per-user quotas in Snowsight](#label-per-us... (truncated)
差分が長いため、途中まで表示しています。
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（54行追加・0行削除）
--- ahttps://docs.snowflake.com/en/developer-guide/declarative-sharing/limitations+++ bhttps://docs.snowflake.com/en/developer-guide/declarative-sharing/limitations@@ -29,4 +29,5 @@ Declarative sharing supports these object types: +- **Workspaces** - **Notebooks** - **Tables**, including:@@ -64,4 +65,57 @@ </dl> +<a id="label-dsna-workspace-limitations"></a>++## Workspace limitations++<dl>+<dt>Notebook service scope</dt>+<dd>++To run a notebook in a shared workspace, a consumer needs a+[Snowflake-managed notebook service](/user-guide/ui-snowsight/notebooks-in-workspaces/notebooks-in-workspaces-compute-setup)+in their own account. That service is scoped to a single application instance. It can't be used by+workspaces that aren't bound to an app, or by workspaces in a different app instance.++</dd>+<dt>PDF files</dt>+<dd>++You can't include `.pdf` files in a workspace. The framework rejects them when you build, commit,+or release the application package, and again when a consumer installs the app.++</dd>+<dt>Read-only for consumers</dt>+<dd>++Consumers can't edit, rename, or delete files in a shared workspace, and they can't add files to+it. They also can't copy files out of a shared workspace into their own workspaces.++</dd>+<dt>Source directory</dt>+<dd>++The `source` path must be a directory that contains at least one file. It must end with a slash+(`/`) and must not start with one. You can't point a workspace at an individual file.++</dd>+<dt>Network access</dt>+<dd>++Notebooks in a shared workspace can't access external endpoints or consumer data when running in+consumer accounts. They run with+[restricted caller's rights](/developer-guide/restricted-callers-rights) and can only reach objects+the app shares.++</dd>+<dt>Re-sharing</dt>+<dd>++Consumers can't share a workspace from an app outside their organization, or share individual files+in the workspace. Access follows the app roles assigned to the workspace.++</dd>+</dl>+ <a id="label-dsna-notebook-limitations"></a>
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（41行追加・0行削除）
--- ahttps://docs.snowflake.com/en/release-notes/clients-drivers/snowapi-python-2026+++ bhttps://docs.snowflake.com/en/release-notes/clients-drivers/snowapi-python-2026@@ -12,4 +12,45 @@ See [](/developer-guide/snowflake-python-api/snowflake-python-overview) for documentation.++## Version 1.13.1 (Aug 12, 2026)++### New features and updates++- **Code Bundle API:**+ - Added typed `BundleSpec` and `CodeBundleSpecification` models for code bundles and code bundle executions.+ - Added `iter()` support for code bundle executions.+- **Dynamic Table API:**+ - Added `initialization_warehouse`, `frozen_where`, `backfill_from`, `default_ddl_collation`, `log_level`, `row_timestamp`, `cluster_by_raw`, and `start_at` fields to `DynamicTable`.+ - Added `DataMetricSchedule`, `DataMetricCronSchedule`, `DataMetricMinutesSchedule`, and `DataMetricTriggerOnChangesSchedule` models for data metric scheduling.+ - Extended `refresh_mode` with `ADAPTIVE` and `CUSTOM_INCREMENTAL` values.++### Bug fixes++- None.++## Version 1.13.0 (Aug 10, 2026)++### New features and updates++- **Task and DAG APIs:**+ - Added `condition` parameter to `DAG` to support setting a WHEN condition on the root task.+ - Added the `recursive` argument to `TaskResource.fetch_task_dependents`.+ - Added support for defining task schedules and target completion intervals at a granularity of seconds, including intervals under a minute.+ - Added `overlap_policy` on `Task` and on the `DAG` root task.+ - Added `success_integration` and `execute_as_user` on `Task` and `DAGTask`.+- **Code Bundle API:**+ - Added support for managing code bundles through `root.databases[<db>].schemas[<schema>].code_bundles` (create, iterate, fetch, add a version, execute, and drop).+ - Added support for code bundle executions through `root.code_bundle_execution` (execute a code bundle from a stage location, and fetch the status of or cancel an execution).+ - Added the `_SNOWFLAKE_SKIP_ASYNC_EXEC_POLLING` environment variable. When set to `true`, a request submitted with `asyncExec=true` that receives a `202 Accepted` response returns that accepted response (carrying the job id) immediately, instead of polling the execution to completion. Transient-error retries, for example, 429/503/504, are unaffected.++### Bug fixes++- `copy.copy`, `copy.deepcopy`, and pickling of `IntervalSchedule` and `TargetCompletionInterval` now work; previously they would raise an exception.+- **Security improvements** - for more information, see [CVE-2025-24793](https://www.cve.org/CVERecord?id=CVE-2026-19594):+ - Improved validation of path parameters; values consisting solely of dot-segments (`.` or `..`) now raise a clear `ValueError`.+ - Improved encoding of URL query parameters; resource names containing special characters, such as `&`, `=`, or `#`, are now percent-encoded correctly, preventing failures on rename, swap, and clone operations for resources whose names include such characters.+ - Fixed `DagRun._repr_html_()` to correctly escape special characters in property values.+ - Improved validation of single-quoted string literals used in stage paths; strings with unescaped embedded quotes are no longer incorrectly treated as valid.+ - Improved sanitization of stage path values; backslash sequences immediately preceding a single quote are now doubled. ## Version 1.12.1 (Jun 10, 2026)
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（28行追加・2行削除）
--- ahttps://docs.snowflake.com/en/user-guide/cleanrooms/ml-jobs+++ bhttps://docs.snowflake.com/en/user-guide/cleanrooms/ml-jobs@@ -121,5 +121,5 @@ entrypoint: train.py stage_code_dir: '@my_db.public.ml_stage/ml_project'- image_tag: "2.5.0"+ image_tag: "2.8.1" pip_requirements: - pandas@@ -128,4 +128,10 @@ $$); ```++The `image_tag` field is optional. If you omit it, the collaboration uses the current default+runtime image. The default may change across Snowflake Data Clean Rooms API releases. To ensure your code spec always runs+against the same set of pre-installed libraries and runtime behavior, pin `image_tag` to a+specific version. See [Code specification — ML Jobs](/user-guide/cleanrooms/spec-code-spec#label-dcr-collab-code-spec-ml-jobs)+for the full field reference. For the full field reference, see@@ -167,5 +173,12 @@ ### 5. Update code as needed -As the code evolves, update the ML Jobs code spec and resubmit for approval.+As the code evolves, update the ML Jobs code spec and resubmit for approval. To update a code+spec, change the `version` field and call `REGISTER_CODE_SPEC` again with the updated YAML.+Re-registration recomputes content hashes automatically.++ML Jobs code specs registered before the+[June 18, 2026 release](/release-notes/2026/other/2026-06-18-dcr) (Clean Rooms API Version 16.3)+don't have content hashes and can't be added to a collaboration. For resolution steps, see+[ML Jobs troubleshooting](/user-guide/cleanrooms/v2/troubleshooting#ml-jobs). <a id="label-dcr-ml-jobs-analysis-runner"></a>@@ -341,4 +354,17 @@ For troubleshooting common ML Jobs errors (template call pattern, compute pool issues), see [Troubleshooting Collaboration Data Clean Rooms — ML Jobs](/user-guide/cleanrooms/v2/troubleshooting#ml-jobs).++### Runtime image upgrades and patching++When a collaboration patch runs, the default ML runtime image reflects the current Snowflake Data Clean Rooms API release.+All pinned `image_tag` values are preserved unchanged.++- **Unspecified `image_tag`:** Uses the current default, which updates when Snowflake Data Clean Rooms ships a new+ default image. To trigger a patch, add a template with the code spec to the collaboration.+- **Pinned `image_tag`:** Your pin is always preserved unchanged across patches. Pin `image_tag`+ to run against a stable, known set of libraries.++See [Code specification — ML Jobs](/user-guide/cleanrooms/spec-code-spec#label-dcr-collab-code-spec-ml-jobs)+for the `image_tag` field reference. ### Development workflow
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（14行追加・8行削除）
--- ahttps://docs.snowflake.com/en/user-guide/cleanrooms/spec-code-spec+++ bhttps://docs.snowflake.com/en/user-guide/cleanrooms/spec-code-spec@@ -304,4 +304,9 @@ the code spec after modifying staged files. +ML Jobs code specs registered before the+[June 18, 2026 release](/release-notes/2026/other/2026-06-18-dcr) (Clean Rooms API Version 16.3)+don't have content hashes and can't be added to a collaboration. For resolution steps, see+[ML Jobs troubleshooting](/user-guide/cleanrooms/v2/troubleshooting#ml-jobs).+ </dd> <dt>`pip_requirements` (*Optional*)</dt>@@ -328,10 +333,11 @@ <dd> -The ML runtime image version to use. Maximum 64 characters. If omitted, the collaboration uses a-default image version. Specifying a tag is recommended so that your code spec is pinned to a known set of-pre-installed libraries and runtime behavior. Pinning prevents unexpected changes if the default-image is updated in a future deployment.--For example: `image_tag: "2.5.0"`+The ML runtime image version to use. Maximum 64 characters. If omitted, the collaboration uses the+current default image version (currently `2.8.1`). The default may change across Snowflake Data Clean Rooms API releases.+Pinning `image_tag` to a specific version is recommended so that your code spec runs against a+known set of pre-installed libraries and runtime behavior, and isn't affected when the default+image is updated.++All pinned versions are preserved unchanged across patches. </dd>@@ -351,5 +357,5 @@ entrypoint: train.py stage_code_dir: '@MY_DB.PUBLIC.MY_STAGE/ml_project'- image_tag: "2.5.0"+ image_tag: "2.8.1" pip_requirements: - pandas@@ -359,5 +365,5 @@ entrypoint: score.py stage_code_dir: '@MY_DB.PUBLIC.MY_STAGE/ml_project'- image_tag: "2.5.0"+ image_tag: "2.8.1" pip_requirements: - pandas
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（10行追加・10行削除）
--- ahttps://docs.snowflake.com/en/user-guide/dynamic-tables/custom-incrementalization+++ bhttps://docs.snowflake.com/en/user-guide/dynamic-tables/custom-incrementalization@@ -356,14 +356,14 @@ ### Iceberg base tables and CHANGES() -The following table summarizes `CHANGES()` support when the base table is an %iceberg-tm% table.--| When this applies | `CHANGES(INFORMATION => DEFAULT)` | `CHANGES(INFORMATION => APPEND_ONLY)` |-| --------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- |-| Snowflake-managed %iceberg-tm% V2 base table | Supported. If external engines wrote to the table since the last refresh: supported; unchanged rows appear as delete+insert pairs ([copy-on-write](/user-guide/tables-iceberg-manage#label-iceberg-merge-on-read-behavior)). | Supported. If external engines wrote to the table since the last refresh: unsupported (refresh will fail). |-| Snowflake-managed %iceberg-tm% V3 base table | Supported. | Supported. If external engines wrote to the table since the last refresh: unsupported (refresh will fail). |-| %iceberg-tm% V2 base table with an external catalog | Supported only with `RELY` on the source primary key. | Unsupported. |-| %iceberg-tm% V3 base table with an external catalog | Supported. | Unsupported. |--For the same external-engine write behavior on streams over Snowflake-managed %iceberg-tm% tables, see [Streams limitations](/user-guide/streams-intro#label-stream-limitations).+The following table summarizes `CHANGES()` support when the base table is an Iceberg table.++| When this applies | `CHANGES(INFORMATION => DEFAULT)` | `CHANGES(INFORMATION => APPEND_ONLY)` |+| ---------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- |+| Snowflake-managed Iceberg V2 base table | Supported. If external engines wrote to the table since the last refresh: supported; unchanged rows appear as delete+insert pairs ([copy-on-write](/user-guide/tables-iceberg-manage#label-iceberg-merge-on-read-behavior)). | Supported. If external engines wrote to the table since the last refresh: unsupported (refresh will fail). |+| Snowflake-managed Iceberg V3 base table | Supported. | Supported. If external engines wrote to the table since the last refresh: unsupported (refresh will fail). |+| Iceberg V2 base table with an external catalog | Supported only with `RELY` on the source primary key. | Unsupported. |+| Iceberg V3 base table with an external catalog | Supported. | Unsupported. |++For the same external-engine write behavior on streams over Snowflake-managed Iceberg tables, see [Streams limitations](/user-guide/streams-intro#label-stream-limitations). <a id="label-dynamic-tables-custom-incremental-whats-next"></a>
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（15行追加・0行削除）
--- ahttps://docs.snowflake.com/en/sql-reference/functions-all+++ bhttps://docs.snowflake.com/en/sql-reference/functions-all@@ -290,4 +290,9 @@ </tr> <tr>+ <td>[](/sql-reference/functions/array_construct_structured)</td>+ <td>Returns a [structured ARRAY](/sql-reference/data-types-structured) constructed from one or more inputs, where the element type is the common type of the inputs.</td>+ <td>[](/sql-reference/functions-semistructured)</td>+ </tr>+ <tr> <td>[](/sql-reference/functions/array_contains)</td> <td>Returns TRUE if the specified value is found in the specified array.</td>@@ -2240,4 +2245,9 @@ </tr> <tr>+ <td>[](/sql-reference/functions/map_construct)</td>+ <td>Returns a [MAP](/sql-reference/data-types-structured) constructed from a series of alternating keys and values.</td>+ <td>[](/sql-reference/functions-semistructured)</td>+ </tr>+ <tr> <td>[](/sql-reference/functions/map_contains_key)</td> <td>Determines whether the specified [MAP](/sql-reference/data-types-structured) contains the specified key.</td>@@ -2450,4 +2460,9 @@ </tr> <tr>+ <td>[](/sql-reference/functions/object_construct_keep_null_structured)</td>+ <td>Returns a [structured OBJECT](/sql-reference/data-types-structured) constructed from the arguments that retains key-value pairs with NULL values.</td>+ <td>[](/sql-reference/functions-semistructured)</td>+ </tr>+ <tr> <td>[](/sql-reference/functions/object_delete)</td> <td>Returns an object containing the contents of the input (that is, source) object with one or more keys removed.</td>
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（10行追加・3行削除）
--- ahttps://docs.snowflake.com/en/sql-reference/sql/create-dynamic-table+++ bhttps://docs.snowflake.com/en/sql-reference/sql/create-dynamic-table@@ -123,4 +123,10 @@ Changes to the other dynamic table properties and parameters preserve data. +<a id="label-create-or-alter-dit-syntax"></a>++#### CREATE OR ALTER DYNAMIC ICEBERG TABLE++To create or alter a dynamic Iceberg table, use CREATE OR ALTER DYNAMIC ICEBERG TABLE. It follows the same rules as CREATE OR ALTER DYNAMIC TABLE, with the additional Iceberg-specific limitations in the [CREATE OR ALTER DYNAMIC TABLE usage notes](#label-create-or-alter-dt-usage-notes). For the Iceberg-specific parameters, see [](#label-create-dt-iceberg-syntax).+ <a id="label-create-dt-backup-syntax"></a> @@ -207,5 +213,5 @@ ### CREATE DYNAMIC ICEBERG TABLE -Creates a new dynamic %iceberg-tm% table. For information about Iceberg tables, see+Creates a new dynamic Iceberg table. For information about Iceberg tables, see [](/user-guide/tables-iceberg) and [](/sql-reference/sql/create-iceberg-table-snowflake). @@ -263,5 +269,5 @@ ``` -To clone a dynamic %iceberg-tm% table to a new dynamic Iceberg table, use CREATE DYNAMIC ICEBERG TABLE ... CLONE:+To clone a dynamic Iceberg table to a new dynamic Iceberg table, use CREATE DYNAMIC ICEBERG TABLE ... CLONE: ```sqlsyntax@@ -1134,5 +1140,6 @@ - Adding or changing tags, policies, and data metric functions. Any existing tags, policies, and data metric functions are preserved. To add or modify these, use [ALTER DYNAMIC TABLE](/sql-reference/sql/alter-dynamic-table).-- Creating or altering dynamic %iceberg-tm% tables.+- For a dynamic Iceberg table, changing the Iceberg storage properties EXTERNAL_VOLUME, CATALOG, or BASE_LOCATION of an existing table isn't supported. To change these, use CREATE OR REPLACE DYNAMIC ICEBERG TABLE, or ALTER ICEBERG TABLE.+- Converting a regular dynamic table into a dynamic Iceberg table, or vice versa. - Changing BACKFILL FROM after the dynamic table is created. - Adding START AT after the dynamic table is created.
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（12行追加・0行削除）
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage@@ -241,4 +241,10 @@ </tr> <tr>+ <td>[LISTINGS](/sql-reference/organization-usage/listings)</td>+ <td>Object</td>+ <td>24 hours</td>+ <td>[Premium view](/user-guide/organization-accounts-premium-views) (only available in organization account).</td>+ </tr>+ <tr> <td>[LOAD_HISTORY](/sql-reference/organization-usage/load_history)</td> <td>Historical</td>@@ -543,4 +549,10 @@ <td>[SESSIONS](/sql-reference/organization-usage/sessions)</td> <td>Historical</td>+ <td>24 hours</td>+ <td>[Premium view](/user-guide/organization-accounts-premium-views) (only available in organization account).</td>+ </tr>+ <tr>+ <td>[SHARES](/sql-reference/organization-usage/shares)</td>+ <td>Object</td> <td>24 hours</td> <td>[Premium view](/user-guide/organization-accounts-premium-views) (only available in organization account).</td>
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（4行追加・8行削除）
--- ahttps://docs.snowflake.com/en/release-notes/2026/10_28+++ bhttps://docs.snowflake.com/en/release-notes/2026/10_28@@ -11,13 +11,8 @@ <a id="about-listing-consumers"></a> -# 10.28 Release Notes (no announcements) (Preview)+# 10.28 Release Notes (no announcements): Aug 9, 2026–Aug 12, 2026 -Content on this page is available in advance of the completion of the 10.28 release, which is currently-either *pending* or *in progress* and is scheduled for completion on Aug 12, 2026 (subject to change).--Features, updates, or behavior changes described on this page might not be available in your accounts-until the release is complete.--For updates to these release notes, see [](#label-rel-notes-change-log-10-28).+This release has completed. For differences between the in-advance and final versions of these release+notes, see [](#label-rel-notes-change-log-10-28). This release contains no significant features, updates, or enhancements to announce.@@ -30,2 +25,3 @@ | ------------- | ----------------------------- | ------------ | | Release notes | Initial publication (preview) | Aug 11, 2026 |+| Release notes | Final publication | Aug 13, 2026 |
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（10行追加・0行削除）
--- ahttps://docs.snowflake.com/en/developer-guide/declarative-sharing/about+++ bhttps://docs.snowflake.com/en/developer-guide/declarative-sharing/about@@ -78,4 +78,12 @@ </dd>+<dt>[Workspaces](/developer-guide/declarative-sharing/workspaces)</dt>+<dd>++A directory of files and folders that consumers get as a read-only workspace. Use a workspace to+share [Snowflake Notebooks in Workspaces](/user-guide/ui-snowsight/notebooks-in-workspaces/notebooks-in-workspaces-overview),+documentation, images, and sample data files together.++</dd> <dt>[Notebooks](/user-guide/ui-snowsight/notebooks), [stored procedures](/developer-guide/stored-procedure/stored-procedures-overview), and [user-defined functions](/developer-guide/udf/udf-overview)</dt> <dd>@@ -219,4 +227,5 @@ - [](/developer-guide/declarative-sharing/introduction) - [](/developer-guide/declarative-sharing/package)+- [](/developer-guide/declarative-sharing/workspaces) - [](/developer-guide/declarative-sharing/live-editing) - [](/developer-guide/declarative-sharing/udfs-sprocs)@@ -231,4 +240,5 @@ - [](/developer-guide/declarative-sharing/consumer/install) - [](/developer-guide/declarative-sharing/consumer/access-app-content)+- [](/developer-guide/declarative-sharing/consumer/access-shared-workspace) - [](/developer-guide/declarative-sharing/consumer/consumer-execution) - [](/developer-guide/declarative-sharing/limitations)
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（2行追加・6行削除）
--- ahttps://docs.snowflake.com/en/user-guide/cortex-code/cortex-code-desktop/index+++ bhttps://docs.snowflake.com/en/user-guide/cortex-code/cortex-code-desktop/index@@ -22,5 +22,5 @@ ## Access control requirements -The user's active role must have the following database roles granted to use CoCo Desktop:+The user's active role must have one of the following database roles granted to use CoCo Desktop: <div className="colwidths-given">@@ -38,8 +38,4 @@ <tbody> <tr>- <td>SNOWFLAKE.COPILOT_USER</td>- <td>Required for all users to access CoCo Desktop. Granted to the PUBLIC role by default.</td>- </tr>- <tr> <td>SNOWFLAKE.CORTEX_USER **or** SNOWFLAKE.CORTEX_AGENT_USER</td> <td>At least one of these database roles is required. SNOWFLAKE.CORTEX_AGENT_USER grants access to Cortex Agents and agentic surfaces, including CoCo Desktop and Snowflake Intelligence.</td>@@ -49,5 +45,5 @@ </div> -By default, SNOWFLAKE.COPILOT_USER and SNOWFLAKE.CORTEX_USER are granted to the PUBLIC role,+By default, SNOWFLAKE.CORTEX_USER is granted to the PUBLIC role, so all users in the account have access to CoCo Desktop without additional configuration. SNOWFLAKE.CORTEX_AGENT_USER is not granted to PUBLIC by default and must be explicitly granted
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（4行追加・4行削除）
--- ahttps://docs.snowflake.com/en/user-guide/cortex-code/cortex-code-desktop/onboarding-and-authentication+++ bhttps://docs.snowflake.com/en/user-guide/cortex-code/cortex-code-desktop/onboarding-and-authentication@@ -10,8 +10,8 @@ Before you sign in, confirm your Snowflake role has the required database roles: -To use CoCo Desktop, your Snowflake role must have SNOWFLAKE.COPILOT_USER and either-SNOWFLAKE.CORTEX_USER or SNOWFLAKE.CORTEX_AGENT_USER. By default, SNOWFLAKE.COPILOT_USER and-SNOWFLAKE.CORTEX_USER are available to all users through the PUBLIC role. Administrators can-restrict access by revoking these roles from PUBLIC or by setting per-user daily credit limits.+To use CoCo Desktop, your Snowflake role must have either+SNOWFLAKE.CORTEX_USER or SNOWFLAKE.CORTEX_AGENT_USER. By default,+SNOWFLAKE.CORTEX_USER is available to all users through the PUBLIC role. Administrators can+restrict access by revoking this role from PUBLIC or by setting per-user daily credit limits. See [Access control requirements](/user-guide/cortex-code/cortex-code-desktop/index#label-cortex-code-desktop-access-control) and [Cost controls for CoCo](/user-guide/cortex-code/credit-usage-limit).
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（7行追加・0行削除）
--- ahttps://docs.snowflake.com/en/release-notes/preview-features+++ bhttps://docs.snowflake.com/en/release-notes/preview-features@@ -521,4 +521,11 @@ </tr> <tr>+ <td>Workspace sharing in %declarative-app-short-plural%</td>+ <td>Open</td>+ <td>August 2026</td>+ <td>[](/developer-guide/declarative-sharing/workspaces)</td>+ <td>Share a directory of files and folders, including Snowflake Notebooks in Workspaces, as a read-only workspace in a %declarative-app-short%.</td>+ </tr>+ <tr> <td>SnowConvert AI - ETL Migration</td> <td>Open</td>
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（2行追加・3行削除）
--- ahttps://docs.snowflake.com/en/user-guide/cortex-code/cortex-code-snowsight/cloud-agents+++ bhttps://docs.snowflake.com/en/user-guide/cortex-code/cortex-code-snowsight/cloud-agents@@ -31,6 +31,5 @@ - **No change to existing grants.** Cloud Agents does not modify any of your Snowflake RBAC settings or open up additional SQL access. - **Isolated execution.** Each session runs in its own container.-- **Outbound network is restricted, not disabled.** HTTPS egress is limited to a fixed allowlist of package managers and related build tooling. For the full list, see [Allowed package manager egress](#label-cloud-agents-allowed-package-manager-egress). Access to hosts outside that allowlist requires [external access integrations](/developer-guide/external-network-access/external-network-access-overview) that your Snowflake administrator configures. These integrations use the same primitives as UDFs and stored procedures.-- **Existing secrets model.** If external access is configured, credentials are managed via Snowflake Secrets. The container never has direct access to secret values.+- **Outbound network is restricted, not disabled.** HTTPS egress is limited to a fixed allowlist of package managers and related build tooling. For the full list, see [Allowed package manager egress](#label-cloud-agents-allowed-package-manager-egress). Hosts outside that allowlist are not reachable from the sandbox. [External access integrations](/developer-guide/external-network-access/external-network-access-overview) are not currently supported for Cloud Agents. <a id="label-cloud-agents-allowed-package-manager-egress"></a>@@ -51,5 +50,5 @@ | OS packages | Debian, Ubuntu, and Alpine package mirrors | -Anything outside Snowflake and this allowlist, including arbitrary websites or private registries, isn't reachable unless your administrator configures an external access integration.+Anything outside Snowflake and this allowlist, including arbitrary websites or private registries, isn't reachable from the sandbox. ## Disable non-Snowflake egress (account administrators)
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（3行追加・2行削除）
--- ahttps://docs.snowflake.com/en/user-guide/dynamic-tables/create-iceberg+++ bhttps://docs.snowflake.com/en/user-guide/dynamic-tables/create-iceberg@@ -9,5 +9,5 @@ - [](/user-guide/dynamic-tables/monitoring) -A dynamic Iceberg table stores its output in Apache Iceberg format on Snowflake-managed external storage. It supports the same refresh modes and scheduling as a regular dynamic table, but external engines such as Spark and Trino can also read the data directly.+A dynamic %iceberg-tm% table stores its output in Iceberg format on Snowflake-managed external storage. It supports the same refresh modes and scheduling as a regular dynamic table, but external engines such as Spark and Trino can also read the data directly. For the full syntax reference, see [CREATE DYNAMIC ICEBERG TABLE](/sql-reference/sql/create-dynamic-table#label-create-dt-iceberg-syntax).@@ -97,4 +97,6 @@ regular dynamic tables. +You can also use CREATE OR ALTER to create a dynamic Iceberg table if it doesn't exist or alter an existing one in place. For syntax and limitations, see [CREATE OR ALTER DYNAMIC ICEBERG TABLE](/sql-reference/sql/create-dynamic-table#label-create-or-alter-dit-syntax).+ <a id="label-dynamic-tables-create-iceberg-grants"></a> <a id="label-dynamic-tables-tasks-create-iceberg-grants"></a>@@ -130,5 +132,4 @@ | SNOWFLAKE catalog only | The CATALOG parameter must be `'SNOWFLAKE'`. External catalogs (Snowflake Open Catalog, AWS Glue) are not supported. | | Backup exclusion | Dynamic Iceberg tables are not included in database or schema backups. |-| Create-or-Alter not supported | The CREATE OR ALTER syntax is not supported for dynamic Iceberg tables. Use CREATE OR REPLACE instead. | | Backfill not supported | Using backfill on dynamic Iceberg tables is not supported. |
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（2行追加・2行削除）
--- ahttps://docs.snowflake.com/en/release-notes/clients-drivers/monthly-releases+++ bhttps://docs.snowflake.com/en/release-notes/clients-drivers/monthly-releases@@ -36,6 +36,6 @@ <tr> <td>%dotnet-rn%</td>- <td>TBD</td>- <td>TBD</td>+ <td>6.0.0</td>+ <td>10-Aug-2026</td> <td></td> </tr>
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（4行追加・0行削除）
--- ahttps://docs.snowflake.com/en/developer-guide/declarative-sharing/introduction+++ bhttps://docs.snowflake.com/en/developer-guide/declarative-sharing/introduction@@ -3,4 +3,5 @@ - [](/developer-guide/declarative-sharing/about) - [](/developer-guide/declarative-sharing/package)+- [](/developer-guide/declarative-sharing/workspaces) - [](/developer-guide/declarative-sharing/live-editing) - [](/developer-guide/declarative-sharing/udfs-sprocs)@@ -15,4 +16,5 @@ - [](/developer-guide/declarative-sharing/consumer/install) - [](/developer-guide/declarative-sharing/consumer/access-app-content)+- [](/developer-guide/declarative-sharing/consumer/access-shared-workspace) - [](/developer-guide/declarative-sharing/consumer/consumer-execution) - [](/developer-guide/declarative-sharing/limitations)@@ -48,4 +50,6 @@ - [Semantic views](/user-guide/views-semantic/overview) +- [Workspaces](/developer-guide/declarative-sharing/workspaces), which can include+ [Snowflake Notebooks in Workspaces](/user-guide/ui-snowsight/notebooks-in-workspaces/notebooks-in-workspaces-overview) - [Notebooks](/user-guide/ui-snowsight/notebooks-working) - [Stored procedures](/developer-guide/stored-procedure/stored-procedures-overview)
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-python-api/snowflake-python-managing-tasks+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-python-api/snowflake-python-managing-tasks@@ -245,5 +245,6 @@ When a task's definition is a `StoredProcedureCall` object, the handler of the stored procedure (or function) can explicitly set the-return value of the task by using a `TaskContext` object.+return value of the task by using a `TaskContext` object. To use a `TaskContext` object, you need to add `snowflake.core`+to the list of imported packages by using the `packages` argument of `StoredProcedureCall`, `DAG`, or `DAGTask` object. For more information, see [](/sql-reference/functions/system_set_return_value).
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/functions/object_construct_keep_null+++ bhttps://docs.snowflake.com/en/sql-reference/functions/object_construct_keep_null@@ -17,5 +17,5 @@ <dd> -[](/sql-reference/functions/object_construct)+[](/sql-reference/functions/object_construct) , [](/sql-reference/functions/object_construct_keep_null_structured) </dd>
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/user-guide/dynamic-tables/supported-queries+++ bhttps://docs.snowflake.com/en/user-guide/dynamic-tables/supported-queries@@ -93,5 +93,5 @@ <td> -Base tables, views, Snowflake-managed %iceberg-tm% tables, externally managed %iceberg-tm% tables, Delta Direct tables, and other dynamic tables.+Base tables, views, Snowflake-managed %iceberg-tm% tables, externally managed Iceberg tables, Delta Direct tables, and other dynamic tables. Subqueries outside of FROM clauses (for example, WHERE EXISTS) are not supported.
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/developer-guide/declarative-sharing/package+++ bhttps://docs.snowflake.com/en/developer-guide/declarative-sharing/package@@ -3,4 +3,5 @@ - [](/developer-guide/declarative-sharing/about) - [](/developer-guide/declarative-sharing/introduction)+- [](/developer-guide/declarative-sharing/workspaces) - [](/developer-guide/declarative-sharing/live-editing) - [](/developer-guide/declarative-sharing/udfs-sprocs)@@ -92,4 +93,5 @@ - A [manifest](/developer-guide/declarative-sharing/manifest-reference) file (required): A text-based file that defines the app's structure.+- [Workspace](/developer-guide/declarative-sharing/workspaces) directories (optional): One or more directories of files and folders that consumers get as read-only workspaces. A workspace can contain notebook (`.ipynb`) files, documentation, images, and sample data files. - [Snowflake Notebook](/user-guide/ui-snowsight/notebooks) files (optional): One or more text-based files that can act as a front end to the consumer experience, referencing the shared views and tables. They can also include code, reference visualizations, and include logic to help present the data.
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/functions/object_construct+++ bhttps://docs.snowflake.com/en/sql-reference/functions/object_construct@@ -16,5 +16,5 @@ <dd> -[](/sql-reference/functions/object_construct_keep_null)+[](/sql-reference/functions/object_construct_keep_null) , [](/sql-reference/functions/object_construct_keep_null_structured) </dd>
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/functions/array_construct+++ bhttps://docs.snowflake.com/en/sql-reference/functions/array_construct@@ -18,5 +18,5 @@ <dd> -[](/sql-reference/functions/array_construct_compact)+[](/sql-reference/functions/array_construct_compact) , [](/sql-reference/functions/array_construct_structured) </dd>
| セクション | S | A | B | C | 計 |
|---|---|---|---|---|---|
| Release Notes | 2 | 0 | 4 | 0 | 6 |
| Developer Guide | 0 | 1 | 3 | 2 | 6 |
| User Guide | 0 | 0 | 3 | 1 | 4 |
| SQL General Reference | 0 | 1 | 2 | 0 | 3 |
| Clean Rooms | 0 | 1 | 2 | 0 | 3 |
| Cortex Code | 0 | 0 | 3 | 0 | 3 |
| SQL Functions | 0 | 0 | 0 | 3 | 3 |
| SQL Commands | 0 | 0 | 1 | 0 | 1 |
| Organization Usage | 0 | 0 | 1 | 0 | 1 |