Hey @joshp - PM for Bitbucket Cloud here, thanks for your questions.
- Bitbucket Cloud’s implementation of Connect has historically been a bit separated from that of Confluence and Jira, so the phase out of Connect is being managed independently.
- However, we 100% are in the process of also EOL’ing Connect on Bitbucket Cloud, and will have detailed information about that being released very soon (1-2 weeks).
- We’re 100% cognisant of the need to have capability parity between our Forge vs Connect implementations before any EOL, and that’s something we will be making sure occurs.
- Key thing to note is that today, Connect apps for Bitbucket Cloud can only be listed on the Marketplace as “non-paid”.
- We expect that in the short-term, Bitbucket Cloud Forge apps will be the same. However, we do plan to bring “Paid Via Atlassian” to Forge Apps for Bitbucket in the near future as part of our wider campaign to standardise Bitbucket extensibility onto Forge.
- Stay tuned over the next 1-2 weeks, we will have an official announcement including information on Bitbucket Forge apps in Marketplace.