Add warning about migration to api tokens

Author: Axot017

docs/getting-started/integrate-source-code/Bitbucket-Cloud.md

@@ -16,9 +16,12 @@ You can set up multiple Space-level and one default Bitbucket Cloud integration
 2. **Integration name**: Enter a name for your integration. It cannot be changed later because the Spacelift webhook endpoint is generated based on this name.
 3. **Integration type**: Default (all spaces) or [Space-specific](../../concepts/spaces/README.md). Each Spacelift account can only support one default integration per VCS provider, which is available to all stacks and modules in the same Space as the integration.
 
+!!! warning "Migration from App Passwords to API Tokens"
+    Previously, this integration used Bitbucket App Passwords for authentication. Atlassian has deprecated App Passwords and [replaced them with API tokens](https://www.atlassian.com/blog/bitbucket/bitbucket-cloud-transitions-to-api-tokens-enhancing-security-with-app-password-deprecation){: rel="nofollow"}.
+
 ### Create your API token
 
-You will need to create an [API token](https://support.atlassian.com/bitbucket-cloud/docs/using-api-tokens) for this integration on the Bitbucket Cloud site.
+You will need to create an [API token](https://support.atlassian.com/bitbucket-cloud/docs/using-api-tokens){: rel="nofollow"} for this integration on the Bitbucket Cloud site.
 
 1. Navigate to **Atlassian account settings** > **Security** > **Create API token with scopes**.
 2. Fill in the details to create a new API token:

docs/integrations/source-control/bitbucket-cloud.md

@@ -25,9 +25,12 @@ Explanation of the fields:
 
 Space-level integrations will be listed to users with **read** access to the integration Space. Integration details however contain sensitive information so they are only visible to those with **admin** access. On the other hand, default integrations are visible to all users of the account, but only **root** Space admins can see the details of them. Visit the [Spaces](../../concepts/spaces/README.md) documentation to learn more about access controls.
 
+!!! warning "Migration from App Passwords to API Tokens"
+    Previously, this integration used Bitbucket App Passwords for authentication. Atlassian has deprecated App Passwords and [replaced them with API tokens](https://www.atlassian.com/blog/bitbucket/bitbucket-cloud-transitions-to-api-tokens-enhancing-security-with-app-password-deprecation){: rel="nofollow"}.
+
 ### Creating an API Token
 
-In order to get the API token you'll need to go to Bitbucket Cloud and navigate to **Atlassian account settings** -> **Security** -> **Create API token with scopes**. In the form, you will need to:
+In order to get the [API token](https://support.atlassian.com/bitbucket-cloud/docs/using-api-tokens){: rel="nofollow"} you'll need to go to Bitbucket Cloud and navigate to **Atlassian account settings** -> **Security** -> **Create API token with scopes**. In the form, you will need to:
 
 1. Choose a name for your API token
 2. Set an expiration date