RAN Booster Bitbucket Cloud

RAN Booster Bitbucket Cloud is the free Bitbucket provider for RAN Booster. It registers the bb provider and adds the Bitbucket settings tab through Provider API 11. The add-on requires Add-on API 16 and inserts its operational guide after Core's Bitbucket provider documentation.

Compatibility and safety

• Requires WordPress 7.0+, PHP 8.2+ (PHP 8.4 recommended), and exactly RAN Booster Provider API 11 and Add-on API 16.
• The current certification target is RAN Booster v1.0.0-beta.29: tag target ffc11fc8e40618624a785b7fca5193029c6d492e, with the immutable release archive promoted from qualified candidate ff35be100a9f5c6cd77a84bcfc3734227106b0b8. The certification records both identities so repository checkout and archive provenance are proved independently.
• Requires Plugins: ran-booster declares Core as a package dependency, but WordPress does not check Booster's APIs. The add-on checks RAN_BOOSTER_PROVIDER_API_VERSION, RAN_BOOSTER_ADDON_API_VERSION and the supported runtime mode; a missing or incompatible API boundary disables provider registration and remote calls.
• Provider API 11 has no logging capability. Diagnostics return bounded ProviderDiagnosticResult values to Core and never send exceptions or vendor text through a logging facade.
• If Core is missing or incompatible, the add-on displays a compatibility notice only to administrators who can activate plugins.
• Credentials come only from Core's provider-bound ProviderCredentialStore. Authenticated webhook-delivery diagnostics use Core's provider-bound AuthenticatedWebhookDeliveryEvidenceReader, supplied by Provider API 11 registration. The add-on neither stores credentials nor reads Core's sidecar paths, service container, database repositories or test fixtures.
• The provider intentionally implements none of the optional release metadata, candidate-listing, inspection, acquisition, native-target or release-workflow capabilities.
• The provider does not implement the optional webhook fitness or management capabilities; use the included instructions to configure Bitbucket webhooks manually. Its webhook diagnostics can still report whether Core has authenticated a delivery and whether that delivery matched a managed package.
• The documentation callback is non-interactive. It receives no Core object or facade and makes no remote calls.

Install and operate

1. Install and activate a RAN Booster release that provides Provider API 11 and Add-on API 16.
2. Download ran-booster-bitbucket-<version>.zip and its .sha256 file from the same GitHub release. Do not use GitHub's generated source archives.
3. Verify the checksum, then upload and activate the ZIP through WordPress's Plugins screen.
4. Open RAN Booster. The Bitbucket tab appears after GitHub.
5. Open RAN Booster's Documentation tab for the add-on's guide to API-token permissions, package connection, manual webhook setup, Transporter recovery, deactivation and support.

Transporter copies only eligible file-stored credentials selected for export. On a target with a compatible version of this add-on active, each carried credential requires a separate choice: import the copied credential, use a saved Bitbucket credential, or leave its packages unchanged. There is no credential or anonymous fallback, and Transporter does not assess token permissions. Copying does not revoke or rotate the source API token.

Deactivating the add-on stops it from registering the bb provider. It owns no installation records or credential storage to remove.

Development

This is a dependent add-on, not a generic standalone plugin. Development tests use the exact certified RAN Booster production source as their contract fixture. The suite loads Core's shipped autoload.php and public production contracts, which require the exact certified Core checkout's locked production Composer dependencies. Do not install Core development dependencies. With the certified Core checkout at ../ran-booster:

composer install
composer check
(cd ../ran-booster && composer install --no-dev --no-interaction --prefer-dist --no-progress)
RAN_BOOSTER_CORE_PATH=../ran-booster RAN_BOOSTER_CORE_VENDOR_AUTOLOAD=../ran-booster/vendor/autoload.php composer check:host
RAN_BOOSTER_CORE_PATH=../ran-booster RAN_BOOSTER_CORE_VENDOR_AUTOLOAD=../ran-booster/vendor/autoload.php composer analyze
composer build:release -- "$(git rev-parse HEAD)"

composer check is the Core-independent source-quality contract used by the shared PHP provider. composer check:host adds blocking level-8 PHPStan analysis, the Core-backed unit and release-candidate contracts and is required for the full repository handoff when the certified Core is available.

Set RAN_BOOSTER_CORE_PATH if the exact certified Core checkout is elsewhere and set RAN_BOOSTER_CORE_VENDOR_AUTOLOAD to that checkout's generated vendor/autoload.php when running Core-backed source tests or analysis. Do not import Core-owned test fixtures into this repository. The add-on owns its PHP tools in its local vendor/, but never packages a vendor tree or Core code in the release artifact. PHPStan is a blocking, Bitbucket-only host gate; read the decision record in CONTRIBUTING.md before raising its level, adding suppressions or adopting it elsewhere.

Releases and support

Releases are GitHub artifacts built and checked by the repository's release workflow, not WordPress.org/SVN publications. To upgrade, download the ZIP and checksum attached to the same release. The plugin's Update URI prevents WordPress.org from claiming its update channel; this add-on does not currently register an automatic update service.

See RELEASE.md and use Conventional Commits as described in CONTRIBUTING.md. Report ordinary issues through the repository's GitHub issue tracker. Report vulnerabilities through the security policy, and never put credentials, webhook secrets, signed URLs, release assets, or customer data in a public issue.

License

GPL-2.0-or-later. See license.txt and NOTICE.md.