This task is about updating CPaaS. You should read the CPaaS changelog and make sure that between our current version and the new one there are no "Breaking changes". Changelog should inform you about those breaking changes and provide proper documentation on a migration plan in case we have breaking changes. Updating CPaaS is as easy as sending a MR to cpaas-products/products-configs updating the version line.

This will trigger internal jobs to update our CPaaS and Jenkins instance. If everything goes well, after merge, we should receive an email with the update status and the Jenkins url.

Here is an example.

Note: Keep in mind this is not our repository and many products are here. So follow the official CPaaS documentation, section "Upgrade the CPaaS Version Used By a Product", and prefix the commit with the "sandboxed-containers:" for better organization.