Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(dagster): Update dagster (patch) #162

Merged
merged 1 commit into from
Aug 4, 2023
Merged

Conversation

plural-renovate[bot]
Copy link
Contributor

@plural-renovate plural-renovate bot commented Aug 3, 2023

This PR contains the following updates:

Package Type Update Change
dagster-azure (source) patch ==0.20.3 -> ==0.20.4
dagster-gcp (source) patch ==0.20.3 -> ==0.20.4
docker.io/dagster/user-code-example final patch 1.4.3 -> 1.4.4

Release Notes

dagster-io/dagster (dagster-azure)

v0.20.4

New
  • [ui] When viewing a run for auto-materialized assets, show a tag with information about the assets that were materialized.
  • [ui] In the Auto-materialize History view, when one or more of an asset’s parents have been updated, the set of updated parents will be viewable.
  • [ui] Link to the auto-materialized history for an asset from the asset DAG view.
  • [ui] For runs that were the result of auto-observation, show a tag for this in the Runs list view.
  • Added warnings for storage incompatibility with the experimental global op concurrency.
Bugfixes
  • [dagster-dbt] Fixed an issue where dagster-dbt project scaffold didn’t create a project directory with all the scaffolded files.
  • Fixed an issue which could cause errors when using the SpecificPartitionsPartitionMapping with auto-materialization.
Breaking Change
  • Previously, it was possible to set max_materializations_per_minute on an AutoMaterializePolicy to a non-positive number. This will now result in an error.
Community Contributions
  • Fix for loading multipartitions paths in upath_io_manager from @​harrylojames; thank you!
  • Docs typo fix from @​C0DK; thank you!
Documentation
  • Revamped the dagster-dbt tutorial to take advantage of dagster project scaffold and the new dagster-dbt APIs.

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

Signed-off-by: plural-renovate[bot] <plural-renovate[bot]@users.noreply.github.com>
@plural-renovate plural-renovate bot changed the title fix(dagster): Update dagster to v0.20.4 (patch) fix(dagster): Update dagster (patch) Aug 4, 2023
@@ -1,4 +1,4 @@
FROM docker.io/dagster/user-code-example:1.4.3
FROM docker.io/dagster/user-code-example:1.4.4

Check failure

Code scanning / Trivy

Image user should not be &#39;root&#39; High

Artifact: dagster/Dockerfile
Type: dockerfile
Vulnerability DS002
Severity: HIGH
Message: Specify at least 1 USER command in Dockerfile with non-root user as argument
Link: DS002
@@ -1,4 +1,4 @@
FROM docker.io/dagster/user-code-example:1.4.3
FROM docker.io/dagster/user-code-example:1.4.4

Check notice

Code scanning / Trivy

No HEALTHCHECK defined Low

Artifact: dagster/Dockerfile
Type: dockerfile
Vulnerability DS026
Severity: LOW
Message: Add HEALTHCHECK instruction in your Dockerfile
Link: DS026
@plural-renovate plural-renovate bot merged commit 1c9498b into main Aug 4, 2023
2 of 3 checks passed
@plural-bot
Copy link
Collaborator

🎉 This PR is included in version 1.1.4 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

@plural-renovate plural-renovate bot deleted the renovate/patch-dagster branch August 4, 2023 01:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant