What's the current release?
See Release notes
Where do I find my current version?
Sign in to the TrustBuilder Admin Portal. The page footer just below your username provides the version number for the tenant you are currently working in.
What's the naming convention for updates?
TrustBuilder names its releases according to Semantic Versioning 2.0.0:
<major version>.<minor version>.<update>
TrustBuilder releases a new <major version> when new functionality is introduced that breaks one or more APIs. A <major version> release may therefor introduce backward-incompatible changes.
TrustBuilder releases a new <minor version> when a new module is introduced with new APIs. A new <minor version> may contain additional APIs and non-breaking updates of existing APIs.
TrustBuilder releases a new <update> version for UX-level updates, backward-compatible API updates, bug fixes and security fixes.
For <minor version> releases and <update> releases, TrustBuilder strives to update Production-level APIs in a backward-compatible way:
Updated APIs may add optional fields and parameters;
Updated APIs do not change the semantics and the meaning of existing fields and parameters;
Updated APIs are not more restrictive in the applying validation rules, except for reasons of security (e.g. a discovered software vulnerability) or overall stability (e.g. a discovered weakness in handling an edge case).
TrustBuilder may from time to time require that updated APIs include breaking changes and imply database migrations. Such releases are marked as a new <major version> and a new API version.
How often does TrustBuilder release new versions?
TrustBuilder typically releases <update> versions twice a month and include:
New API endpoints and updated API endpoints
Bug and Security Fixes
New app integrations
TrustBuilder typically releases <minor version> twice a year and include:
New functional domains
What's the difference between Preview and Production releases?
A Preview release contain features, enhancements, fixes, and integrations that are deployed to Preview tenants only. A Preview tenant is optional and available upon request.
A Production release contain features, enhancements, fixes, and integrations that are made available to customer tenants. Customer tenants may be labelled development, acceptance and production by the customer. A Production release is only deployed to a customer-production tenant, if and only if accepted by the customer.
Most features and enhancements that are introduced in a Preview release are typically made available in the Production release during the next deployment date.
Can we test against new releases?
Since new versions may impact customer’s use of the TrustBuilder platform, the following provisions are offered:
<Critical updates>: A Critical Update corrects the TrustBuilder platform to enable it to meet the security level and operational service level targets. Critical Updates generally do not require changes on customers’ side to be made. TrustBuilder installs a Critical Update first in Preview environments and customers are invited to regression test their own services against the Critical Update. At its sole discretion, however, TrustBuilder is entitled to choose the moment, including any time before tests by the customers are finalised, that the Critical Update is installed in production environments.
<Minor versions> and <updates>: TrustBuilder installs an <update> or a <minor version> first in Preview environments and customers are invited to test the integration compatibility of their applications against the <update> or <minor version>. Customers have 10 business days to conduct such regression tests, after which and in the absence of blocking issues or specific postponement requests, TrustBuilder is entitled to install the <update> or <minor version> in production environments. In case a blocking issue would surface after an <update>, a customer can request TrustBuilder to undo the installation of the <update> in their environment.
<major versions>: A <major version> adds new functionality to the TrustBuilder platform and may require one or more changes on Customers’ side, including data migrations. TrustBuilder installs a <major version> first in a Preview environment and invites customers to adapt their applications to benefit from the <major version>. TrustBuilder announces the end-of-life date of the prior <major version> which is typically several years in the future.