fix(ingest-data): update dependency prefect to v2.13.5 #11675
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.13.4
->2.13.5
⚠ Dependency Lookup Warnings ⚠
Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.
Release Notes
PrefectHQ/prefect (prefect)
v2.13.5
Compare Source
Load and serve remotely stored flows
You can now load and serve flows from a git repository!
With the new
flow.from_source
method, you can specify a git repository and a path to a flow file in that repository. This method will return a flow object that can be run or served withflow.serve()
.Here's an example of loading a flow from a git repository and serving it:
When you load and serve a flow from a git repository, the serving process will periodically poll the repository for changes. This means that you can update the flow in the repository and the changes will be reflected in the served flow without restarting the serve script!
To learn more about loading and serving flows from a git repository, check out the docs!
See the following pull requests for details:
Experimental Pydantic 2 Compatibility
We're working eagerly toward having
prefect
installable with eitherpydantic<2
orpydantic>2
. As a first step toward compatibility, we've ensured that Prefect's use ofpydantic
is isolated from your use ofpydantic
in as many ways as possible. As of this release,prefect
still has a statedpydantic
requirement of<2
, but we are testing againstpydantic>2
in our continuous integration tests. If you're feeling adventurous, feel free to manually installpydantic>2
and run some flows with it. If you do, please let us know how it's going with a note in Slack or with a Github issue.See the following pull requests for details
Enhancements
PREFECT_UI_API_URL
to relative path /api — https://github.com/PrefectHQ/prefect/pull/10755prefect deploy
— https://github.com/PrefectHQ/prefect/pull/10656Fixes
default-agent-pool
work pool if no pool is specified — https://github.com/PrefectHQ/prefect/pull/10804Runner
to correctly handle spaces in Python executable path — https://github.com/PrefectHQ/prefect/pull/10878PREFECT__FLOW_RUN_ID
environment variable to dash-delimited UUID format — https://github.com/PrefectHQ/prefect/pull/10881prefect
in a thread — https://github.com/PrefectHQ/prefect/pull/10871Documentation
.serve()
in tutorials — https://github.com/PrefectHQ/prefect/pull/10861Contributors
All changes: PrefectHQ/prefect@2.13.4...2.13.5
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.