# 2025 12 18 release notes (core)

## Release summary <a href="#release-summary" id="release-summary"></a>

This page summarises items scheduled for the following release to the Patchworks Core Production environment.&#x20;

| Release version | Release date                 |
| --------------- | ---------------------------- |
| v2025-12-18     | Thursday 18th December (a.m) |

New features, updates, and enhancements of note are summarised by product area, below:

* [​Process flows](#process-flows)
* [Blueprints](#blueprints)
* [Virtual environments](#virtual-environments)
* [Connector builder](#connector-builder)

## Process flows <a href="#process-flows" id="process-flows"></a>

<table><thead><tr><th width="180">Type<select><option value="edbc33cea7f34e16b3a205c7a65c3172" label="New" color="blue"></option><option value="d8457d8925c74fab90fa132d141b764b" label="Change" color="blue"></option><option value="030babd6286a4fe19214da74af9afb98" label="Enhancement" color="blue"></option><option value="9a29ee576f43448f9b1623baca59c3db" label="Bug" color="blue"></option><option value="L09Gy6z2y7VD" label="Breaking change" color="blue"></option></select></th><th width="426">Summary</th><th>Ref #</th></tr></thead><tbody><tr><td><span data-option="9a29ee576f43448f9b1623baca59c3db">Bug</span></td><td><strong>Cache retention</strong><br>Fixed an issue where the retention period set for caches (of any type) was not always respected. <br><img src="/files/j1i0cLEEKzAu7FBcGQmn" alt="" data-size="line"> <a href="/pages/02CKnvBeSizeNM08Vhih">Caches</a></td><td>CPT-5019</td></tr><tr><td><span data-option="9a29ee576f43448f9b1623baca59c3db">Bug</span></td><td><strong>Editing an existing deployment</strong><br>Fixed an issue where choosing to edit an existing deployment via the view deployments modal was not working as expected.<br><img src="/files/j1i0cLEEKzAu7FBcGQmn" alt="" data-size="line"> <a href="/pages/QJn3I6Ens3cFWBGOJZMh">Deploying a single process flow to a virtual environment</a></td><td>CPT-5057</td></tr></tbody></table>

## Blueprints

<table><thead><tr><th width="180">Type<select><option value="edbc33cea7f34e16b3a205c7a65c3172" label="New" color="blue"></option><option value="d8457d8925c74fab90fa132d141b764b" label="Change" color="blue"></option><option value="030babd6286a4fe19214da74af9afb98" label="Enhancement" color="blue"></option><option value="9a29ee576f43448f9b1623baca59c3db" label="Bug" color="blue"></option><option value="L09Gy6z2y7VD" label="Breaking change" color="blue"></option></select></th><th width="426">Summary</th><th>Ref #</th></tr></thead><tbody><tr><td><span data-option="9a29ee576f43448f9b1623baca59c3db">Bug</span></td><td><strong>Blueprint process flows calling child flows</strong><br>When a process flow includes a run process flow shape to call a 'child' flow and is added to a private blueprint, the associated 'child' flow is also added - this happens automatically. In this release, we have fixed an issue where 'child' process flows installed from a blueprint were installed with missing steps. <br><img src="/files/j1i0cLEEKzAu7FBcGQmn" alt="" data-size="line"> <a href="/pages/E5shawOmOVLcH0FYZEWm">Building a private blueprint</a></td><td>CPT-5037</td></tr><tr><td><span data-option="9a29ee576f43448f9b1623baca59c3db">Bug</span></td><td><strong>Blueprint labels</strong><br>Fixed an issue where labels applied to a blueprint (and to process flows within blueprints) did not persist when the blueprint was installed. <br><br>This change is not retrospective. If you are installing a blueprint built before this release, labels should be checked and re-applied where necessary.<br><img src="/files/j1i0cLEEKzAu7FBcGQmn" alt="" data-size="line"> <a href="/pages/E5shawOmOVLcH0FYZEWm">Building a private blueprint</a></td><td>CPT-5038</td></tr></tbody></table>

## Virtual environments

<table><thead><tr><th width="180">Type<select><option value="edbc33cea7f34e16b3a205c7a65c3172" label="New" color="blue"></option><option value="d8457d8925c74fab90fa132d141b764b" label="Change" color="blue"></option><option value="030babd6286a4fe19214da74af9afb98" label="Enhancement" color="blue"></option><option value="9a29ee576f43448f9b1623baca59c3db" label="Bug" color="blue"></option><option value="L09Gy6z2y7VD" label="Breaking change" color="blue"></option></select></th><th width="426">Summary</th><th>Ref #</th></tr></thead><tbody><tr><td><span data-option="030babd6286a4fe19214da74af9afb98">Enhancement</span></td><td><strong>Overview display</strong><br>The layout of the virtual environments overview page has been improved to ensure compatibility for mobile devices. <br><img src="/files/j1i0cLEEKzAu7FBcGQmn" alt="" data-size="line"> <a href="/pages/mOQQBxbQqCqhuToig0h0">The virtual environments overview page</a></td><td>CPT-4466</td></tr></tbody></table>

## Connector builder

<table><thead><tr><th width="180">Type<select><option value="edbc33cea7f34e16b3a205c7a65c3172" label="New" color="blue"></option><option value="d8457d8925c74fab90fa132d141b764b" label="Change" color="blue"></option><option value="030babd6286a4fe19214da74af9afb98" label="Enhancement" color="blue"></option><option value="9a29ee576f43448f9b1623baca59c3db" label="Bug" color="blue"></option><option value="L09Gy6z2y7VD" label="Breaking change" color="blue"></option></select></th><th width="426">Summary</th><th>Ref #</th></tr></thead><tbody><tr><td><span data-option="030babd6286a4fe19214da74af9afb98">Enhancement</span></td><td><strong>Authentication variables unlocked</strong><br>Previously, applying an authentication method for a connector (<code>OAuth 2</code>, <code>basic</code>, etc.) added default authentication variables in a locked state. Now, all default authentication variables are unlocked and can be edited, if required. <br><img src="/files/j1i0cLEEKzAu7FBcGQmn" alt="" data-size="line"> <a href="/pages/d0W9xUHtNUGOq53xmDvN">Connector builder - authentication</a></td><td>CPT-5018</td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://doc.wearepatchworks.com/product-documentation/release-information/core-release-notes/2025-12-18-release-notes-core.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.