Transitioning into phase 2 of the end-of-support process for Connect app on Bitbucket Cloud

Hi everyone,

Thank you for your continued partnership as wen move through the **Connect-to-Forge transition for Bitbucket Cloud.**Your feedback and engagement over the past few months have been invaluable, and we want to make sure you have the clarity and support you need as we enter the next stage.

We wanted to share an important update: we are now entering phase 2 of the Connect end of support for Bitbucket Cloud where all app updates must be delivered via Forge.

What’s changing in Phase 2

Moving forward, all app updates must be delivered via Forge. The only updates that may be permitted for Connect apps are those that directly support migration to Forge equivalents, such as adding the mechanism for Connect apps to register a Forge app as their replacement. To do this, add a `forgeAppLink` key to the root of your Connect app descriptor JSON, using the Forge installation link as the value.

Migration path

We’ve received several questions regarding the migration path, and we appreciate your patience as we work through this. Our team is actively discussing with our Marketplace teams to align on how to get Connect apps transitioned smoothly to Forge. We will be finalizing these details in the coming weeks and will update you as soon as we have clarity.

Share your feedback and needs with us

As we work through this transition together, we want to make sure you have everything you need to migrate successfully. If there’s a capability you’re missing, a friction point you’ve encountered, or a question about the process, we’d love to hear about it. Please share your input in this thread below or via this form by June 1st so we can prioritize and plan accordingly.

We want to ensure the migration to Forge is a success, and we’re dedicated to providing the support and resources you need to get there. We know this transition requires a lot on your part, and we want to make sure you feel supported. Thank you for your continued collaboration and we’re here for you every step of the way. Please don’t hesitate to share your feedback below.

If I’m not mistaken the current “mechanism”, is actually not a migration from Connect to Forge? So far it’s a hard switch, IMO.

@HamreetKaur thanks for addressing this explicitly and working on a smoother migration path for Bitbucket Cloud.

Accessing bitbucket properties (app/user/repo/workspace) is a must-have for Forge apps. Any further guidance around this blocker is appreciated.