JFrog Workers Release Information

Here's where you'll find the latest release notes for JFrog Workers, including the main fixes and enhancements made to each version as it is released. Each version heading indicates whether the release applies to SaaS, Self-Managed, or both.

Self-ManagedSaaS
1.2161.359

JFrog Workers 1.359 SaaS

Released: 9 September, 2026

Highlights

  • Support for Crypto Helpers in Worker Scripts

    JFrog Workers now supports using context.crypto.hash(), context.crypto.hmac(), and context.crypto.randomBytes() in Worker scripts. You can hash data, compute HMAC values, and generate random bytes from the Worker context.

  • Virtual Repositories Removed from Repository Filters

    The Worker repository filter no longer lists virtual repositories. You can select local, remote, and federated repositories, including the Any Local, Any Remote, and Any Federated shortcuts.

JFrog Workers 1.294 SaaS

Released: 24 August, 2026

Highlights

  • Tutorial and Feedback Buttons Removed from Workers UI

    The JFrog Platform UI no longer includes tutorial and feedback buttons on the Workers pages.

JFrog Workers 1.230 SaaS

Released: 4 August, 2026

Highlights

  • Workers Pages Use Unified Breadcrumbs

    The Workers pages in the JFrog Platform UI now use the same breadcrumbs as other JFrog Platform pages.

Resolved Issues

  • Fixed an issue whereby impersonation token scopes that wrap the username in double quotes were not parsed. Worker executions then used the token identity instead of the impersonated user.

JFrog Workers 1.219 SaaS

Released: 27 July, 2026

Resolved Issues

  • Fixed an issue whereby users whose username contains a space could not access Workers in the UI or use Worker service APIs, such as executing an HTTP-triggered Worker.

JFrog Workers 1.216 Self-Managed

Released: 10 July, 2026

This Self-Managed release includes versions 1.200.0 through 1.215.x. It also includes the changes from 1.217.0 and 1.219.0, which are not published as separate Docker images.

Highlights

  • Execution Logs Saved for Killed Worker Runs

    JFrog Workers now returns the Worker execution logs when a run is killed, so you can debug timeouts and other resource exhaustion.

  • Support for Generic Platform HTTP Requests

    JFrog Workers now supports platformHttp.request(method, body, headers), which lets you send a request with the HTTP method, body, and headers you specify, including a body with DELETE. The existing get, post, put, patch, and delete methods are unchanged.

  • Support for Base64-Encoded Worker Source Code

    JFrog Workers now accepts Worker source code as plain text or encoded in Base64. The JFrog Platform UI sends source code as Base64.

  • User Context Included in Worker Event Payload

    JFrog Workers now includes the user context of the event that triggered the Worker in the event payload. The userContext object includes the user ID or token ID, whether the identity is a token, and the realm.

  • Support for Paged Worker Execution History

    JFrog Workers now supports fetching execution history in smaller pages by using the maxItems, start, and end query parameters. For more information, see Get Worker Execution History.

Resolved Issues

  • Fixed an issue whereby users whose username contains a space could not access Workers in the UI or use Worker service APIs, such as executing an HTTP-triggered Worker.
  • Fixed an issue whereby PlatformContext.baseUrl returned the Kubernetes internal service URL instead of the platform base URL.

JFrog Workers 1.203 SaaS

Released: 27 April, 2026

Highlights

  • Improved Worker Metrics

    The JFrog Platform now supports tenant metrics that do not reset after each metrics endpoint call.

JFrog Workers 1.199 Self-Managed

This Self-Hosted release includes versions 1.179.1 through 1.198.x.

Highlights

  • Worker Warnings and Backoff Displayed in the UI

    The Workers list now shows a warning icon next to a Worker name when there is a warning, including when the Worker is in backoff after repeated execution failures. Hover over the icon to see the reason. You can dismiss a warning, and if a Worker has more than one warning, you can open a dialog to view all of them. Executions that were stopped because of backoff appear in Troubleshooting. Failures caused by queue wait time, and test runs from the edit page, do not trigger backoff. For more information, see Workers Limitations.

Resolved Issues

  • This version includes bug fixes and dependency security fixes.

JFrog Workers 1.179 Self-Managed

Released: 6 January, 2026

This Self-Hosted release includes versions 1.167.1 through 1.178.x.

Highlights

  • Support for Worker Code Validation During Save

    The JFrog Platform now supports compiling the Worker TypeScript code while saving. If the compilation fails, the Worker will not be saved.

Resolved Issues

  • This version includes bug fixes and dependency security fixes.

JFrog Workers 1.167 Self-Managed

Released: 15 October, 2025

Highlights

  • Introducing JFrog Worker Docker Compose Installer

    The JFrog Platform now supports a Docker Compose package for the new JFrog Worker service to automate and extend your platform workflows in Self-Hosted environments. Use this new package to connect JFrog Workers to your JFrog Platform and execute custom logic within a secure and isolated environment. For more information, see Install JFrog Worker with Docker Compose.

  • Support for State Management Variables

    JFrog Workers now supports setting context variables in the Worker script, allowing you to preserve information about state between Worker runs. For more information, see Optimize Workers Within Platform Limits.

  • Workers Code Gallery Improvements

    The Workers code gallery is now better integrated in the user flow, providing Worker script samples to accelerate and inspire your work.

  • Support for Getting Remaining Execution Time

    JFrog Workers now supports the function context.getRemainingExecutionTime(), which allows you to get the remaining number of milliseconds before a Worker execution time out.

  • Trace ID Displayed in Workers Troubleshooting

    Workers Troubleshooting now displays the trace ID of the event that triggered the Worker execution.

  • Updated Artifactory Worker Events

    Updated the following Worker Events:

    • After Copy: The following fields are removed from the Sample Payload:

      contentLength, trustServerChecksums, servletContextUrl, skipJarIndexing and disableRedirect.

    • After Delete: The following field is removed from the Sample Payload:

      headers

    • After Property Create: The following fields are removed from the Sample Payload:

      contentLength, trustServerChecksums, servletContextUrl, skipJarIndexing, disableRedirect and headers.

    • After Move: The following fields are removed from the Sample Payload:

      contentLength, trustServerChecksums, servletContextUrl, skipJarIndexing and disableRedirect.

    • Before Move: The following fields are removed from the Sample Payload:

      contentLength, trustServerChecksums, servletContextUrl, skipJarIndexing and disableRedirect.

  • Error Location Appears in Execution Logs

    JFrog Workers now displays the location of an error in the Worker’s execution logs, instead of in the execution error message.

  • Support for Non-Secret Properties

    JFrog Workers now supports adding non-secret Worker properties, allowing you to configure Workers.

JFrog Workers 1.164 SaaS

Released: 30 September, 2025

Highlights

  • Support for State Management Variables

    JFrog Workers now supports setting context variables in the Worker script, allowing you to preserve information about state between Worker runs. For more information, see StateManager .

  • Workers Code Gallery Improvements

    The Workers code gallery is now better integrated in the user flow, providing Worker script samples to accelerate and inspire your work.

  • Support for Getting Remaining Execution Time

    JFrog Workers now supports the function context.getRemainingExecutionTime(), which allows you to get the remaining number of milliseconds before a Worker execution time out.

  • Trace ID Displayed in Workers Troubleshooting

    Workers Troubleshooting now displays the trace ID of the event that triggered the Worker execution.

  • Updated Artifactory Worker Events

    Updated the following Worker Events:

    • After Copy: The following fields are removed from the Sample Payload:

      contentLength, trustServerChecksums, servletContextUrl, skipJarIndexing and disableRedirect.

    • After Delete: The following field is removed from the Sample Payload:

      headers

    • After Property Create: The following fields are removed from the Sample Payload:

      contentLength, trustServerChecksums, servletContextUrl, skipJarIndexing, disableRedirect and headers.

    • After Move: The following fields are removed from the Sample Payload:

      contentLength, trustServerChecksums, servletContextUrl, skipJarIndexing and disableRedirect.

    • Before Move: The following fields are removed from the Sample Payload:

      contentLength, trustServerChecksums, servletContextUrl, skipJarIndexing and disableRedirect.

JFrog Workers 1.158 SaaS

Released: 21 August, 2025

Highlights

  • Support for Non-Secret Properties

    JFrog Workers now supports adding non-secret Worker properties, allowing you to configure Workers.

  • Error Location Appears in Execution Logs

    JFrog Workers now displays the location of an error in the Worker’s execution logs, instead of in the execution error message.

JFrog Workers 1.153 SaaS

Released: 28 July, 2025

Highlights

  • New Worker Event: Before Token Expiry

    JFrog now supports creating event-driven Workers to trigger before a token expires. For more information, see Before Token Expiry Worker Code Sample.

  • Get Worker Code Samples with Worker Code Gallery

    The JFrog Platform now supports populating new Workers with GitHub code samples, directly from the JFrog Platform WebUI. For more information, see Configure Workers in the UI.

  • Workers Logs Enhancements

    Added additional log tabs to distinguish between internal execution calls, external HTTP request logs, and Platform HTTP request logs.

  • Rerun Worker Runs

    The JFrog Platform now supports a Rerun feature to troubleshoot Worker runs. For more information, see Workers Troubleshooting.

  • Support for Setting Max Payload

    JFrog Workers now supports overriding the 100 KB default body size for Workers by setting the parameter worker.execution.limits.jsonPayloadLimitKB in the Workers Configuration YAML file to the desired value.

JFrog Workers 1.133 SaaS

Released: 2 April, 2025

Highlights

  • Updated Type Definitions for Event-Driven Workers' Response

    Refined TypeScript type definitions for event-driven workers' response to improve the developer experience.

  • New Worker Event: Before Token Expiry

    JFrog now supports creating event-driven workers to trigger before a token expires. Learn more

  • Supported New Worker Events

    • Alt Response event is now supported.
    • Alt All Responses event is now supported.
    • Alt Remote Content event is now supported.
    • After Download Error event is now supported.
    • Before Download Request event is now supported.
    • Before Build Info Save event is now supported.

JFrog Workers 1.118 SaaS

Released: 15 January, 2025

Highlights

  • Support for Scheduled Workers

    JFrog now supports creating scheduled workers to trigger at predefined times or intervals, which you can define using Cron expressions. Learn more

  • Support for Triggering a Worker From a Webhook

    JFrog now supports configuring webhooks to trigger workers, allowing you to configure workers to events that are not pre-configured in JFrog Workers. Learn more

JFrog Workers 1.95 SaaS and Self-Managed

Released: 30 October, 2024

Highlights

  • Workers Now in General Availability

    JFrog has a new way to integrate and extend our platform execution workflows and functionality. We call it Workers - it seamlessly automates the JFrog Platform at scale. We are pleased to announce that JFrog Workers is now in general availability. Learn more.

  • Workers Events

    JFrog Workers are available for a growing number of pre-defined events. You can also create on-demand, HTTP-triggered Workers. Learn more.

  • Workers Installation for Self-Hosted Customers

    JFrog Workers can now be installed for Self-Hosted customers. For Workers version 1.95, both Artifactory and Workers must be deployed in Kubernetes. Learn more.


Did this page help you?