Stay organized with collections
Save and categorize content based on your preferences.
This page documents production updates to Secure Source Manager.
Check this page for announcements about new or updated features, bug fixes,
known issues, and deprecated functionality.
You can see the latest product updates for all of Google Cloud on the
Google Cloud page, browse and filter all release notes in the
Google Cloud console,
or programmatically access release notes in
BigQuery.
To get the latest product updates delivered to you, add the URL of this page to your
feed
reader, or add the
feed URL directly.
You can use custom constraints with Organization Policy to provide more granular control over specific fields for some Secure Source Manager resources. For more information, see Manage resources with custom constraints.
November 21, 2024
Secure Source Manager supports email notifications. For more information, see Notifications overview. To configure notifications, follow the instructions in Set up notifications.
Secure Source Manager integration with Cloud Build lets you define your Cloud Build configuration and build triggers in your Secure Source Manager repository. To learn how to trigger builds automatically, see Connect to Cloud Build.
Secure Source Manager is now available in the northamerica-northeast1 (Montréal) region.
August 14, 2023
A one-time clean up of unused Secure Source Manager instances is scheduled for August 16, 2023. Instances that haven't been accessed or used for 30 days or more will be deleted.
We previously announced that this clean up policy would be an ongoing policy, but that has been changed based on user feedback. This will be a one-time clean up operation.
To prevent deletion of your Secure Source Manager instance, you can perform any of the following actions: log in using the web interface, use Git to push or pull from your repository, or access the instance via the Secure Source Manager API.
July 20, 2023
Secure Source Manager is now available in the me-west1 (Tel Aviv) region.
July 17, 2023
A new policy to clean up unused Secure Source Manager instances is now in effect. On August 16, 2023, instances that have not been accessed or used for 30 days or more will be deleted.
To prevent deletion of your Secure Source Manager instance, you can perform any of the following actions: log in using the web interface, use Git to push or pull from your repository, or access the instance via the Secure Source Manager API.
New repositories must be created in the same project as their parent instance.
A new Repo Creator role (roles/securesourcemanager.repoCreator) is available.
All repositories in separate projects from their parent instances will be deleted after May 1, 2023.
Repositories in separate projects from their parent instances can request to be migrated. For migration steps see Migrate to single-project repositories.
Repositories must be created in the same Google Cloud project as their parent Secure Source Manager instance. Customers can continue to use repositories previously created in separate projects from their parent instance.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[],[],null,["# Secure Source Manager release notes\n\nThis page documents production updates to Secure Source Manager.\nCheck this page for announcements about new or updated features, bug fixes,\nknown issues, and deprecated functionality.\n\n\nYou can see the latest product updates for all of Google Cloud on the\n[Google Cloud](/release-notes) page, browse and filter all release notes in the\n[Google Cloud console](https://console.cloud.google.com/release-notes),\nor programmatically access release notes in\n[BigQuery](https://console.cloud.google.com/bigquery?p=bigquery-public-data&d=google_cloud_release_notes&t=release_notes&page=table).\n\nTo get the latest product updates delivered to you, add the URL of this page to your\n[feed\nreader](https://wikipedia.org/wiki/Comparison_of_feed_aggregators), or add the\n[feed URL](https://cloud.google.com/feeds/secure-source-manager-release-notes.xml) directly.\n\nAugust 21, 2025\n---------------\n\nYou can now use a Google-managed certificate when you create a [create a Private Service Connect Secure Source Manager instance](https://cloud.google.com/secure-source-manager/docs/create-private-service-connect-instance#create-private-service-connect-instance).\n\nAugust 14, 2025\n---------------\n\nIntegrated data loss prevention (DLP) is now [generally available](https://cloud.google.com/products#product-launch-stages)\n\nAugust 04, 2025\n---------------\n\nSecure Source Manager is now [generally available](https://cloud.google.com/products#product-launch-stages) for all customers.\n\nJuly 08, 2025\n-------------\n\nSecure Source Manager is now available in the following [regions](https://cloud.google.com/secure-source-manager/docs/locations#regions):\n\n- australia-southeast1 (Sydney)\n- asia-northeast1 (Tokyo)\n\nApril 15, 2025\n--------------\n\nRegional endpoints are now available in Secure Source Manager. For more information, see [Configure data locality by using regional endpoints](https://cloud.google.com/secure-source-manager/docs/endpoints).\n\nDecember 19, 2024\n-----------------\n\nYou can use custom constraints with Organization Policy to provide more granular control over specific fields for some Secure Source Manager resources. For more information, see [Manage resources with custom constraints](https://cloud.google.com/secure-source-manager/docs/custom-constraints).\n\nNovember 21, 2024\n-----------------\n\nSecure Source Manager supports email notifications. For more information, see [Notifications overview](https://cloud.google.com/secure-source-manager/docs/notifications-overview). To configure notifications, follow the instructions in [Set up notifications](https://cloud.google.com/secure-source-manager/docs/set-up-notifications).\n\nNovember 14, 2024\n-----------------\n\nSecure Source Manager supports [Workforce Identity Federation](https://cloud.google.com/iam/docs/workforce-identity-federation).\n\nTo create an instance with Workforce Identity Federation enabled, follow the instructions in [Create a Secure Source Manager instance to use with federated identities](https://cloud.google.com/secure-source-manager/docs/create-instance-federated-identities).\n\nSeptember 11, 2024\n------------------\n\nSecure Source Manager branch protection is Generally Available. To learn more about branch protection, see the [Branch protection overview](https://cloud.google.com/secure-source-manager/docs/branch-protection-overview) and [Configure branch protection](https://cloud.google.com/secure-source-manager/docs/configure-branch-protection). \nSecure Source Manager integration with Cloud Build lets you define your Cloud Build configuration and build triggers in your Secure Source Manager repository. To learn how to trigger builds automatically, see [Connect to Cloud Build](https://cloud.google.com/secure-source-manager/docs/connect-cloud-build).\n\nOctober 12, 2023\n----------------\n\n[Secure Source Manager](https://cloud.google.com/secure-source-manager/docs/overview) is generally available ([GA](https://cloud.google.com/products#product-launch-stages)) by invitation only.\n\nSeptember 25, 2023\n------------------\n\nSecure Source Manager is now available in the `northamerica-northeast1` (Montréal) [region](https://cloud.google.com/secure-source-manager/docs/locations#regions).\n\nAugust 14, 2023\n---------------\n\nA one-time clean up of unused Secure Source Manager instances is scheduled for August 16, 2023. Instances that haven't been accessed or used for 30 days or more will be deleted.\n\nWe previously announced that this clean up policy would be an ongoing policy, but that has been changed based on user feedback. This will be a one-time clean up operation.\n\nTo prevent deletion of your Secure Source Manager instance, you can perform any of the following actions: log in using the web interface, use Git to push or pull from your repository, or access the instance via the Secure Source Manager API.\n\nJuly 20, 2023\n-------------\n\nSecure Source Manager is now available in the `me-west1` (Tel Aviv) [region](https://cloud.google.com/secure-source-manager/docs/locations#regions).\n\nJuly 17, 2023\n-------------\n\nA new policy to clean up unused Secure Source Manager instances is now in effect. On August 16, 2023, instances that have not been accessed or used for 30 days or more will be deleted.\n\nTo prevent deletion of your Secure Source Manager instance, you can perform any of the following actions: log in using the web interface, use Git to push or pull from your repository, or access the instance via the Secure Source Manager API.\n\nJune 15, 2023\n-------------\n\nSecure Source Manager is available in [Preview](https://cloud.google.com/products#product-launch-stages).\n\nHost your source code in a single tenant, regionally deployed, managed source code repository hosted on Google Cloud.\n\nFor preview access, contact [secure-source-manager-support@google.com](mailto:secure-source-manager-support@google.com).\n\nTo get started with Secure Source Manager, [Enable the Secure Source Manager API](https://cloud.google.com/secure-source-manager/docs/enable-disable) and then [Deploy and access an instance](https://cloud.google.com/secure-source-manager/docs/deploy-access-instance).\n\nApril 28, 2023\n--------------\n\nSecure Source Manager is now available in `asia-east1` (Taiwan) and `europe-west4` (Netherlands) [regions](https://cloud.google.com/secure-source-manager/docs/locations#regions).\n\nApril 06, 2023\n--------------\n\nSecure Source Manager has entered phase 2 of implementing the [Google Cloud project location restriction](https://cloud.google.com/secure-source-manager/docs/overview#project_location_restriction). The changes are as follows:\n\n- New repositories must be created in the same project as their parent instance.\n- A new Repo Creator role (`roles/securesourcemanager.repoCreator`) is available.\n- All repositories in separate projects from their parent instances will be deleted after May 1, 2023.\n- Repositories in separate projects from their parent instances can request to be migrated. For migration steps see [Migrate to single-project repositories](https://cloud.google.com/secure-source-manager/docs/migrate-repositories).\n\nIf you have any questions, feel free to reach out to us at [secure-source-manager-support@google.com](mailto:secure-source-manager-support@google.com).\n\nMarch 10, 2023\n--------------\n\nRepositories must be created in the same Google Cloud project as their parent Secure Source Manager instance. Customers can continue to use repositories previously created in separate projects from their parent instance.\n\nFor more details see [Google Cloud project location restriction](https://cloud.google.com/secure-source-manager/docs/information-multi-project)."]]
