<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">Nov 24th, 2025</span>
    </div>
    <div class="change-area">
      <p>We have added a brand new Product Duplication resource to our API. This will allow a product to be duplicated, as well as its prices, variations and image.</p>
      
      <h2>Summary of the changed endpoints</h2>
			<p>The Products resource includes the following endpoints:</p>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#duplicateProduct">POST /api/v2/products/{id}/duplicate</a></li>
			</ul>
      
      <p>If you have any questions or comments, feel free to let us know in <a href="https://devcommunity.pipedrive.com/">the Developer’s Community</a>.</p>

  </div>
</div>
`}</HTMLBlock>

<br />

{"product": ["API"], "features": ["Product Duplication”], "email_description": "We are introducing new Product Duplication API" }


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">Nov 24th, 2025</span>
    </div>
    <div class="change-area">
      <p>We have added a brand new Product Duplication resource to our API. This will allow a product to be duplicated, as well as its prices, variations and image.</p>
      
      <h2>Summary of the changed endpoints</h2>
			<p>The Products resource includes the following endpoints:</p>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#duplicateProduct">POST /api/v2/products/{id}/duplicate</a></li>
			</ul>
      
      <p>If you have any questions or comments, feel free to let us know in <a href="https://devcommunity.pipedrive.com/">the Developer’s Community</a>.</p>

  </div>
</div>


Introducing new Product Duplication API

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">Nov 24th, 2025</span>
    </div>
    <div class="change-area">
      <p>Added a new query parameter to the <code>GET /api/v2/persons</code> API. If supplied, only persons linked to the specified deal are returned.</p>
      
      <h2>Summary of the changed endpoints</h2>
			<p>The new option was added to the following endpoint:</p>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Persons#getPersons">GET /api/v2/persons</a></li>
			</ul>
      
      <p>If you have any questions or comments, feel free to let us know in <a href="https://devcommunity.pipedrive.com/">the Developer’s Community</a>.</p>

  </div>
</div>
`}</HTMLBlock>

<br />

{"product": ["API"], "features": ["Persons”], "email_description": "We are adding deal_id parameter to GET /api/v2/persons" }


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">Nov 24th, 2025</span>
    </div>
    <div class="change-area">
      <p>Added a new query parameter to the <code>GET /api/v2/persons</code> API. If supplied, only persons linked to the specified deal are returned.</p>
      
      <h2>Summary of the changed endpoints</h2>
			<p>The new option was added to the following endpoint:</p>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Persons#getPersons">GET /api/v2/persons</a></li>
			</ul>
      
      <p>If you have any questions or comments, feel free to let us know in <a href="https://devcommunity.pipedrive.com/">the Developer’s Community</a>.</p>

  </div>
</div>


Introducing deal_id parameter for GET /api/v2/persons endpoint

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">Feb 1st, 2026</span>
    </div>
    <div class="change-area">
      
      <h2>Deprecation of Channels API</h2>
      <p>We are deprecating the Channel API to concentrate on developing the next generation of our CRM. All conversation data will remain preserved — any existing messages linked to deals or other entities will continue to be available in your account as notes, ensuring your communication history is not lost.</p>
      
      <h2>What will change?</h2>
      <p>We are deprecating Channel API endpoints (listed below). These endpoints will remain accessible until <b>February 1st, 2026</b>.</p>
      
      <h3>Deprecated endpoints:</h3>
      
      <ul>
        <li><code>POST /v1/channels</code></li>
        <li><code>POST /v1/channels/messages/receive</code></li>
        <li><code>DELETE /v1/channels/{id}</code></li>
        <li><code>DELETE /v1/channels/{channel-id}/conversations/{conversation-id}</code></li>
      </ul>
      
      <h2>Who is affected?</h2>
      <p>If you currently use the Omnichannel API beta, you'll need to transition to an alternative solution before deprecation date to avoid any service disruptions.</p>
      
			<p>If you have any questions or comments, feel free to let us know in <a href="https://devcommunity.pipedrive.com/">the Developer's Community</a>.</p>

          
  </div>
</div>
`}</HTMLBlock>

<br />

{"product": ["API"], "features": ["Channels API”], "email_description": "We are deprecating Channels API" }

Deprecation of Channels API


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">Feb 1st, 2026</span>
    </div>
    <div class="change-area">
      
      <h2>Deprecation of Channels API</h2>
      <p>We are deprecating the Channel API to concentrate on developing the next generation of our CRM. All conversation data will remain preserved — any existing messages linked to deals or other entities will continue to be available in your account as notes, ensuring your communication history is not lost.</p>
      
      <h2>What will change?</h2>
      <p>We are deprecating Channel API endpoints (listed below). These endpoints will remain accessible until <b>February 1st, 2026</b>.</p>
      
      <h3>Deprecated endpoints:</h3>
      
      <ul>
        <li><code>POST /v1/channels</code></li>
        <li><code>POST /v1/channels/messages/receive</code></li>
        <li><code>DELETE /v1/channels/{id}</code></li>
        <li><code>DELETE /v1/channels/{channel-id}/conversations/{conversation-id}</code></li>
      </ul>
      
      <h2>Who is affected?</h2>
      <p>If you currently use the Omnichannel API beta, you'll need to transition to an alternative solution before deprecation date to avoid any service disruptions.</p>
      
			<p>If you have any questions or comments, feel free to let us know in <a href="https://devcommunity.pipedrive.com/">the Developer's Community</a>.</p>

          
  </div>
</div>


Breaking change: Deprecation of Channels API

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">Oct 1st, 2025</span>
    </div>
    <div class="change-area">
      <p>We have added new bulk operation endpoints to our Deal Products API. These new endpoints allow you to efficiently manage multiple products attached to deals in a single request, enabling streamlined deal composition and product management workflows. </p>
      
      <h2>Summary of the changed endpoints</h2>
			<p>The Deal Products bulk operations include the following endpoints:</p>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#addManyDealProducts">POST /api/v2/deals/{id}/products/bulk</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#deleteManyDealProducts">DELETE /api/v2/deals/{id}/products </a></li>
			</ul>
      
      <p>If you have any questions or comments, feel free to let us know in <a href="https://devcommunity.pipedrive.com/">the Developer’s Community</a>.</p>

  </div>
</div>
`}</HTMLBlock>

We are introducing new Deal Products bulk operations API endpoints


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">Oct 1st, 2025</span>
    </div>
    <div class="change-area">
      <p>We have added new bulk operation endpoints to our Deal Products API. These new endpoints allow you to efficiently manage multiple products attached to deals in a single request, enabling streamlined deal composition and product management workflows. </p>
      
      <h2>Summary of the changed endpoints</h2>
			<p>The Deal Products bulk operations include the following endpoints:</p>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#addManyDealProducts">POST /api/v2/deals/{id}/products/bulk</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#deleteManyDealProducts">DELETE /api/v2/deals/{id}/products </a></li>
			</ul>
      
      <p>If you have any questions or comments, feel free to let us know in <a href="https://devcommunity.pipedrive.com/">the Developer’s Community</a>.</p>

  </div>
</div>


Introducing new Deal Products bulk operations API

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">Oct 1st, 2025</span>
    </div>
    <div class="change-area">
      <p>Added a new query parameter to the API v2 that allows sorting products within deals. Users can now sort products by their order number when fetching them.</p>
      
      <h2>Summary of the changed endpoints</h2>
			<p>The new option was added to the following endpoint:</p>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealProducts">GET /api/v2/deals/{id}/products</a></li>
			</ul>
      
      <p>If you have any questions or comments, feel free to let us know in <a href="https://devcommunity.pipedrive.com/">the Developer’s Community</a>.</p>

  </div>
</div>
`}</HTMLBlock>

We are introducing order_nr as new sorting query parameter for Products API v2


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">Oct 1st, 2025</span>
    </div>
    <div class="change-area">
      <p>Added a new query parameter to the API v2 that allows sorting products within deals. Users can now sort products by their order number when fetching them.</p>
      
      <h2>Summary of the changed endpoints</h2>
			<p>The new option was added to the following endpoint:</p>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealProducts">GET /api/v2/deals/{id}/products</a></li>
			</ul>
      
      <p>If you have any questions or comments, feel free to let us know in <a href="https://devcommunity.pipedrive.com/">the Developer’s Community</a>.</p>

  </div>
</div>


Introducing new sorting parameter for Products API

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">August 25th, 2025</span>
    </div>
    <div class="change-area">
      <p>We have added a brand new Product Images resource to our API.</p>
			<p>Product Images represent the image associated with the Product. Each product can have one image to represent it better visually. </p>
      
      <h2>Summary of the new endpoints</h2>
      <p>The Installments resource includes the following endpoints:</p>
      
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#getProductImage" target="_blank"><code>GET /api/v2/products/{id}/images</code></a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#uploadProductImage" target="_blank"><code>POST /api/v2/products/{id}/images</code></a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#updateProductImage" target="_blank"><code>PUT /api/v2/products/{id}/images</code></a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#deleteProductImage" target="_blank"><code>DELETE/api/v2/products/{id}/images</code></a></li>
      </ul>  
      
      <h2>Additional resources:</h2>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1">API Reference</a></li>
      </ul>      
      
      <p>If you have any questions or comments, feel free to let us know in <a href="https://devcommunity.pipedrive.com/">the Developer’s Community</a>.</p>

  </div>
</div>
`}</HTMLBlock>

{"product": ["API"], "features": ["Product Images”], "email_description": "We are introducing new Product Images API" }


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">August 25th, 2025</span>
    </div>
    <div class="change-area">
      <p>We have added a brand new Product Images resource to our API.</p>
			<p>Product Images represent the image associated with the Product. Each product can have one image to represent it better visually. </p>
      
      <h2>Summary of the new endpoints</h2>
      <p>The Installments resource includes the following endpoints:</p>
      
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#getProductImage" target="_blank"><code>GET /api/v2/products/{id}/images</code></a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#uploadProductImage" target="_blank"><code>POST /api/v2/products/{id}/images</code></a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#updateProductImage" target="_blank"><code>PUT /api/v2/products/{id}/images</code></a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#deleteProductImage" target="_blank"><code>DELETE/api/v2/products/{id}/images</code></a></li>
      </ul>  
      
      <h2>Additional resources:</h2>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1">API Reference</a></li>
      </ul>      
      
      <p>If you have any questions or comments, feel free to let us know in <a href="https://devcommunity.pipedrive.com/">the Developer’s Community</a>.</p>

  </div>
</div>


Introducing new Product Images API

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">September 21st, 2025</span>
    </div>
    <div class="change-area">
      <h2>What is changing?</h2>
			<p>From <b>Sep 21, 2025</b> we are changing the size limit of the activity note field for <code>POST  v1/activities</code> request to be <b>100kb</b>.</p>

      <h2>Why is it changing?</h2>
			<p>We’re adding a 100 KB cap to activity notes to keep the database lean, prevent oversized payloads, and make Activities consistent with the limits already used for other entities.</p>

      <p>If you have any questions or comments, feel free to let us know in <a href="https://devcommunity.pipedrive.com/">the Developer’s Community</a>.</p>

  </div>
</div>
`}</HTMLBlock>

We are changing the  activities notes size limit POST v1/activities endpoint


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">September 21st, 2025</span>
    </div>
    <div class="change-area">
      <h2>What is changing?</h2>
			<p>From <b>Sep 21, 2025</b> we are changing the size limit of the activity note field for <code>POST  v1/activities</code> request to be <b>100kb</b>.</p>

      <h2>Why is it changing?</h2>
			<p>We’re adding a 100 KB cap to activity notes to keep the database lean, prevent oversized payloads, and make Activities consistent with the limits already used for other entities.</p>

      <p>If you have any questions or comments, feel free to let us know in <a href="https://devcommunity.pipedrive.com/">the Developer’s Community</a>.</p>

  </div>
</div>


Breaking change: updating activities note field limit sizing for POST v1/activities

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">June 30th, 2025</span>
    </div>
    <div class="change-area">
      <p>We’ve identified an issue where the v2 user webhooks are deviating from the documented specification. According to our <a href="https://pipedrive.readme.io/docs/guide-for-webhooks-v2" target="_blank">Webhooks v2 documentation</a>, the <code>timestamp</code> field in the event meta object should be an RFC 3339 formatted timestamp (e.g., "2025-01-01T00:00:00.000Z"). However, the current implementation returns timestamps as UNIX timestamps (seconds since 1970) instead.</p>
      
     <p>On June 30th this behaviour will be rectified to reflect our documentation and user webhooks meta timestamp will be switched to RFC 3339 format.</p>
      
      <h2>What does it mean for me?</h2>

			<p>If you are consuming v2 user webhooks and rely on the <code>timestamp</code> field in the event meta object, make sure your application can process the updated RFC 3339 format. This change only affects v2 <b>user</b> webhooks — all other v2 webhooks (including activity, deal, lead, note, organization, person, pipeline, product, and stage) are already using the correct timestamp format and are not impacted by this fix.</p>

      <h2>Additional resources:</h2>
      <ul>
        <li><a href="https://pipedrive.readme.io/docs/guide-for-webhooks-v2">Guide for Webhooks v2</a></li>
      </ul>      
      
      <p>If you have any questions or comments, feel free to let us know in <a href="https://devcommunity.pipedrive.com/">the Developer’s Community</a>.</p>

  </div>
</div>
`}</HTMLBlock>


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">June 30th, 2025</span>
    </div>
    <div class="change-area">
      <p>We’ve identified an issue where the v2 user webhooks are deviating from the documented specification. According to our <a href="https://pipedrive.readme.io/docs/guide-for-webhooks-v2" target="_blank">Webhooks v2 documentation</a>, the <code>timestamp</code> field in the event meta object should be an RFC 3339 formatted timestamp (e.g., "2025-01-01T00:00:00.000Z"). However, the current implementation returns timestamps as UNIX timestamps (seconds since 1970) instead.</p>
      
     <p>On June 30th this behaviour will be rectified to reflect our documentation and user webhooks meta timestamp will be switched to RFC 3339 format.</p>
      
      <h2>What does it mean for me?</h2>

			<p>If you are consuming v2 user webhooks and rely on the <code>timestamp</code> field in the event meta object, make sure your application can process the updated RFC 3339 format. This change only affects v2 <b>user</b> webhooks — all other v2 webhooks (including activity, deal, lead, note, organization, person, pipeline, product, and stage) are already using the correct timestamp format and are not impacted by this fix.</p>

      <h2>Additional resources:</h2>
      <ul>
        <li><a href="https://pipedrive.readme.io/docs/guide-for-webhooks-v2">Guide for Webhooks v2</a></li>
      </ul>      
      
      <p>If you have any questions or comments, feel free to let us know in <a href="https://devcommunity.pipedrive.com/">the Developer’s Community</a>.</p>

  </div>
</div>


Bug fix in v2 user webhooks payload

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">Apr 22nd, 2025</span>
    </div>
    <div class="change-area">
      <p>We’ve identified an issue where the following endpoints were returning data for entities that had already been deleted:</p>
      
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Persons#getPersons" target="_blank"><code>GET /api/v2/persons</code></a></li>
				<li><a href="https://developers.pipedrive.com/docs/api/v1/Organizations#getOrganizations" target="_blank"><code>GET /api/v2/organizations</code></a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Activities#getActivities" target="_blank"><code>GET /api/v2/activities</code></a></li>
      </ul>  
      
     <p>These endpoints now correctly return only active (non-deleted) entities in their responses.</p>
      
      <h2>What does it mean for me?</h2>

			<p>If you were filtering or processing data returned by these endpoints, you may now notice a smaller or more accurate result set, as deleted entities are no longer included.</p>

      <h2>Additional resources:</h2>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1">API Reference</a></li>
      </ul>      
      
      <p>If you have any questions or comments, feel free to let us know in <a href="https://devcommunity.pipedrive.com/">the Developer’s Community</a>.</p>

  </div>
</div>
`}</HTMLBlock>

We’ve identified an issue where the following endpoints were returning data for entities that had already been deleted


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">Apr 22nd, 2025</span>
    </div>
    <div class="change-area">
      <p>We’ve identified an issue where the following endpoints were returning data for entities that had already been deleted:</p>
      
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Persons#getPersons" target="_blank"><code>GET /api/v2/persons</code></a></li>
				<li><a href="https://developers.pipedrive.com/docs/api/v1/Organizations#getOrganizations" target="_blank"><code>GET /api/v2/organizations</code></a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Activities#getActivities" target="_blank"><code>GET /api/v2/activities</code></a></li>
      </ul>  
      
     <p>These endpoints now correctly return only active (non-deleted) entities in their responses.</p>
      
      <h2>What does it mean for me?</h2>

			<p>If you were filtering or processing data returned by these endpoints, you may now notice a smaller or more accurate result set, as deleted entities are no longer included.</p>

      <h2>Additional resources:</h2>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1">API Reference</a></li>
      </ul>      
      
      <p>If you have any questions or comments, feel free to let us know in <a href="https://devcommunity.pipedrive.com/">the Developer’s Community</a>.</p>

  </div>
</div>


Bug fix in data returned by three endpoints

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">Apr 22nd, 2025</span>
    </div>
    <div class="change-area">
      <p>We are introducing the possibility of initiating a conversion between Deals and Leads.</p>
      
      <h2>What is being added?</h2>
      <p>Four new endpoints to enable conversion between Deals and Leads have been released. Those endpoints allow the initialization of a conversion and getting the status of an ongoing conversion.</p>
      
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#convertDealToLead" target="_blank"><code>POST /api/v2/deals/{id}/convert/lead</code></a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#convertLeadToDeal" target="_blank"><code>POST /api/v2/leads/{id}/convert/deal</code></a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealConversionStatus" target="_blank"><code>GET /api/v2/deals/{id}/convert/status/{conversion_id}</code></a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Leads#getLeadConversionStatus" target="_blank"><code>GET /api/v2/leads/{id}/convert/status/{conversion_id}</code></a></li>
      </ul>  
      
      <h2>Additional resources:</h2>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1">API Reference</a></li>
      </ul>      
      
      <p>If you have any questions or comments, feel free to let us know in <a href="https://devcommunity.pipedrive.com/">the Developer’s Community</a>.</p>

  </div>
</div>
`}</HTMLBlock>

New endpoints to convert Deals to Leads and Leads to Deals


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">Apr 22nd, 2025</span>
    </div>
    <div class="change-area">
      <p>We are introducing the possibility of initiating a conversion between Deals and Leads.</p>
      
      <h2>What is being added?</h2>
      <p>Four new endpoints to enable conversion between Deals and Leads have been released. Those endpoints allow the initialization of a conversion and getting the status of an ongoing conversion.</p>
      
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#convertDealToLead" target="_blank"><code>POST /api/v2/deals/{id}/convert/lead</code></a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#convertLeadToDeal" target="_blank"><code>POST /api/v2/leads/{id}/convert/deal</code></a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealConversionStatus" target="_blank"><code>GET /api/v2/deals/{id}/convert/status/{conversion_id}</code></a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Leads#getLeadConversionStatus" target="_blank"><code>GET /api/v2/leads/{id}/convert/status/{conversion_id}</code></a></li>
      </ul>  
      
      <h2>Additional resources:</h2>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1">API Reference</a></li>
      </ul>      
      
      <p>If you have any questions or comments, feel free to let us know in <a href="https://devcommunity.pipedrive.com/">the Developer’s Community</a>.</p>

  </div>
</div>


Contents

Changelog

Announced changes

Subscribe to our Changelog

Subscribe to our Changelog

Subscribe to our
Changelog