chore(warehouse_sources): promote Brevo to GA - #95864
Merged
Merged
Conversation
Brevo has met the GA bar for adoption maturity and import reliability, so its release status moves from beta to GA. No connector behavior, schema, or sync logic changes. Generated-By: PostHog Desktop Task-Id: 17a86e58-8d01-4e51-bb02-168ad73783df
|
😎 Merged successfully - details. |
Contributor
🤖 CI report
|
![stamphog[bot]](https://avatars.githubusercontent.com/in/3000332?s=60&v=4){kind=small}
There was a problem hiding this comment.
Approved.
Single-line release-status label flip on a source the author owns and has strong familiarity with; no behavioral or risky-territory impact.
- Author wrote 100% of the modified lines and has 2 merged PRs in these paths (familiarity STRONG).
- copilot-pull-request-reviewer[bot] reviewed the current head.
Gate mechanics and policy version
| Gate | Result | |
|---|---|---|
| prerequisites | ✓ | all clear |
| deny-list | ✓ | no deny categories matched |
| size | ✓ | 2L, 1F substantive — within ceiling |
| tier | ✓ | T1-agent / T1a-trivial (2L, 1F, single-area, chore) |
| stamphog 2.0.0b4 | .stamphog/policy.yml @ f85983e · reviewed head f85983e |
Contributor
|
/trunk merge |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Anyone browsing the data warehouse source catalog sees Brevo labelled Beta, which reads as "not ready for production yet". It is ready — the connector has been live for over three months with a clean import record, so the label is now understating it and gives teams a reason to hesitate before connecting.
Changes
BrevoSource.get_source_config—releaseStatusgoes fromReleaseStatus.BETAtoReleaseStatus.GA.Brevo carries no
unreleasedSourceflag and nofeatureFlaggate, so nothing else had to be unwound. It was already visible and connectable to everyone; only the label changes.The promotion bar it clears:
How did you test this code?
No new tests.
releaseStatusis a declared label with no branching on it, so a test asserting the new value would only restate the diff.No automated tests were run for this change, and no manual testing was done — the connector's request, schema, and sync paths are untouched, so the existing Brevo suites cover the same ground they did before. CI reports the results.
Automatic notifications
Docs update
The posthog.com Brevo doc renders its release status from the
public_source_configsAPI, so it picks the change up automatically.🤖 Agent context
Autonomy: Fully autonomous
Tooling: Claude Code (Opus 5), via the
ghCLI and repo file tools. Skills invoked:/implementing-warehouse-sources(for the release-status conventions and theReleaseStatusenum rule),/writing-pr-descriptions.Decisions along the way:
releaseStatusentirely. Omitting the field also means GA, but the explicitReleaseStatus.GAmatches what every other GA source in the tree does.unreleasedSource/featureFlagwhen they are present, and Brevo has neither.No duplicate: searched open PRs for "brevo", "releaseStatus", and "promote", and listed the maintainer's open PRs. The nearest match, #95842, promotes ActiveCampaign and Mailjet and touches neither Brevo file. Nothing else addresses this.
Public artifact: the diff is one enum value. The adoption and error-rate figures quoted above are this connector's own aggregate health metrics, not customer data, and no session material reached the branch.
Created with PostHog Desktop