Update dagster-postgres requirement from <0.21.7,>=0.21.5 to >=0.21.5,<0.21.8

[dependabot]

Updates the requirements on dagster-postgres to permit the latest version.

Changelog

Sourced from dagster-postgres's changelog.

1.5.7 / 0.21.7 (libraries)

New

• The OpExecutionContext and AssetExecutionContext now have a partition_keys property
• [dagster-ui] The asset graph layout algorithm has been changed to a much faster one called “tight-tree”
• [dagster-ui] The Runs table filters has a top level filter for partitions
• [dagster-dbt] dbt-core==1.7.* is now supported.

Bugfixes

• Fixed an issue where some schedules skipped a tick on the day after a fall Daylight Savings Time transition.
• Fixed a bug that caused backfill policies that execute multiple partitions in a single run not to work with dynamic partitions.
• Fixed a bug that caused an error when build_schedule_from_partitioned_job was used with a job with multi-partitioned assets and the partitions_def argument wasn’t provided to define_asset_job.
• We now raise an error early if the empty string is provided as an asset’s group name (Thanks Sierrra!)
• Fixed an issue where custom setup and teardown methods were not properly called on nested Pythonic resources.
• Added a warning message when op or asset config is passed as an argument not named config.
• [dagster-cloud] Fixed an issue where overriding the default I/O manager could break the Snowflake-dbt insights job.
• [auto-materialize] Fixed an issue where materializing an unpartitioned parent of a dynamic-partitioned asset would only result in the latest dynamic partition of that asset being requested. Now, all partitions will be requested.
• [dagster-embedded-elt] Fixed an issue in dagster-embedded-elt where sling’s updated_at parameter was set to the incorrect type
• [dagster-ui] Fixed an issue in the launchpad where selecting a partition wouldn’t correctly overwrite fields using the partition’s specific configuration

Community Contributions

• A docs fix to the testing concepts page, thanks @​NicolaiLolansen!
• The schema can now be overridden per asset in DB IO managers, thanks @​jrstats!

Experimental

• Improved failure recovery and retry behavior when the daemon that launches auto-materialization runs fails or crashes in the middle of a tick.
• [asset-checks] UI performance for displaying check results is improved
• [asset-checks] Removed noisy experimental warning about AssetCheckKey
• [op-concurrency] Fixed a bug where concurrency slots were not getting assigned if a run that was assigned a slot was deleted before the slot had actually been claimed during execution.
• [dagster-pipes] The PipesSubprocessClient now inherits the environment variables of the parent process in the launched subprocess.
• [dagster-pipes] Exceptions are now reported in the event log for framework components and from the external process.

Documentation

• Added a guide for using Dagster Pipes with Databricks

1.5.6 / 0.21.6 (libraries)

New

• [dagster-k8s] The PipesK8sClient will now attempt to load the appropriate kubernetes config, and exposes arguments for controlling this process.
• [ui] The launch asset backfill modal now offers a preview dialog showing the targeted asset partitions and their backfill policies when partition mapping or varying backfill policies are present.
• [asset-checks] New load_asset_checks_from_modules functions for loading asset checks in tandem with load_assets_from_modules.
• Previously, the daemon process would terminate with an error if it believed that a thread might be hanging, which sometimes caused undesirable terminations when doing large backfills or auto-materializing many assets. Now, the daemon process will emit a warning instead of terminate.
• [dagster-dbt] dagster-dbt project scaffold now uses ~/.dbt/profiles.yml if a profiles.yml is not present in the dbt project directory.
• [dagster-dbt] @dbt_assets now support PartitionMapping using DagsterDbtTranslator.get_partition_mapping.

... (truncated)

Commits

• See full diff 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)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (2aaafc4) 88.7% compared to head (c1f8ea5) 88.7%.
Report is 2 commits behind head on dev.

Additional details and impacted files

@@          Coverage Diff          @@
##             dev   #3037   +/-   ##
=====================================
  Coverage   88.7%   88.7%           
=====================================
  Files         90      90           
  Lines      10988   10994    +6     
=====================================
+ Hits        9752    9758    +6     
  Misses      1236    1236           

Files	Coverage Δ
src/pudl/extract/xbrl.py	96.0% <100.0%> (+0.4%)	⬆️
src/pudl/workspace/setup.py	91.8% <100.0%> (+0.1%)	⬆️

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.