test: verify migration guide validation with PR #67077 changes (do not merge) #67595
+97
−1
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.
This PR targets the following PR:
What
This is a test PR to verify that the migration guide validation fix in #67594 correctly handles connectors with MDX imports before their migration guide title. This PR should NOT be merged.
These changes recreate the schema additions from PR #67077 for the source-zendesk-support connector, which has a migration guide that starts with an MDX import statement.
Related to GitHub issue #45667.
How
Manually recreated the three file changes from PR #67077:
sla
,group_sla
,status
,deleted
) to theticket_metric_events
schema in the connector manifestReview guide
airbyte-integrations/connectors/source-zendesk-support/manifest.yaml
- Verify the SLA schema definitions are correctly formatted (95+ lines of nested schema)airbyte-integrations/connectors/source-zendesk-support/metadata.yaml
- Confirm version bump to 4.10.13docs/integrations/sources/zendesk-support.md
- Check changelog entry accuracy and formattingUser Impact
Testing only - No user impact intended since this PR will not be merged.
The original changes would add missing SLA fields to the
ticket_metric_events
stream, allowing users to access SLA policy information, target times, and status data that was previously unavailable.Can this PR be safely reverted and rolled back?
Link to Devin run: https://app.devin.ai/sessions/d66e3af38e1d4d5396c475c9215e827f
Requested by: [email protected]