Bump dagster-graphql from 1.6.9 to 1.7.7

[dependabot]

Bumps dagster-graphql from 1.6.9 to 1.7.7.

Changelog

Sourced from dagster-graphql's changelog.

1.7.7 (core) / 0.23.7 (libraries)

New

• [ui] Command clicking on nodes in the asset lineage tab will now open them in a separate tab. Same with external asset links in the asset graph.
• Added support for setting a custom job namespace in user code deployments. (thanks @​tmatthews0020!)
• Removed warnings due to use of datetime.utcfromtimestamp (thanks @dbrtly!)
• Custom smtp user can now be used for e-mail alerts (thanks @edsoncezar16!)
• [dagster-dbt] Added support for dbt-core==1.8.*.
• [dagster-embedded-elt] Failed dlt pipelines are now accurately reflected on the asset materialization (thanks @edsoncezar16!)

Bugfixes

• Fixed spurious errors in logs due to module shadowing.
• Fixed an issue in the Backfill Daemon where if the assets to be materialized had different BackfillPolicys, each asset would get materialized in its own run, rather than grouping assets together into single run.
• Fixed an issue that could cause the Asset Daemon to lose information in its cursor about an asset if that asset’s code location was temporarily unavailable.
• [dagster-dbt] Mitigated issues with cli length limits by only listing specific dbt tests as needed when the tests aren’t included via indirect selection, rather than listing all tests.

Documentation

• Markdoc tags can now be used in place of MDX components (thanks @nikomancy)

1.7.6 (core) / 0.23.6 (libraries)

New

• The backfill daemon now has additional logging to document the progression through each tick and why assets are and are not materialized during each evaluation of a backfill.
• Made performance improvements in both calculating and storing data version for assets, especially for assets with a large fan-in.
• Standardized table row count metadata output by various integrations to dagster/row_count .
• [dagster-aws][community-contribution] Additional parameters can now be passed to the following resources: CloudwatchLogsHandler, ECRPublicClient, SecretsManagerResource, SSMResource thanks @jacob-white-simplisafe !
• Added additional frontend telemetry. See https://docs.dagster.io/about/telemetry for more information.

Bugfixes

• Fixed issue that could cause runs to fail if they targeted any assets which had a metadata value of type TableMetadataValue, TableSchemaMetadataValue, or TableColumnLineageMetadataValue defined.
• Fixed an issue which could cause evaluations produced via the Auto-materialize system to not render the “skip”-type rules.
• Backfills of asset jobs now correctly use the BackfillPolicy of the underlying assets in the job.
• [dagster-databricks][community-contribution] databricks-sdk version bumped to 0.17.0, thanks @lamalex !
• [helm][community-contribution] resolved incorrect comments about dagster code-server start , thanks @SanjaySiddharth !

Documentation

• Added section headings to Pipes API references, along with explanatory copy and links to relevant pages
• Added a guide for subletting asset checks
• Add more detailed steps to transition from serverless to hybrid
• [community-contribution] asset selection syntax corrected, thanks @JonathanLai2004!

Dagster Plus

• Fixed an issue where Dagster Cloud agents would wait longer than necessary when multiple code locations were timing out during a deployment.

... (truncated)

Commits

• f911fb8 bring back dbt core version upper bound
• c4707b2 1.7.7
• 1cfd2de Fix fast partition count calculations for daily partitions definition (#22046)
• aaaa8c5 Revert "Pin requests < 2.32.0" (#22055)
• d11bd69 updated dockerfile for uv 2.0 (#22039)
• c62d958 Fix freshness sensor to use assetchecksummaryrecord (#22013)
• 45fb40b AssetCheckSummaryRecord (#21940)
• d5ec06c [dagster-dbt] fix dbt row count behavior on warehouses, test row count code o...
• 878997a [dagster-polars] bump pin (#22007)
• 52152d6 metadata bounds asset checks (#21630)
• 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)

[dependabot]

Superseded by #144.