| copyright |
|
||
|---|---|---|---|
| lastupdated | 2026-05-08 | ||
| keywords | IBM Cloud Continuous Delivery, release notes, CD | ||
| subcollection | ContinuousDelivery | ||
| content-type | release-note |
{{site.data.keyword.attribute-definition-list}}
{: #cd-relnotes}
Use these release notes to learn about the latest updates to {{site.data.keyword.contdelivery_full}} that are grouped by date. Release notes are available for a minimum of three years. {: shortdesc}
{: #ContinuousDelivery-apr1026} {: release-note} IBM Cloud {{site.data.keyword.contdelivery_short}}, is discontinued in the following regions:
- Osaka (jp-osa)
- Madrid (eu-es)
{: #ContinuousDelivery-mar3026} {: release-note} IBM Cloud {{site.data.keyword.contdelivery_short}}, Code Risk Analyzer and {{site.data.keyword.DRA_short}} end of service in select regions. : The services will no longer be available in the Madrid (eu-es) and Osaka (jp-osa) regions on 10 April 2026
If you have the {{site.data.keyword.contdelivery_short}} service in Madrid (eu-es) or Osaka (jp-osa), we provide a migration guide to help you with:
- Migrate Git Repos and Issue Tracking projects across regions via direct transfer (GitLab feature).
- Copy toolchains (including Tekton pipelines) to another region using the migration guide
- Securely export and move secrets to Secrets Manager
{: #ContinuousDelivery-feb1226} {: release-note}
IBM Cloud {{site.data.keyword.contdelivery_short}} deprecation in select regions. : The service will no longer be available in the following regions: au-syd, ca-mon, ca-tor, eu-es, jp-osa and us-east. We recognize that changes like these may impact your current setup, and our goal is to make this transition as smooth and predictable as possible, with clear guidance and tools to help you migrate confidently and without disruption.
Code Risk Analyzer and {{site.data.keyword.DRA_short}} service deprecation. : The service will no longer be available in all regions. We recognize that changes like these may impact your current setup, and our goal is to make this transition as smooth and predictable as possible, with clear guidance and tools to help you migrate confidently and without disruption.
End of Marketing: 12 June 2026 - After this date, customers will no longer be able to create new resources in the affected regions. However, if a region has no active usage before this date, the {{site.data.keyword.contdelivery_short}}, Code Risk Analyzer or {{site.data.keyword.DRA_short}} service in that region may be discontinued earlier and stop accepting new resource creation. {: important}
End of Service: 12 February 2027 - The date when {{site.data.keyword.contdelivery_short}}, Code Risk Analyzer and {{site.data.keyword.DRA_short}} services will no longer be available in the affected regions. However, if a region has no active usage before this date, or if all customers in the region complete their migrations early, the services in that region may be discontinued earlier. {: important}
If you have the {{site.data.keyword.contdelivery_short}} service in an affected region, we provide a migration guide to help you with:
- Migrate Git Repos and Issue Tracking projects across regions via direct transfer (GitLab feature).
- Copy toolchains (including Tekton pipelines) to another region using the migration guide
- Securely export and move secrets to Secrets Manager
Customers using affected regions or features must plan and complete migration by 12 February 2027 to ensure uninterrupted service. Please note: In regions where there is no active usage of the service, or where customers have already completed their migrations before the scheduled end‑of‑service date, the service may be closed earlier than previously communicated. If any regional changes are planned, customers will receive advance notification to ensure they have sufficient time to prepare and take any necessary actions. {: important}
{: #ContinuousDelivery-aug0125} {: release-note}
{{site.data.keyword.contdelivery_full}} is now available in the Montreal Region. : Each location has three different data centers and provides a full cloud service stack to enable high availability, redundancy, and geographical dispersion.
Montreal (ca-mon) is a limited-availability region and not generally available. {: important}
{: #ContinuousDelivery-apr2925} {: release-note}
Private worker installation no longer supports the Operator Lifecycle Manager (OLM) framework. : The Operator Lifecycle Manager (OLM) framework is no longer supported for private worker installation.
{: #ContinuousDelivery-sep2524} {: release-note}
The {{site.data.keyword.contdelivery_short}} toolchain API method for generating bespoke toolchain events to {{site.data.keyword.en_short}}, POST /toolchains/:toolchain_id/events, is now generally available.
: The text_plain property of the request payload is changed from a string to a JSON object of the form {“content”: “string”}. The API is otherwise unchanged from the Beta.
: For more information, see Enabling event notifications for toolchains and the CD Toolchain API Docs{: external}.
{: #ContinuousDelivery-august2424} {: release-note}
{{site.data.keyword.gitrepos}} : Upgraded to GitLab 17.1.4{: external}.
{: #ContinuousDelivery-sep0624} {: release-note}
Enabling Direct Integration with an Existing Git Repository : Link a Continuous Delivery service and toolchain instance to a Git project for seamless integration, automating code deployment, and real-time collaboration. It is mandatory to link Continuous Delivery service and toolchain instance for creating a new project in the UI.
: For more information, see Link a Continuous Delivery service instance to a Git Project.
{: #ContinuousDelivery-09july2424} {: release-note}
{{site.data.keyword.gitrepos}} : Upgraded to GitLab 17.0.3{: external}.
{: #ContinuousDelivery-01july2424} {: release-note}
{{site.data.keyword.gitrepos}} : Upgraded to GitLab 16.11.5{: external}.
{: #ContinuousDelivery-june2424} {: release-note}
The {{site.data.keyword.contdelivery_short}} service Professional plan now supports consolidated billing of authorized users within enterprise account hierarchies. This feature ensures that authorized user emails are counted and billed only once across all {{site.data.keyword.contdelivery_short}} service instances in your enterprise and in a region, rather than being counted and billed separately for each instance. : For more information, see Consolidated billing.
{{site.data.keyword.deliverypipeline}} : Upgraded to Tekton Pipelines v0.59.2{: external}.
{: #ContinuousDelivery-feb1524} {: release-note}
{{site.data.keyword.deliverypipeline}} : The toolchain service can now be selected as a service reference when creating network zones under Context-based restrictions.
{: #ContinuousDelivery-jan0224} {: release-note}
The {{site.data.keyword.contdelivery_short}} toolchain API provides a new, beta method that you can use to generate bespoke (custom) toolchain events which the toolchain will forward to integrated instances of {{site.data.keyword.en_short}}. : For more information, see Enabling event notifications for toolchains and the CD Toolchain API Docs{: external}.
{: #ContinuousDelivery-dec0723} {: release-note}
{{site.data.keyword.gitrepos}} : Upgraded to GitLab 16.5.3{: external}.
{: #ContinuousDelivery-nov2423} {: release-note}
{{site.data.keyword.contdelivery_full}} is now available in the Madrid region. : Each location has three different data centers and provides a full cloud service stack to enable high availability, redundancy, and geographical dispersion.
{: #ContinuousDelivery-nov1623} {: release-note}
{{site.data.keyword.gitrepos}} : Upgraded to GitLab 16.4.2{: external}.
{: #ContinuousDelivery-nov0323} {: release-note}
{{site.data.keyword.gitrepos}} : Upgraded to GitLab 16.3.5{: external}.
{: #ContinuousDelivery-otc1923} {: release-note}
{{site.data.keyword.gitrepos}} : Upgraded to GitLab 16.2.8{: external}.
{: #ContinuousDelivery-otc0423} {: release-note}
{{site.data.keyword.gitrepos}} : Upgraded to GitLab 16.1.5{: external}.
{: #ContinuousDelivery-sep2723} {: release-note}
{{site.data.keyword.contdelivery_short}} toolchains APIs, SDKs, and Terraform now support looking up toolchains by name. : For more information, see the CD Toolchain API Docs{: external} and the Terraform IBM Cloud provider docs{: external}.
{: #ContinuousDelivery-sep1123} {: release-note}
{{site.data.keyword.gitrepos}} : Upgraded to GitLab 16.0.8{: external}.
: In GitLab 16.0, any personal, project, or group access token that does not have an expiration date{: external} will automatically have an expiration date set at one year.
{: #ContinuousDelivery-july1223} {: release-note}
{{site.data.keyword.gitrepos}} : Upgraded to GitLab 15.11.11{: external}.
{: #ContinuousDelivery-june1323} {: release-note}
{{site.data.keyword.gitrepos}} : Upgraded to GitLab 15.10.8{: external}.
{: #ContinuousDelivery-may1923} {: release-note}
{{site.data.keyword.gitrepos}} : Upgraded to GitLab 15.9.8{: external}.
{: #ContinuousDelivery-apr2023} {: release-note}
{{site.data.keyword.contdelivery_short}} toolchains are now integrated with the {{site.data.keyword.en_full}} service. : Enabling {{site.data.keyword.en_short}} for toolchains
{: #ContinuousDelivery-apr1023} {: release-note}
{{site.data.keyword.gitrepos}} : Upgraded to GitLab 15.8.5{: external}.
{: #ContinuousDelivery-feb2123} {: release-note}
Java, Node, and Python SDKs for toolchains and Tekton pipelines are now generally available. : Java SDK: github.com/IBM/continuous-delivery-java-sdk{: external}
: Node SDK: github.com/IBM/continuous-delivery-node-sdk{: external}
: Python SDK: github.com/IBM/continuous-delivery-python-sdk{: external}
{: #ContinuousDelivery-feb1323} {: release-note}
{{site.data.keyword.gitrepos}} : Upgraded to GitLab 15.7.6{: external}.
{: #ContinuousDelivery-jan1923} {: release-note}
{{site.data.keyword.gitrepos}} : Upgraded to GitLab 15.6.6{: external}.
{: #ContinuousDelivery-jan0923} {: release-note}
{{site.data.keyword.gitrepos}} : Upgraded to GitLab 15.6.3{: external}.
{: #ContinuousDelivery-dec1422} {: release-note}
The {{site.data.keyword.contdelivery_short}} service is now designated as {{site.data.keyword.cloud_notm}} for Financial Services Validated. : This designation does not apply to all of the tools that you can integrate into toolchains. For more information about which tool integrations and tools are designated as {{site.data.keyword.cloud_notm}} for Financial Services Validated when they are used with {{site.data.keyword.contdelivery_short}} toolchains, see Understanding tool integrations with {{site.data.keyword.cloud_notm}} for Financial Services.
: For more information about {{site.data.keyword.cloud_notm}} for Financial Services, see {{site.data.keyword.cloud_notm}} Framework for Financial Services.
{: #ContinuousDelivery-dec0722} {: release-note}
{{site.data.keyword.gitrepos}} : Upgraded to GitLab 15.5.5{: external}.
{: #ContinuousDelivery-dec0122} {: release-note}
The Terraform resources and data sources, Go SDKs, and HTTP APIs for toolchains and Tekton pipelines are now generally available. : Updates include a few breaking changes.
: The Terraform resources and data sources, Go SDKs, and HTTP APIs are now a generally available, fully supported feature.
: Read the release notes{: external}.
{: #ContinuousDelivery-nov1822} {: release-note}
The Beta Terraform resources and data sources, Go SDKs, and HTTP APIs are updated, including several breaking changes.
: Read the release notes{: external}.
{: #ContinuousDelivery-nov1622} {: release-note}
{{site.data.keyword.gitrepos}} : Upgraded to GitLab 15.4.4{: external}.
{: #ContinuousDelivery-nov0222} {: release-note}
{{site.data.keyword.gitrepos}} : Upgraded to GitLab 15.3.4{: external}.
{: #ContinuousDelivery-oct0622} {: release-note}
{{site.data.keyword.gitrepos}} : Upgraded to GitLab 15.2.5{: external}.
{: #ContinuousDelivery-oct0522} {: release-note}
The Beta Terraform resources and data sources, Go SDKs, and HTTP APIs are updated, including several breaking changes.
: Read the release notes{: external} .
{: #ContinuousDelivery-sept1622} {: release-note}
{{site.data.keyword.contdelivery_short}} service instances and toolchains that reside in Cloud Foundry orgs are no longer supported. : Services instances and toolchains that reside in resource groups remain fully supported.
{: #ContinuousDelivery-sept0822} {: release-note}
{{site.data.keyword.gitrepos}} : Upgraded to GitLab 15.1.6{: external}.
{: #ContinuousDelivery-july2222} {: release-note}
The Beta Terraform resources and data sources, Go SDKs, and HTTP APIs are now available for working with Toolchains and Tekton Pipelines. : Terraform resources and data sources: IBM-Cloud provider{: external}. : Go SDKs: Open-source repository (repo) continuous-delivery-go-sdk{: external}. : HTTP APIs: {{site.data.keyword.contdelivery_short}} Toolchain{: external} and {{site.data.keyword.contdelivery_short}} Tekton Pipeline{: external}.
Ask questions and provide feedback in the [#ask-your-question](https://ibm-devops-services.slack.com/archives/C5AHRCLHH){: external} Slack channel.
{: #ContinuousDelivery-july2022} {: release-note}
{{site.data.keyword.gitrepos}} : Upgraded to GitLab 15.0.4{: external}.
{: #ContinuousDelivery-july1222} {: release-note}
{{site.data.keyword.gitrepos}} : Upgraded to GitLab 14.10.5{: external}.
{: #ContinuousDelivery-july0822} {: release-note}
The Eclipse Orion {{site.data.keyword.webide}} feature in the {{site.data.keyword.contdelivery_full}} service is deprecated. : The {{site.data.keyword.contdelivery_short}} service does not provide a direct replacement.
: As of 8 August 2022, new toolchains will not include the {{site.data.keyword.webide}} as a default tool. You cannot create and add instances of the {{site.data.keyword.webide}} tool integration to existing toolchains. Existing instances of the {{site.data.keyword.webide}} continue to operate normally.
: As of 7 October 2022, the {{site.data.keyword.webide}} tool integration will be removed from existing toolchains and the associated data will be deleted. It is recommended that you export your data from your {{site.data.keyword.webide}} workspace before this date, or commit and push all of your outstanding changes into a Git repository.
{: #ContinuousDelivery-june3022} {: release-note}
Private workers can now be run in stand-alone mode. : Using {{site.data.keyword.deliverypipeline}} Private Workers in stand-alone mode.
Private workers can now be managed on a Satellite cluster, providing easier management of workers on {{site.data.keyword.redhat_openshift_full}} clusters by using the Operator Lifecycle Manager (OLM) framework. : Installing {{site.data.keyword.deliverypipeline}} Private Workers.
{: #ContinuousDelivery-june2322} {: release-note}
New toolchain template demonstrates how to use a pull-based deployment mechanism to continuously deploy Kubernetes resources to multiple clusters on IBM Cloud Satellite by using a Tekton pipeline. : Satellite Template{: external}.
{: #ContinuousDelivery-june1322} {: release-note}
{{site.data.keyword.gitrepos}} : Upgraded to GitLab 14.10.4{: external}.
{: #ContinuousDelivery-june0722} {: release-note}
Private information in {{site.data.keyword.contdelivery_short}} and toolchains can now be protected by the Customer Root Key as part of Bring Your Own Key. : Bring Your Own Key is available only in a professional plan.
{: #ContinuousDelivery-may2322} {: release-note}
{{site.data.keyword.gitrepos}} : Upgraded to GitLab 14.9.4{: external}.
{: #ContinuousDelivery-may1822} {: release-note}
New toolchain template demonstrates how to deploy a sample NodeJS application with Code Engine by using a Tekton pipeline. : Code Engine Template{: external}.
{: #ContinuousDelivery-may0522} {: release-note}
{{site.data.keyword.gitrepos}} : Upgraded to GitLab 14.8.5{: external}.
{: #ContinuousDelivery-mar0122} {: release-note}
{{site.data.keyword.gitrepos}} : Upgraded to GitLab 14.7.4{: external}.
{: #ContinuousDelivery-feb1722} {: release-note}
{{site.data.keyword.gitrepos}} : Upgraded to GitLab 14.6.4{: external}.
{: #ContinuousDelivery-jan2422} {: release-note}
{{site.data.keyword.gitrepos}} : Upgraded to GitLab 14.5.3{: external}.
{: #ContinuousDelivery-jan0722} {: release-note}
{{site.data.keyword.gitrepos}} : Upgraded to GitLab 14.4.4{: external}.
{: #ContinuousDelivery-nov3021} {: release-note}
{{site.data.keyword.contdelivery_full}} is now available in the Sao Paulo region. : Each location has three different data centers and provides a full cloud service stack to enable high availability, redundancy, and geographical dispersion.
{: #ContinuousDelivery-nov2921} {: release-note}
{{site.data.keyword.gitrepos}} : Upgraded to GitLab 14.4.2{: external}.
{: #ContinuousDelivery-nov0421} {: release-note}
{{site.data.keyword.gitrepos}} : Upgraded to GitLab 14.3.4{: external}.
{: #ContinuousDelivery-oct3121} {: release-note}
{{site.data.keyword.deliverypipeline}} : Upgraded to Tekton Pipelines v0.27.3{: external}.
{: #ContinuousDelivery-oct2121} {: release-note}
New in the DevSecOps reference implementation: : SonarQube scanning : Additional validations for image signing : Improvements to the getting-started experience
{: #ContinuousDelivery-oct0721} {: release-note}
New toolchain templates demonstrate release strategies : Rolling: Deploy a new release with no downtime by incrementally updating all the instances in a sequential manner. : Blue-Green: Deploy a new release to an environment identical to — and isolated from — current production for quicker rollbacks and ease of testing. : Canary: Deploy a new release incrementally to the production environment, gradually replacing the older version of the application with the newer one, gating increments with a test to reducing risks.
{: #ContinuousDelivery-sep3021} {: release-note}
{{site.data.keyword.deliverypipeline}} : Upgraded to Tekton Pipelines v0.27.2{: external}.
{: #ContinuousDelivery-jul0921} {: release-note}
{{site.data.keyword.contdelivery_full}} is now available in the Toronto Region. : Each location has three different data centers and provides a full cloud service stack to enable high availability, redundancy, and geographical dispersion.
{: #ContinuousDelivery-jun2921} {: release-note}
DevSecOps Reference Implementation : A complete SDLC following NIST Configuration Management controls that you can configure in a few clicks by using toolchain templates. The workflow will build, scan, test, and deploy your cloud-native applications while ensuring security and compliance goals are met and evidence is retained for any future audits. The workflow can be customized to leverage other enterprise tools or implement custom policies.
{: #ContinuousDelivery-may2421} {: release-note}
Code Risk Analyzer now scans Terraform : Misconfiguration of infrastructure and cloud service dependencies can put enterprise applications and data at risk. Now, Code Risk Analyzer looks for these issues by scanning Terraform Infrastructure as Code (IaC) files.
{: #ContinuousDelivery-apr3021} {: release-note}
{{site.data.keyword.contdelivery_full}} is now available in the Osaka region. : Each location has three different data centers and provides a full cloud service stack to enable high availability, redundancy, and geographical dispersion.
{: #ContinuousDelivery-mar3121} {: release-note}
{{site.data.keyword.contdelivery_full}} is now available in the Sydney region. : Each location has three different data centers and provides a full cloud service stack to enable high availability, redundancy, and geographical dispersion.
{: #ContinuousDelivery-feb2821} {: release-note}
{{site.data.keyword.deliverypipeline}} : Upgraded to Tekton Pipelines v0.20.1{: external}.
{: #ContinuousDelivery-nov3020} {: release-note}
{{site.data.keyword.deliverypipeline}} : Upgraded to Tekton Pipelines v0.18.1{: external}.
{: #ContinuousDelivery-nov0220} {: release-note}
New Code Risk Analyzer scans source code repositories for: : Known vulnerabilities in open source dependencies : Known vulnerabilities in operating system dependencies : Conformance to the CIS Docker benchmark : Configuration risks in Kubernetes YAML
{: #ContinuousDelivery-sep3020} {: release-note}
{{site.data.keyword.deliverypipeline}} : Upgraded to Tekton Pipelines v0.16.3{: external}.
{: #ContinuousDelivery-jul3120} {: release-note}
{{site.data.keyword.deliverypipeline}} : Upgraded to Tekton Pipelines v0.14.1{: external}.
{: #ContinuousDelivery-apr3020} {: release-note}
{{site.data.keyword.deliverypipeline}} : Upgraded to Tekton Pipelines v0.11.2{: external}.
{: #ContinuousDelivery-feb2820} {: release-note}
{{site.data.keyword.deliverypipeline}} : Upgraded to Tekton Pipelines v0.10.1{: external}.
{: #ContinuousDelivery-oct3119} {: release-note}
{{site.data.keyword.deliverypipeline}} : Upgraded to Tekton Pipelines v0.7.0{: external}.
{: #ContinuousDelivery-oct3019} {: release-note}
{{site.data.keyword.gitrepos}} : Upgraded to GitLab 12.2.7{: external}.
{: #ContinuousDelivery-oct1019} {: release-note}
{{site.data.keyword.deliverypipeline}} now has Tekton option. : Tekton Pipelines is an open source project that you can use to configure and run continuous integration/continuous delivery (CI/CD) pipelines within a Kubernetes cluster. Pipelines are defined as Tekton resources in YAML, typically stored in a Git repository.
{: #ContinuousDelivery-oct0219} {: release-note}
New DevOps tab in your IBM Cloud Kubernetes Service cluster details. : Find all toolchains whose delivery pipelines deployed to that cluster : Easily create a new DevOps toolchain
{: #ContinuousDelivery-oct0119} {: release-note}
DevOps Insights : DevOps Insights features are now part of Continuous Delivery.
{: #ContinuousDelivery-sep2019} {: release-note}
{{site.data.keyword.gitrepos}} : Upgraded to GitLab 12.1.9{: external}.
{: #ContinuousDelivery-sep1619} {: release-note}
{{site.data.keyword.gitrepos}} : Upgraded to GitLab 12.0.8{: external}.
{: #ContinuousDelivery-sep0919} {: release-note}
{{site.data.keyword.gitrepos}} : Upgraded to GitLab 11.11.8{: external}.
{: #ContinuousDelivery-sept0519} {: release-note}
Develop and test microservices with Kubernetes and Helm template doesn't support API keys that aren't bound to a specific account.
: When a {{site.data.keyword.deliverypipeline}} stage attempts to run the ibmcloud login command, it fails because no account is specified. To work around this limitation, in the {{site.data.keyword.deliverypipeline}} within the Develop and test microservices with Kubernetes and Helm template, create a pipeline property that is called ACCOUNTID and add the account that you want to use with the pipeline. In each pipeline stage, add -c $ACCOUNTID to each instance of the ibmcloud login command.
{: #ContinuousDelivery-sep0419} {: release-note}
{{site.data.keyword.gitrepos}} : Upgraded to GitLab 11.10.8{: external}.
{: #ContinuousDelivery-sept0319} {: release-note}
{{site.data.keyword.deliverypipeline}} events are not translated. : Events that are triggered by the {{site.data.keyword.deliverypipeline}} send Slack messages. Since Slack APIs do not support multi-language message payload, these Slack messages cannot be translated.
{: #ContinuousDelivery-aug2819} {: release-note}
{{site.data.keyword.gitrepos}} : Upgraded to GitLab 11.9.12{: external}.
{: #ContinuousDelivery-jun2419} {: release-note}
Stricter enforcement of service plans : A toolchain must be linked to a CD service in order for the Delivery Pipeline run. : Users of the CD service are automatically added to the list of "Authorized Users." : If you are using the Lite plan with more than five authorized users, the pipelines no longer run, pushes to Git Repos are unavailable, and DevOps Insights is unavailable. : If you are using the Lite plan, after 500 Delivery Pipeline jobs are run during a month, pipelines do not run, pushes to Git Repos are unavailable, and DevOps Insights is unavailable for the remainder of that billing period.