Can't submit version update for Maestro Cloud Upload pipe in official-pipes (forking disabled)

Proksh Luthra

Hi, we (mobile.dev) maintain the Maestro Cloud Upload pipe, mobiledevinc/maestro-cloud-upload, listed in bitbucketpipelines/official-pipes. The registry has it at 1.6.1, and we've since released 1.7.0, 1.7.1 and 1.8.0 (image mobiledevinc/maestro-cloud-upload:1.8.0 on Docker Hub).

The README says vendors should fork the repo and open a PR, which is how we submitted earlier bumps (most recently PR #890). Forking now fails with "Forking to a different workspace is not allowed", and our existing fork mobiledevinc/official-pipes is no longer linked to the upstream, so we can't open a PR. We also saw that the auto-bump job only updates Atlassian-maintained pipes.

Could you:
1. update pipes/maestro-cloud-upload.yml to version: "1.8.0" (the one-line change is on branch maestro-cloud-upload-1.8.0 in mobiledevinc/official-pipes), and
2. tell us how vendors should submit version updates now, or re-enable forking/PRs for us?

Thanks!

Arkadiusz Wroblewski

Hello @Proksh Luthra

This community forum is primarily for fellow users and not Atlassian employees. Because Atlassian manages the repository, we’re unable to change its forking permissions or accept contributions. Please reach out to Atlassian Support, and they can look into the restriction and direct your request to the right team.

https://support.atlassian.com/contact/

Cheers,

Arek🤠🧙‍♂️