Update dagster requirement from <1.9.6,>=1.7.15 to >=1.7.15,<1.10.2

[dependabot]

Updates the requirements on dagster to permit the latest version.

Changelog

Sourced from dagster's changelog.

1.10.1 (core) / 0.26.1 (libraries)

Bugfixes

• Fixed an issue where runs containing pool-assigned ops without limits set got stuck in the run queue.
• Fixed an issue where a "Message: Cannot return null for non-nullable field PartitionKeys.partitionKeys." error was raised in the launchpad for jobs with unpartitioned assets.
• [ui] Updated "Queue criteria" modal to reference and link to pool concurrency settings pages.
• [ui] The "Queue criteria" modal for a run no longer closes as new runs arrive.

1.10.0 (core) / 0.26.0 (libraries)

New

• Added a new AutomationCondition.data_version_changed() condition.
• [dagster-msteams] Added support for sending messages to PowerAutomate flows using AdaptiveCard formatting.
• dagster definitions validate is now less verbose, primarily highlighting load errors.
• [ui] Made defunct code locations removable when editing environment variables.
• [ui] Added a warning icon to the Agents item in Deployment settings, indicating when there are no active agents.
• [dagster-tableau] Changed logic to show embedded data sources in case published data sources are not present. Also, pulled more metadata from Tableau. (Thanks @​VenkyRules!)
• Added new decorators to reflect our new API lifecycle: @preview, @beta and @superseded. Also added new annotations and warnings to match these new decorators.

Bugfixes

• [ui] Fixed persistence of the group-by setting in the run timeline view.
• [ui] Fixed timestamped links to asset pages from asset check evaluations in run logs.
• [ui] Fixed excessive rendering and querying on the Concurrency configuration page.
• Fixed the step stats calculations for steps that fail and request a retry before the step starts. This happened if a failure occurred in the step worker before the compute function began execution. This should help with sporadic hanging of step retries.
• Fixed an issue where the Concurrency UI was broken for keys with slashes.
• Fixed an issue with emitting AssetResult with ops or multi-assets that are triggered multiple times in the same run.
• [dagster-dbt] Fixed a bug introduced in dagster-dbt 0.25.7 that would cause execution to fail when using the @dbt_assets decorator with an io_manager_key specified.
• [dagster-dbt] Refactored UnitTestDefinition instantiation to address failure to initialize dbt models with unit tests. (Thanks @​kang8!)
• Fixed issue where dagster instance migrate was failing for instances with tables having non-empty concurrency limits.
• Fixed an issue where Declarative Automation sensors in code locations that included source assets referencing assets with automation conditions in other code locations would sometimes cause duplicate runs to be created.
• Turned on run blocking for concurrency keys/pools by default. For op granularity, runs are dequeued if there exists at least one op that can execute once the run has started. For run granularity, runs are dequeued if all pools have available slots.
• [dagster-dbt] Added pool support.
• [dagster-dlt] Added pool support.
• [dagster-sling] Added pool support.

Documentation

• Corrected docs on managing concurrency.
• Fixed a Markdown link to "assets metadata." (Thanks @​rchrand!)
• Fixed a pip install command for Zsh. (Thanks @​aimeecodes!)

Breaking Changes

• The include_sources param on all AssetSelection APIs has been renamed to include_external_assets.
• Disallowed invalid characters (i.e. anything other than letters, numbers, dashes, and underscores) in pool names.
• Changed the default run coordinator to be the queued run coordinator. This requires the Dagster daemon to be running for runs to be launched. To restore the previous behavior, you can add the following configuration block to your dagster.yaml:

... (truncated)

Commits

• 75166fb 1.10.1
• 3eda008 1.10.1 changelog (#27864)
• 0f290c1 [ui] Fix link to deployment concurrency, stop modal from closing as runs arri...
• d40763c update queue criteria to use pool terminology (#27851)
• 30e6bd7 Fix partitionKeysOrError for asset jobs with just unpartitioned assets (#27841)
• bb90347 fix broken test (#27854)
• 9bb6e74 only fetch the concurrency info for configured keys (#27853)
• ef57514 1.10.0
• 3975782 Create the change log and migration guide for 1.10 (#27715)
• e1d42a2 Pull is_transient_task_stopped_reason into a util module (#27690)
• 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)