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.

Sign up for GitHub

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

Jump to bottom

Bump prefect from 2.17.1 to 2.20.1 #38

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Bump prefect from 2.17.1 to 2.20.1 #38

wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Aug 12, 2024

Bumps prefect from 2.17.1 to 2.20.1.

Release notes

Sourced from prefect's releases.

2.20.1: pip, pip hooray!

This release is small and includes fixes for various dependency issues, as well as a fix for submodule handling in git-based deployments.

Python 3.11 introduced the concept of "exception groups" for situations in which multiple unrelated exceptions need to be raised - for example, in concurrent execution models or retrying an operation across distinct error modes. Prefect has begun to leverage this capability, and we rely on a separate package (exceptiongroup) which backports this functionality to lower supported versions of Python. This dependency was missing from client-side requirements in 2.20.0.

Bug Fixes 🐞

Integrations & Dependencies 🤝

Development & Tidiness 🧹

2.20.0: CVE you later

Continuing the 2.0 lineage, Prefect's 2.20 release includes a major compatibility upgrade with anyio: previous versions of anyio were subject to a critical race condition that many CVE scanners are flagging as a high severity vulnerability. Because of the changes necessary in this upgrade, please be aware that new versions of many Prefect integration packages such as prefect-dask and prefect-ray will require 2.20.0 to function properly.

(For those who have already upgraded to 3.0, don't worry - Prefect 3.0 release candidates are already anyio>=4.4.0 compatible).

Bug Fixes 🐞

Integrations & Dependencies 🤝

Development & Tidiness 🧹

Full Changelog: PrefectHQ/prefect@2.19.9...2.20

2.19.9: Sync or Swim

This PR continues Prefect's 2.0 lineage as we prepare for a major 3.0 release. This release is particularly special with respect to 3.0 as it adds warnings to APIs or interfaces that will need updating in 3.0.

There are many internal APIs in Prefect that can be run both synchronously and asynchronously depending on the runtime context in which they are called. If you've ever encountered the error AttributeError: 'coroutine' object has no attribute when loading a Block then you know what I'm referring to. In 3.0 we have updated the internal logic for switching between synchronous/asynchronous modes in an attempt to provide clearer guidelines and improved performance.

If you ever encounter such an error, you can now use the special _sync keyword argument to explicitly enforce the mode of execution you'd prefer:

my_block = Block.load("example/block", _sync=True)
my_block = await Block.load("example/block", _sync=False)
</tr></table>

... (truncated)

Changelog

Sourced from prefect's changelog.

Prefect Release Notes

Release 3.0.0rc10

Enhancements

Fixes

Documentation

... (truncated)

Commits

Dependabot compatibility score

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
Bump prefect from 2.17.1 to 2.20.1
83daeaa 
Bumps [prefect](https://github.com/PrefectHQ/prefect) from 2.17.1 to 2.20.1.
- [Release notes](https://github.com/PrefectHQ/prefect/releases)
- [Changelog](https://github.com/PrefectHQ/prefect/blob/main/RELEASE-NOTES.md)
- [Commits](PrefectHQ/prefect@2.17.1...2.20.1)

---
updated-dependencies:
- dependency-name: prefect
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot requested a review from jeanluciano as a code owner August 12, 2024 08:17
@dependabot dependabot bot added dependencies Pull requests that update a dependency file python Pull requests that update Python code labels Aug 12, 2024
@dependabot dependabot bot mentioned this pull request Aug 12, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@jeanluciano jeanluciano Awaiting requested review from jeanluciano jeanluciano is a code owner

At least 1 approving review is required to merge this pull request.

Assignees
No one assigned
Labels
dependencies Pull requests that update a dependency file python Pull requests that update Python code
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants