Update dagster requirement from >=1.13.11 to >=1.13.23

[dependabot]

Updates the requirements on dagster to permit the latest version.

Release notes

Sourced from dagster's releases.

1.13.23 (core) / 0.29.23 (libraries)

New

• In Dagster+, alert policies can now target deployment capacity metrics — queued runs and in-progress runs — evaluated over a rolling window with aggregations such as max.
• In Dagster+ Serverless, fast deploys now build a Docker image instead of a Python executable when the target environment cannot run one: Serverless on Kubernetes, or a Harbor image registry. Set DAGSTER_CLOUD_DISABLE_PEX_DOCKER_REDIRECT to opt out.
• Component definition files can now use the .yml extension in addition to .yaml, as can dagster.yaml and workspace.yaml. .yaml still takes precedence when both are present.
• The dagster-k8s, dagster-celery-k8s, and user-code-example images are now published as multi-platform images supporting both amd64 and arm64.
• [cli] dagster project from-example now produces a components-layout project that installs with uv sync outside the Dagster repo.
• [ui] Updated the Prefect kind tag icon, which now adapts to dark mode.

Bugfixes

• [ui] Fixed an issue where pages that refresh automatically stopped polling after a failed request.
• [ui] Fixed an issue where the Catalog assets folder tree could jump back to the top while scrolling.
• [dagster-dbt] The dbt Cloud client now tolerates a trailing slash in access_url, treats deleting an already-deleted job as success, and includes dbt Cloud's error response body when logging request failures.
• [dagster-prefect] Failure messages now name the Prefect run state consistently across Python versions.

Changelog

Sourced from dagster's changelog.

1.13.23 (core) / 0.29.23 (libraries)

New

• In Dagster+, alert policies can now target deployment capacity metrics — queued runs and in-progress runs — evaluated over a rolling window with aggregations such as max.
• In Dagster+ Serverless, fast deploys now build a Docker image instead of a Python executable when the target environment cannot run one: Serverless on Kubernetes, or a Harbor image registry. Set DAGSTER_CLOUD_DISABLE_PEX_DOCKER_REDIRECT to opt out.
• Component definition files can now use the .yml extension in addition to .yaml, as can dagster.yaml and workspace.yaml. .yaml still takes precedence when both are present.
• The dagster-k8s, dagster-celery-k8s, and user-code-example images are now published as multi-platform images supporting both amd64 and arm64.
• [cli] dagster project from-example now produces a components-layout project that installs with uv sync outside the Dagster repo.
• [ui] Updated the Prefect kind tag icon, which now adapts to dark mode.

Bugfixes

• [ui] Fixed an issue where pages that refresh automatically stopped polling after a failed request.
• [ui] Fixed an issue where the Catalog assets folder tree could jump back to the top while scrolling.
• [dagster-dbt] The dbt Cloud client now tolerates a trailing slash in access_url, treats deleting an already-deleted job as success, and includes dbt Cloud's error response body when logging request failures.
• [dagster-prefect] Failure messages now name the Prefect run state consistently across Python versions.

1.13.22 (core) / 0.29.22 (libraries)

New

• Run dequeuing is now significantly faster when concurrency pools are in use and many runs are queued, as pool state is read once per dequeue pass rather than repeatedly.
• In Dagster+, the MCP server's launch_job_run and launch_asset_run tools no longer require a code location and repository name. They are looked up from the job being launched.
• [ui] The tick timeline now supports filtering to a time window, paging through history, and a live-updating view.
• [dagster-dbt] Added support for dbt-core 1.12. (Thanks, @​jrbasso!)
• [dagster-looker] Now requires python-liquid>=2.2.1 (previously <2).
• [dagster-prefect] A new Prefect integration is available in preview. Launch Prefect deployments and background tasks from a Dagster asset with Dagster Pipes, including partition mapping and cancellation forwarding.

Bugfixes

• In Dagster+, querying asset metrics by asset key no longer fails with a server error.

1.13.21 (core) / 0.29.21 (libraries)

New

• Asset backfills whose runs have all finished but which still have partitions with no materialization status now complete as failed instead of remaining in progress indefinitely.
• In Dagster+, wiping and deleting dynamic partitions in a single action now also supports multi-partitioned assets that use the dynamic partitions definition as a dimension.
• In Dagster+, alert policies defined in a YAML file can no longer be edited, disabled, or deleted from the UI. Update the file and sync instead. Muting is still available from the UI, and the in-app YAML editor now shows only UI-managed alert policies.
• In Dagster+, syncing alert policies from a YAML file no longer deletes alert policies created in the UI. Alert policies that existed before this release are never removed by a sync and must be deleted manually from the UI.
• [ui] Automation condition evaluations now explain history-dependent conditions (since, newly_true, newly_missing) by showing the remembered values that determined them, such as when a latch was set or reset and an operand's value on the current versus previous tick, instead of the operands' current values, which could appear to contradict the parent condition.

Bugfixes

• Fixed an issue where a freshness policy declared for an asset in one code location was ignored when another code location defined the same asset without a policy (for example, a dbt source spec paired with an ingestion-tool materialization). The policy now appears in the asset catalog and is evaluated by the freshness daemon.
• Fixed a bug where a backfill run that materialized some partitions of an asset and failed on others left the failed partitions showing as in progress.
• [dagster-postgres] Fixed a connection leak where checking for the existence of the event log table did not return its connection to the pool, which could exhaust the webserver's connection pool on instances with many asset nodes. (Thanks, @​watacoso!)

Documentation

... (truncated)

Commits

• 562b676 1.13.23
• 7c73a49 Changelog 1.13.23 (#26920)
• e1b09f0 [ui] Add paginated data loading for the Runs redesign (#26792)
• 52b707c Use spawn context in dbt test_snapshot_id (#26835)
• 893941a [ui] Add Runs feed summaries and selection details for the redesign (#26774)
• cc55e54 [ui] Fix scroll jumping in Catalog > Assets folder tree (#26461)
• ebaca8c [dagster-dbt] Harden dbt Cloud client: idempotent job delete, URL normalizati...
• 68e80a6 [ui] Keep automatic refresh working after a failed request (#26800)
• f083f2d Support .yml extension for component definition files (#22306)
• b0541c0 [dagster-dbt] Make the dbt Cloud kitchen-sink suite safe to run concurrently ...
• Additional commits viewable 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)

[dependabot]

Superseded by #141.