feat(data-warehouse): promote Brevo source to beta - #74100
Merged
Conversation
Promote the Brevo data-warehouse source from alpha to beta. It has cleared the usage and reliability bar over the last 7 days: in active use by 31 teams (threshold 30) with a 0.0% import error rate (threshold under 5.0%). This is a status-label change only - no connector behavior, schema, or sync logic is touched. Generated-By: PostHog Code Task-Id: 02ad9847-3c04-4774-9596-cadac148f8b1
Contributor
|
Hey @Gilbert09! 👋 It looks like your git author email on this PR isn't your
You can fix it for this repo with: git config user.email "you@posthog.com"Or set it globally with |
![stamphog[bot]](https://avatars.githubusercontent.com/in/3000332?s=60&v=4){kind=small}
There was a problem hiding this comment.
Trivial two-line status-label flip (alpha→beta) with matching test update, author is on the owning team, no gating or connector logic touched.
- 👍 on the PR from hex-security-app[bot].
Gate mechanics and policy version
| Gate | Result | |
|---|---|---|
| prerequisites | ✓ | all clear |
| deny-list | ✓ | no deny categories matched |
| size | ✓ | 2L, 1F substantive, 4L/2F incl. docs/generated/snapshots — within ceiling |
| tier | ✓ | T1-agent / T1a-trivial (4L, 2F, single-area, feat) |
| stamphog 2.0.0b3 | .stamphog/policy.yml @ bdc6fa7 · reviewed head 102143d |
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
1 participant
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
The Brevo (formerly Sendinblue) data-warehouse source has been running as alpha. Over the last 7-day window it has cleared our promotion bar, so the alpha label undersells how ready it is.
Changes
Promote the Brevo source's
releaseStatusfromalphatobeta- the value the/api/public_source_configs/endpoint surfaces for the connector. Metrics backing the promotion (7-day window):Status-label change only. No connector behavior, schemas, or sync logic changed. Gating is untouched - the source was already visible (
unreleasedSourceis unset), soreleaseStatusis a soft label with no extra flag to remove.How did you test this code?
Updated the existing source-config assertion to expect
betaand ran it:products/warehouse_sources/backend/temporal/data_imports/sources/brevo/tests/test_brevo_source.py::TestBrevoSource::test_source_config_basicspasses.ruff checkis clean on the source.Automatic notifications
Docs update
🤖 Agent context
Autonomy: Human-driven (agent-assisted)
I (Claude) made this change on Tom's direction. Invoked the
/implementing-warehouse-sourcesskill to confirm the convention:releaseStatususes theReleaseStatusenum and moves alpha → beta once a source is past its rough edges. Located the single source of truth inbrevo/source.py, flipped the enum, and updated the one test that pinned the old value. Checked open PRs (including the maintainer's own) for an existing Brevo promotion first - none found.Created with PostHog Code