Bump dagster from 1.8.3 to 1.12.9

[dependabot]

Bumps dagster from 1.8.3 to 1.12.9.

Changelog

Sourced from dagster's changelog.

1.12.9 (core) / 0.28.9 (libraries)

New

• The core dagster package (and most libraries) are now compatible with Python 3.14.
• Added support for using python version 3.13 when running dg plus deploy.
• dg plus login now supports a region flag for eu-based users: dg plus login --region eu.
• Updated the bulk_actions table body column from Text to LongText for Mysql storage. To take advantage of this migration run dagster instance migrate. (Thanks, @​jenkoian!)
• Updated the asset_keys table cached_status_data column from Text to LongText for Mysql storage. To take advantage of this migration run dagster instance migrate. (Thanks, @​jenkoian!)
• Runs now automatically include a dagster/code_location tag when created with a remote_job_origin, enabling filtering and concurrency control by code location. (Thanks, @​ssup2!)
• [ui] the Asset > Partitions page now shows historical "Failed to materialize" events for consistency with the Asset > Events page.
• [helm] Added a concurrency setting to the helm chart to configure concurrency pools.
• [dagster-azure] The ADLS2PickleIOManager now overwrites blob keys when the same asset is materialized twice, instead of deleting then writing the blob.
• [dagster-aws] An ecs/container_overrides tag can now be set on jobs (or on runs in the launchpad) to customize container-level overrides (like GPU resource requirements) for runs using the EcsRunLauncher.
• [dagster-dbt] dagster-dbt now supports dbt-core 1.11. (Thanks, @​nicoa!)
• [dagster-dlt] update url in README (Thanks, @​Miesjell!)
• [dagster-databricks] Introduced DatabricksWorkspaceComponent to automatically discover Databricks jobs as Dagster assets.
• [dagster-looker] Added option PDT asset support to LookerComponent.

Bugfixes

• Fixed an issue where a transient issue caused a step health check to fail when using the k8s_job_executor.
• Fixed an issue where a health check failure while using the k8s_job_executor could result in a step continuing to run after the run failed.
• Invalid TimeWindowPartitionsDefinitions that contain multiple time windows that map to the same partition key (for example, an hourly partitions definition with a daily format key) will now raise an Exception during dagster definitions validate, instead of being allowed but causing undefined behavior.
• [ui] Entering the asset launchpad by right-clicking on the asset graph no longer causes keyboard navigation issues.
• [ui] Fixed an issue where removing an asset prevented rendering status information for backfills involving that asset in the Dagster UI.
• [dagster-dbt] Fixed issue that could cause the DbtCliEventMessage iterator to error while parsing certain error messages produced by dbt-core.

1.12.8 (core) / 0.28.8 (libraries)

New

• dg plus deploy commands now support Python 3.13 and Python 3.14.

Bugfixes

• Fixed an issue where the Dagster Helm chart and Dagster+ agent helm chart could no longer deploy using Helm without adding the --skip-schema-validation flag to the Helm deploy command. Thanks @​kang8!

1.12.7 (core) / 0.28.7 (libraries)

New

• Optimized performance of calculating partition keys for time window partitions with exclusions.
• timedelta and datetime are now available via the datetime context when rendering components (Thanks, @​stevenayers!)
• FreshnessPolicy is now available via the dg context when rendering components. (Thanks, @​stevenayers!)
• Assets may now be annotated with up to 10 kinds (limit was previously 3).
• Arbitrary resource parameters may now be hidden in the UI by setting json_schema_extra={"dagster__is_secret": True} on the corresponding Field definition in the resource class.
• The dg docs cli group has been removed. The integrations subcommand has been moved to dg utils integrations.
• Bumped the gql dependency in dagster-graphql to be inclusive of v4 for broader transitive dependency compatibility
• [dagster-omni] Fix issue where retries would terminate while asynchronously gathering metadata.

... (truncated)

Commits

• 98b78ef 1.12.9
• 6b0c966 [ui] Expicitly install assert dep to resolve CSP issue (#33214)
• 0c64cc5 [dagster-dbt] Fix issue with parsing certain test error messages (#33211)
• aa97ecd Don't fail a step when check_step_health raises an exception (#33209)
• aaccb06 [dagster-ui] updates occurrences of array element access non-null checks with...
• 648fc05 [dagster-ui] remove usage of external invariant package (#33181)
• 2577bb6 [dagster-ui] introduce invariant utilities: invariant() and `assertExists()...
• 292a701 Better handling for health check failures in StepDelegatingExecutor (#33205)
• 774446f Allow dbt-core 1.11 (#33105)
• 437f92d [helm] adds support for configuring pools/concurrency (#33194)
• 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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)
  You can disable automated security fix PRs for this repo from the Security Alerts page.