Skip to content

Release Notes

For any questions or concerns, please reach out to support@prefect.io.

June 2025 Prefect Self-Managed Release Notes

Versions

Please see below the tags to pull the latest helm charts and images from Google Artifact Registry.

  • Latest Server Image: 2025.0625.164239
  • Latest UI Image: 2025.0625.164306
  • Latest Prefect Istio Chart: 0.1.3
  • Latest Self-Managed Cloud Chart: 0.7.0
  • Latest 2.x Client Supported: 2.20.16
  • Latest 3.x Client Supported: 3.4.6
  • Next Scheduled Release: 09/2025

Features

  • Schedule Parameters and Slug Support - Enhanced scheduling capabilities with parameter support and slug-based references backported from Nebula
  • Work Pool Storage Configuration - Comprehensive storage configuration options for work pools with deployment parameter schema updates
  • ANDed Related Resources in Event Queries - Support for AND operations in event queries for more precise filtering
  • Work Pool/Queue/Job Variables in Flow Run Creation - Enhanced FlowRunCreate with support for work pool, queue, and job variable fields
  • Updateable Pull Steps for Deployments - Pull steps can now be modified post-deployment creation
  • Admin API Access for Owners/Admins - Direct admin API access for account owners and administrators
  • Persistent Tracing Filters - UI tracing filters now saved to local storage
  • Deployment versioning - deployment versions from later client versions will show in the UI but this release does not cover full deployment version rollback

Maintenance

  • Fixed TaskRunPolicy Retry Delays - Proper float value support for retry_delay configurations
  • Enabled Autocommit Mode for Automations - Improved transaction handling for automation workflows
  • Removed Cloud-Specific Features - Removed rate limiting, billing, managed execution, and incident management features for optimized self-managed experience

Upgrading Self Managed Cloud

Upgrade Guidelines

Each release of Prefect Cloud is associated with a specific helm chart revision, which introduces new or updated services to your infrastructure. As such, when upgrading Prefect Server and UI versions, you must upgrade the helm chart as well. The relevant chart should be packaged with each quarterly release of Prefect Cloud.

Below we will provide important information on changes between Helm chart releases to make note of as you migrate from each minor version.

Note You must update Prefect versions one release (and subsequently chart minor release) at a time. (i.e 0.4.2 -> 0.5.2 -> 0.6.1 -> 0.7.0)

Upgrade from 0.6.x - 0.7.x

Breaking Values file updates

N/A

Non-Breaking Values file updates

Specify Ingress backend service

You can now specify an existing service for the ingress backend(s) to point to. Defaults to the prefect-istio-gateway instance.

ingress:
  frontend:
    port: ""
    targetServiceName: ""

ingress:
  backend:
    port: ""
    targetServiceName: ""
Maintenance Mode

Starting in chart release 0.7.0 you can now enable maintenance mode for the application directly from the Helm Chart. Enabling:

serviceMesh:
  maintenanceMode:
    enabled: true

Disabling:

serviceMesh:
  maintenanceMode:
    enabled: false

Upgrade from 0.5.x - 0.6.x

Breaking Values file updates

N/A

Non-Breaking Values file updates

Cloud Features

Enabling cloud features directly from the helm chart is now enabled.

cloudFeatures:
  - disable-rate-limiting
  - schemas-v2
Autoscaling off external metrics and autoscaling behavior

It is now possible to configure outscaling based upon external metrics rather than the default CPU/Memory metrics and scaling behavior can be adjusted.

backend:
  autoscaling:
    actions:
      minReplicas: 1
      maxReplicas: 2
      metrics:
        - containerResource:
            container: actions
            name: memory
            target:
              averageUtilization: 95
              type: Utilization
      behavior:
        scaleDown:
          policies;
            - periodSeconds: 120
              type: Pods
              value: 2
          selectPolicy: Max
          stabilizationWindowSeconds: 10
Readiness Probes

It is now possible to create readiness probes per application with defaults provided.

actions:
  cloud2:
    readinessProbe:
      exec:
        command:
          - /bin/sh
          - -c
          - ps aux | grep "prefect" | grep -v grep
      initialDelaySeconds: 15
      periodSeconds: 10
      timeoutSeconds: 3
      failureThreshold: 3

Upgrade from 0.4.x - 0.5.x

Breaking Values file updates

Frontend and Backend URL migration

Before:

ingress:
  frontend:
    url: <URL> # Remove this line
    path: "/"

After:

frontendUrl: <URL>
ingress:
  frontend:
    path: "/"

Before:

ingress:
  backend:
    url: <URL> # Remove this line
    path: "/"

After:

backendUrl: <URL>
ingress:
  backend:
    path: "/"

Non-Breaking Values file updates

Autoscaling

It is now possible to set max and min replicas for each service if autoscaling is enabled.

backend:
  autoscaling:
    actions:
      minReplicas: 1
      maxReplicas: 2