feat(warehouse_sources): promote Vercel source to beta - #76747
Conversation
Promote the Vercel data-warehouse source release status from alpha to beta. Generated-By: PostHog Code Task-Id: 5334f6aa-a082-4a9a-894d-f5e397587936
|
😎 Merged successfully - details. |
|
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 |
There was a problem hiding this comment.
Pull request overview
Promotes the Vercel data warehouse import source from alpha to beta by updating its releaseStatus in the source metadata (surfaced via /api/public_source_configs/), plus the corresponding metadata test assertion.
Changes:
- Update Vercel
SourceConfig.releaseStatusfromReleaseStatus.ALPHAtoReleaseStatus.BETA. - Update the Vercel source metadata test to assert
beta.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| products/warehouse_sources/backend/temporal/data_imports/sources/vercel/source.py | Bumps Vercel source releaseStatus to BETA in SourceConfig. |
| products/warehouse_sources/backend/temporal/data_imports/sources/vercel/tests/test_vercel_source.py | Updates metadata test expectation to ReleaseStatus.BETA. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
![stamphog[bot]](https://avatars.githubusercontent.com/in/3000332?s=60&v=4){kind=small}
There was a problem hiding this comment.
Trivial one-line release-status label change (alpha→beta) with matching test update, authored by the owning team, no behavioral/schema changes.
- Author wrote 0% of the modified lines and has 8 merged PRs in these paths (familiarity MODERATE).
- 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, 4L/2F incl. docs/generated/snapshots — within ceiling |
| tier | ✓ | T1-agent / T1a-trivial (4L, 2F, single-area, feat) |
| stamphog 2.0.0b4 | .stamphog/policy.yml @ 324716a · reviewed head 6c8b356 |
|
/trunk merge |
Problem
The Vercel data-warehouse source has been running as
alphasince launch. It has now cleared our promotion bar over the last 7 days, so it should carry thebetalabel instead.Changes
Promote the Vercel source's
releaseStatusfromReleaseStatus.ALPHAtoReleaseStatus.BETA(surfaced by the/api/public_source_configs/endpoint). No behavior, schema, or sync-logic changes — this is a status-label promotion only.The source has no
unreleasedSourceflag orfeatureFlaggate, so nothing else changed alongside the stage.Promotion metrics (7-day window):
How did you test this code?
Ran the Vercel source metadata test, which now asserts
beta:products/warehouse_sources/backend/temporal/data_imports/sources/vercel/tests/test_vercel_source.py::TestVercelSource::test_source_config_metadata— passes.ruff checkclean on the touched files.Docs update
No user-facing doc changes needed for a release-status label bump.
🤖 Agent context
Autonomy: Human-driven (agent-assisted)
Invoked the
/implementing-warehouse-sourcesskill to confirm release-status conventions (use theReleaseStatusenum,betais a soft label on a visible source, no gating to remove here). The change is limited to thereleaseStatusfield and its matching test assertion. Checked open PRs (including the maintainer's own) for an existing Vercel promotion before opening this one — none found.Created with PostHog Code