Repository navigation
chore(source-brevo): bump SDM base image for memory monitor (CDK PR #962) - #75946
Conversation
… test) Co-Authored-By: patrick.nilan@airbyte.io <patrick.nilan@airbyte.io>
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
|
Note 📝 PR Converted to Draft More info...Thank you for creating this PR. As a policy to protect our engineers' time, Airbyte requires all PRs to be created first in draft status. Your PR has been automatically converted to draft status in respect for this policy. As soon as your PR is ready for formal review, you can proceed to convert the PR to "ready for review" status by clicking the "Ready for review" button at the bottom of the PR page. To skip draft status in future PRs, please include |
👋 Greetings, Airbyte Team Member!Here are some helpful tips and reminders for your convenience. 💡 Show Tips and TricksPR Slash CommandsAirbyte Maintainers (that's you!) can execute the following slash commands on your PR:
📚 Show Repo GuidanceHelpful Resources
|
|
Co-Authored-By: patrick.nilan@airbyte.io <patrick.nilan@airbyte.io>
|
Deploy preview for airbyte-docs ready! ✅ Preview Built with commit 1f9c14c. |
|
/ai-canary-prerelease
|
🐤 Canary Prerelease Testing — StartingI'm beginning canary prerelease testing for
Session: https://app.devin.ai/sessions/6b88e1ad5f834b77942c63f51273563d Updates will follow shortly. |
|
Canary Prerelease: Deployment CompleteConnector: Pinning Summary
All 9 actors successfully pinned from Approval: Approved by Patrick Nilan (@pnilan) via Slack HITL. Now entering monitoring phase. Will post periodic updates as syncs complete on the prerelease version. |
Co-Authored-By: patrick.nilan@airbyte.io <patrick.nilan@airbyte.io>
This reverts commit b1d0301.
Canary Monitoring Update (2026-04-01T01:52 UTC)Monitoring duration: ~1 hour since pinning (pinned at 00:49 UTC)
Overall status: 🟢 HEALTHY — 2/2 post-pin syncs succeeded, 0 failures Triggering manual syncs on a few idle connections to broaden coverage. Will continue monitoring for 2-4 hours total. |
Canary Monitoring Update (2026-04-01T02:36 UTC)Monitoring duration: ~1h 47m (pinned at 00:49 UTC)
Summary: 8/9 actors have post-pin syncs. 7 succeeded, 0 failed, 1 still running (Customer-E-EU-1 on Snowflake — larger sync). Customer-B-EU-2 has not yet synced (trigger failed with 404, waiting for its next scheduled sync). Overall status: HEALTHY ✅ — 100% success rate on all completed syncs (7/7). Will continue monitoring. Next update in ~1 hour or when Customer-E-EU-1 completes. |
Canary Prerelease: Final ReportConnector: SummaryThe prerelease performed well across all canary connections. 9 post-pin syncs completed across 8 unique actors with a 100% success rate (9/9 succeeded, 0 failed). The change (SDM base image swap for memory monitor support) introduced no regressions. One connection (Customer-B-EU-2) did not sync during the monitoring period due to a trigger error (404), but its actor was successfully tested via another connection (Customer-B-EU-1). Detailed Results
Destination coverage: BigQuery (5), Postgres (2), Snowflake (1), Postgres/Neon (1) Canary VerdictOverall Status: PASS The prerelease performed well across all canary connections. Recommend proceeding to formal release. Next steps:
For full customer details, see the linked private issue. |
Canary Cleanup: Handoff Instructions (click to expand)Status: PASS verdict issued. Pins are intentionally left in place while the PR is open. After this PR is merged, all canary pins must be removed. A 3-day reminder has been set to check PR merge status automatically. If the session is no longer active when the PR merges, here are manual unpinning instructions: Pinned actors (all pinned to
To unpin manually: Use Approval URL: #75946 (comment) |
Canary Cleanup CompletePR has been merged. All 9 canary version pins have been successfully removed:
All connections will now use the default GA version. Canary prerelease workflow for |
…irbytehq#962) (airbytehq#75946) Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> Co-authored-by: patrick.nilan@airbyte.io <patrick.nilan@airbyte.io>
What
Updates
source-brevoto use the dev build ofsource-declarative-manifestfrom airbyte-python-cdk#962, which introduces the dual-condition memory monitor with fail-fast shutdown on memory threshold. Also replaces the connector icon with the official Brevo logo.How
source-declarative-manifestbase image from released7.14.0to dev build7.13.0.post13.dev23823332086(published from CDK PR editing a oneOf config doesn't show the selected sub-schema #962 prerelease workflow run 23823332086)dockerImageTagfrom0.2.29→0.2.300.2.30icon.svgwith the official Brevo logoReview guide
airbyte-integrations/connectors/source-brevo/metadata.yaml7.13.0.post13.dev...), not a released version — verify the@sha256:dc8f1d05...digest matches the published dev image7.14.0to a7.13.0prerelease — this is intentional, as the dev build is branched from the7.13.0line with the new memory monitor feature0.2.29→0.2.30is correctairbyte-integrations/connectors/source-brevo/icon.svg#F9FFF6) on transparent background — confirm this is acceptable for the connector icon format (Airbyte typically expects square icons; this may trigger a pre-release check warning)docs/integrations/sources/brevo.md— changelog entry added for0.2.30User Impact
Connectors built from this PR will use the dev SDM image containing the new memory monitor. Low-usage community connector selected to minimize blast radius. The connector icon is updated to the official Brevo branding.
Can this PR be safely reverted and rolled back?
Link to Devin session: https://app.devin.ai/sessions/070ecb51ceee4f9189e1c09a83ba31cb