fix(dagster): Update dagster (patch)

[plural-renovate]

This PR contains the following updates:

Package	Type	Update	Change
dagster-azure (source)		patch	==0.21.4 -> ==0.21.5
dagster-gcp (source)		patch	==0.21.4 -> ==0.21.5
docker.io/dagster/user-code-example	final	patch	1.5.4 -> 1.5.5

---

Release Notes

dagster-io/dagster (dagster-azure)

v0.21.5

New

• Dagster now supports using Pydantic 2 models for Config and Resources. Pydantic 1.10 continues to be supported.
• Added a report_asset_observation REST API endpoint for runless external asset observation events
• Dramatically improved the performance of partition-mapping, for basic hourly and daily partitions definitions
• [ui] When viewing a list of runs, you can quickly add the tag in the “Launched by” column as a filter on the list view. Hover over the tag to see the “Add to filter” button.
• [helm] The env vars DAGSTER_K8S_PG_PASSWORD_SECRET and DAGSTER_K8S_INSTANCE_CONFIG_MAP will no longer be set in all pods.
• [dagster-pyspark] build_pyspark_zip now takes an exclude parameter that can be used to customize the set of excluded files.
• [ui] Links beginning with http://, https:// in unstructured run logs (via context.log) are automatically converted to clickable links

Bugfixes

• Fixed an asset backfill bug where certain asset partitions with no targeted parents would hang indefinitely.
• Fixed a bug where the source_key_prefix argument to load_assets_from_current_module and load_assets_from_package_name was ignored
• Fixed two bugs in dagster_embedded_elt where the mode parameter was not being passed to Sling, and only one asset could be created at a time
• Fixed a bug with handing default values for Pydantic validators on Windows
• [ui] Clicking an asset with checks shows them in the asset graph sidebar, even if live data on the page is still loading.
• [ui] Reported materialization events are presented more clearly in the asset graph sidebar and in other parts of the Dagster UI.

Deprecations

• [helm] The pipelineRun configuration in the Helm chart is now deprecated. The same config can be set under dagster-user-deployments

Community Contributions

• Added setup_for_execution and teardown_after_execution calls to the inner IOManagers of the BranchingIOManager - thank you @​danielgafni!
• The S3FakeResource.upload_fileobj() signature is now consistent with boto3 S3.Client.upload_fileobj() - thank you @​jeanineharb!
• dbt_assets now have an optional name parameter - thank you @​AlexanderVR!

Documentation

• Added a link to Dagster University to the docs landing page 🎓
• Improved readability of API docs landing page
• Removed straggling mention of Dagit from the Kubernetes OSS deployment guide

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[plural-bot]

🎉 This PR is included in version 1.2.5 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀