Update dagster-gcp requirement from >=0.24 to >=0.29.11

[dependabot]

Updates the requirements on dagster-gcp to permit the latest version.

Changelog

Sourced from dagster-gcp's changelog.

1.13.11 (core) / 0.29.11 (libraries)

New

• [ui] The asset catalog page now renders as a single virtualized list, so workspaces with many asset groups or code locations no longer freeze the UI when expanding those sections.
• [dagster-dbt] Added a new "insights" option to DbtProjectComponent's include_metadata field, enabling Dagster+ Insights tracking from YAML config.
• [dagster-graphql] Added an optional limit argument and new assetSelectionCount / assetCheckSelectionCount fields to the Run GraphQL type, so clients can render a bounded preview of a run's asset/check selection alongside the true totals.

Bugfixes

• Asset check history is now cleared when an asset or its partitions are wiped; stale entries no longer linger in the Execution History and Partitions views.
• [ui] The run detail page header now displays the asset-check count for asset-job runs, and the count is now read from the execution plan rather than by scanning the full run event log.
• [ui] The "View asset lineage" item in the run actions menu now correctly scopes to the assets in that run.
• [dagster-dbt] .with_insights() now logs a warning instead of raising when called against an unsupported adapter.

Documentation

• Added a new page documenting Dagster+ code-location snapshot size limits, with a script you can run locally to estimate snapshot sizes before deploying.
• Documented the "Run concurrency" Insights metric.
• Fixed an invalid pool config in the "Preventing concurrent dbt snapshots" DbtProjectComponent example.

1.13.10 (core) / 0.29.10 (libraries)

Bugfixes

• Fixed a bug where DagsterInstance.get_latest_materialization_event (and get_asset_records) could return a stale pre-wipe materialization for a wiped asset once a new run targeting the asset started or an observation was reported. In Dagster+, fixed the analogous bug where wiping partitions could leave the wiped partition's materialization as the asset's latest materialization.
• Fixed an issue where an asset backfill could get stuck — emitting no further runs but never completing — when an asset whose partitions definition includes certain dates depended on an asset whose partitions definition excludes them.
• Fixed a performance issue where assets partitioned by a cron schedule using an explicit minute list (e.g. 0,30 * * * *) computed partition counts much more slowly than the equivalent */30 schedule.
• Improved the performance of loading the backfills for a partition set on deployments with a large number of backfills, which previously fetched and deserialized every backfill in the deployment on each request.
• [ui] Fixed a performance regression that caused views with truncated text, such as the asset catalog, to render slowly.
• [dagster-cloud] Fixed an issue where importing dagster_cloud.serverless could fail with a missing boto3 dependency on serverless deployments that did not install the [serverless] extra.

1.13.9 (core) / 0.29.9 (libraries)

New

• Asset group names may now contain / separators to define hierarchical groups (e.g. marketing/ads). Hierarchical groups can be selected with wildcards in asset selections (e.g. group:"marketing/*") and are rendered as nested groups in the asset graph.
• Added an is: filter to the asset selection syntax and search filters to select assets by type (e.g. is:external, is:materializable).
• [dg] DG_PROJECT_PYTHON_EXECUTABLE in a project's .env is now parsed via python-dotenv, so export KEY=value, quoted values, and trailing comments are honored.
• [ui] When filtering assets in the lineage view with the selection input, a "Save selection" button now allows creating a saved selection directly from the input value.
• [ui] Redesigned the recent updates timeline on asset pages.
• [dagster-cloud] Uploads through S3 presigned URLs (code location snapshots, serverless I/O manager objects, compute logs, and PEX files) now retry on transient HTTP 500 errors from S3.
• [dagster-dlt] DltLoadCollectionComponent now supports partitions_def and backfill_policy. (Thanks, @​Benjamin0313!)
• [helm] User code deployments now support running multiple replicas via replicaCount. All replicas of a deployment share a consistent gRPC server ID, so multi-replica deployments do not trigger spurious code location reloads. (Thanks, @​HynekBlaha!)

Bugfixes

• Fixed an issue where date-like strings (e.g. "2021-10-30") in YAML config files were converted to datetime objects instead of being passed through as strings.
• Fixed an issue where run failure sensors did not receive error information when a run failed due to a step failure. The originating step error is now available on the sensor context.
• Fixed an issue where schedules using cron strings constrained to specific hours or days (e.g. */15 9-16 * * 1-5) were incorrectly treated as ticking uniformly throughout the day, which could produce overcounted partition counts and oversized backfills.

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)