[dependabot]

Bumps dagster from 1.13.22 to 1.13.23.

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.

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 #592.