PrefectHQ/prefect - CodSpeed

prefect

Blog Docs Changelog

Performance History

Latest Results

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

3 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

Fix typo in documentation about task result handling (#22389)

main

3 days ago

Fix set_working_directory relative path resolution in workspace resolver The workspace resolver introduced in 3.7.0 changes CWD to a temporary workspace root before running pull steps. This caused relative paths passed to set_working_directory to resolve against the temp dir instead of the original process CWD (e.g. the container WORKDIR). Fix: capture the original CWD (source_cwd) via a ContextVar (_PULL_STEP_SOURCE_CWD) before pull steps execute. In set_working_directory, resolve relative paths against source_cwd when the ContextVar is set. Clear the ContextVar after any step that produces a directory output or changes CWD, so subsequent steps resolve relative paths against the updated CWD. Closes #22391

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

3 days ago

fix: static analysis Signed-off-by: Hemant M Mehta <hemant29mehta@gmail.com>

hemantmm:flow-run-graph-attempt-filter

3 days ago

fix(databricks): conform partner User-Agent to Databricks telemetry attribution format (#22359) Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

main

4 days ago

Raise clear error when FlowRun/TaskRun passed as task argument (#22352) Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> Co-authored-by: Alex Streed <alex.s@prefect.io> Co-authored-by: alex.s <ajstreed1@gmail.com>

main

4 days ago

Latest Branches

0%

Preserve a paused deployment schedule on redeploy#22396

4 hours ago

8ef8a3d

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

0%

Fix `set_working_directory` relative path resolution in workspace resolver#22392

3 days ago

ee92d41

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

0%

fix: flow-run-graph-attempt-filter#22388

3 days ago

7d75503

hemantmm:flow-run-graph-attempt-filter

© 2026 CodSpeed Technology

Home Terms Privacy Docs