chore(warehouse-sources): promote the pylon source to GA - #108904
Conversation
The Pylon source meets the GA bar: live over three months with a 0.0% import error rate in the last 7 days. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Generated-By: PostHog Desktop Task-Id: d09b5108-23f4-4bf1-964b-25647479c2b0
|
😎 Merged successfully - details. |
There was a problem hiding this comment.
Approved.
Single-field label change from alpha to GA with a matching test update; contained, reversible, no behavior change.
- Author wrote 100% of the modified lines and has 0 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, 7L/2F incl. docs/generated/snapshots — within ceiling |
| tier | ✓ | T1-agent / T1a-trivial (7L, 2F, single-area, chore) |
| stamphog 2.3.1 | .stamphog/policy.yml @ 6e5f17a · reviewed head 6e5f17a |
🤖 CI report
|
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: PostHog/posthog/.coderabbit.yaml Review profile: QUIET Plan: Enterprise Run ID: 📒 Files selected for processing (2)
Included review availability: This review used your included allowance. Your plan provides up to 12 included reviews per hour; 8 remain after this review. 📝 WalkthroughWalkthroughThe Pylon source configuration now sets its release status to GA instead of alpha. The test expects the GA status and verifies that Priority: ⬇️ Low Merge Risk: ⚪ Minimal · up to Pylon will be classified as generally available. The selected value is supported by the shared status contract, and no concrete merge-blocking risk is evidenced. 🚥 Pre-merge checks | ✅ 1✅ Passed checks (1 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
|
/trunk merge |
Problem
Anyone connecting a source in the data warehouse wizard sees Pylon labelled "alpha", which reads as "this might not work" and discourages people from picking it. The connector has earned its way out of that label: it has been live for over three months, and its imports failed 0.0% of the time over the last 7 days (the bar is under 2.5%).
Changes
releaseStatuson the Pylon source config moves fromReleaseStatus.ALPHAtoReleaseStatus.GA. That is the value/api/public_source_configs/surfaces and the frontend renders.unreleasedSourceflag and nofeatureFlag, so there is no gating to remove. The test now asserts both stay absent.How did you test this code?
products/warehouse_sources/backend/temporal/data_imports/sources/pylon/tests/test_pylon_source.pylocally: 12 passed.unreleasedSource,featureFlag, andreleaseStatustogether.Release status
Automatic notifications
Docs update
None.
🤖 Agent context
Autonomy: Fully autonomous
Agent: Claude Code, Opus 5
Skills invoked:
/implementing-warehouse-sources,/writing-pr-descriptions.No duplicate: searched open PRs for "Pylon", "releaseStatus", and "promote", and listed every open PR by the maintainer. The only other Pylon PR is #106228, which swaps the source icon and does not touch release status. #108805 is the same promotion for Neon and was used as the pattern for this diff.
Public artifact: the diff and this description carry no material from the agent session beyond the two aggregate metrics quoted above.
Created with PostHog Desktop
🤖 Generated with Claude Code