PrefectHQ/prefect - CodSpeed

prefect

Blog Docs Changelog

Performance History

Latest Results

Use single backticks in action-normalization docstring Co-authored-by: alex.s <alex.s@prefect.io> Co-Authored-By: alex.s <ajstreed1@gmail.com>

devin/1782780327-prefect-yaml-single-step-mapping

54 minutes ago

fix: run pull steps for module-path entrypoints when loading flow from flow run (#22376)

main

5 hours ago

docs: align Docker deployment examples with current step contract (#22400) Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> Co-authored-by: alex.s <alex.s@prefect.io> Co-authored-by: alex.s <ajstreed1@gmail.com>

main

8 hours ago

docs: align docker build examples with tag Co-authored-by: alex.s <alex.s@prefect.io> Co-Authored-By: alex.s <ajstreed1@gmail.com>

devin/20260629-docker-docs-tag-fix

9 hours ago

Fix `set_working_directory` relative path resolution in workspace resolver (#22392) Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> Co-authored-by: Alexander Streed <alex.s@prefect.io>

main

10 hours ago

Preserve a paused deployment schedule on redeploy A schedule that was turned off in the UI was silently re-activated when the deployment was re-deployed without an explicit `active`, as long as the schedule had no slug. Two things combined to cause this: - The client always serialized `active=True` for a schedule when the caller didn't pass `active`, so the update payload (built with `exclude_unset=True`) still forced the schedule active. - On update, the server recreates slug-less schedules from scratch and defaulted `active` to True, discarding the previous state. `active` is now left unset on the schedule helpers and the `Schedule` factories when the caller doesn't provide it, so an update omits it entirely. The server update path inherits the existing schedule's active state when an update doesn't specify one, matching schedules by slug or, for slug-less schedules, by their definition. A new or changed schedule still defaults to active.

apoorva-01:fix/19302-preserve-disabled-schedule-on-redeploy

16 hours ago

Clear source CWD after every step to fix workspace-relative composition The _PULL_STEP_SOURCE_CWD ContextVar was only cleared after steps that produced a 'directory' output or changed CWD. Steps like run_shell_script that create workspace content without either signal left the source CWD set, causing a subsequent set_working_directory to resolve relative paths against the original process CWD instead of the workspace root. Now clear the ContextVar after every step completion so the source-CWD fallback only applies to the first pull step (the baked-image case). Co-authored-by: Alexander Streed <alex.s@prefect.io>

devin/1782499546-fix-set-working-directory-relative-path

3 days ago

Update security issue reporting instructions (#22356)

main

3 days ago

Latest Branches

0%

Accept a single step mapping in prefect.yaml action sections#22403

1 hour ago

f992c58

devin/1782780327-prefect-yaml-single-step-mapping

0%

docs: align Docker deployment examples with current step contract#22400

10 hours ago

ea43e3f

devin/20260629-docker-docs-tag-fix

0%

Preserve a paused deployment schedule on redeploy#22396

16 hours ago

8ef8a3d

apoorva-01:fix/19302-preserve-disabled-schedule-on-redeploy

© 2026 CodSpeed Technology

Home Terms Privacy Docs