[devin-ai-integration]

Triggering Context

Run triggered by: Merged commit to master: 45ca8549 — fix(source-linkedin-ads): resolve pivot placeholder in custom analytics reports (#83268), releasing version 6.0.2. The autodoc workflow started this session to review the connector's documentation.

Relevant context: #83268

Confidence impact: A small, merged bug-fix PR with a clear scope gives the strongest possible triggering context (5/5).

Documentation Confidence Assessment

Overall Confidence: 4/5

Dimension	Score	Rationale
Code Comprehension of the Documented Surface	5/5	Manifest-only connector; the documented surface is changelog dates and PR links, all verified directly against git log merge history.
API Documentation Quality	5/5	LinkedIn Marketing API has comprehensive Microsoft Learn docs; metadata.yaml lists 4+ diverse external doc links.
Change Scope & Risk	5/5	Changelog date/link corrections and duplicate-row removal only; 5 insertions, 7 deletions.
Existing Doc Maturity	4/5	345-line doc with full prerequisites, setup, streams, rate-limit, and limitations coverage.
Connector Sensitivity	2/5	Certified connector with high usage (ql 400, sl 300).
Triggering Context	5/5	Triggered from a small, merged bug-fix PR.
Inference Ratio	5/5	Every changed fact (merge dates, PR numbers) verified against git history; nothing inferred.

Adjustments based on code comprehension

None -- scored at baseline (manifest-only, 5).

What I Verified vs. What I Inferred

• Verified from code: All corrected changelog dates match the merge dates in git log origin/master -- airbyte-integrations/connectors/source-linkedin-ads/metadata.yaml; PR chore(connectors): roll Cloud back to pre-SDM-7.23.7 versions for 19 sources #83183 is the commit that rolled Cloud back to 5.6.10; the 6.0.2 pivot fix and its changelog entry landed in commit 45ca854. The rest of the doc (auth scopes, streams, custom report config) matches manifest.yaml and was left unchanged.
• Verified from API docs: No changed fact depends on third-party API documentation.
• Inferred: Nothing.

Areas of Concern

None identified.

---

What

Corrects changelog inaccuracies in docs/integrations/sources/linkedin-ads.md. The rest of the doc was reviewed against the connector's manifest.yaml and recent changes (6.0.0–6.0.2) and is already accurate and complete, so no other edits were needed.

How

Corrections only:

• 6.0.1: date 2026-07-30 → 2026-07-31 (PR fix(source-linkedin-ads): use error_handler key so custom error handler is instantiated #83269 merged Jul 31)
• 6.0.0: date 2026-07-21 → 2026-07-30 (PR perf(source-linkedin-ads)!: Batch analytics requests #74334 merged Jul 30)
• 5.7.0: date 2026-07-28 → 2026-07-30 (PR feat(source-linkedin-ads): Add Statistics Finder custom reports #78505 merged Jul 30)
• 5.6.12: the "Pull Request" cell linked an airbyte-python-cdk issue (1082); now links the airbyte PR that made the change, 83183
• 5.6.4: date 2026-02-10 → 2026-02-11 (PR feat(source-linkedin-ads): Upgrade LinkedIn API version from 202502 to 202601 #72831 merged Feb 11)
• Removed duplicate rows for 5.6.7 and 5.6.6 (each appeared twice with different dates; kept the rows with the correct 2026-04-06 merge date)

Review Guide

All changes are in the changelog table (lines 232–245). Cross-check any row against the linked PR's merge date.

---

Note: I am an AI assistant (Devin) and have proposed these documentation updates based on a review of the connector source code and recent merge history. Reviewers may merge, modify, or close this PR as they see fit.

---

Devin session

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment, CI, and merge conflict monitoring

[github-actions]

👋 Greetings, Airbyte Team Member!

Here are some helpful tips and reminders for your convenience.

💡 Show Tips and Tricks

PR Slash Commands

Airbyte Maintainers (that's you!) can execute the following slash commands on your PR:

• 🛠️ Quick Fixes
  • /format-fix - Fixes most formatting issues.
  • /bump-version - Bumps connector versions, scraping changelog description from the PR title.
    • Bump types: patch (default), minor, major, major_rc, rc, promote.
    • The rc type is a smart default: applies minor_rc if stable, or bumps the RC number if already RC.
    • The promote type strips the RC suffix to finalize a release.
    • Example: /bump-version type=rc or /bump-version type=minor
  • /bump-progressive-rollout-version - Alias for /bump-version type=rc. Bumps with an RC suffix and enables progressive rollout.
• ❇️ AI Testing and Review (internal link: AI-SDLC Docs):
  • /ai-prove-fix - Runs prerelease readiness checks, including testing against customer connections.
  • /ai-canary-prerelease - Rolls out prerelease to 5-10 connections for canary testing.
  • /ai-review - AI-powered PR review for connector safety and quality gates.
• 📝 AI Documentation:
  • /ai-docs-review - AI-powered documentation review for PRs with connector changes.
  • /ai-create-docs-pr - Creates a documentation PR for connector changes, stacked on the current PR.
• 🚀 Connector Releases:
  • /publish-connectors-prerelease - Publishes pre-release connector builds (tagged as {version}-preview.{git-sha}) for all modified connectors in the PR.
  • /enable-autopilot-rollouts - Enables autopilot progressive rollouts for the modified connector(s) in the PR, remediating "autopilot rollouts not enabled for {connector-name}" auto-merge blockers. Sets defaultRolloutMode: autopilot and enableProgressiveRollout: true, preserving any existing autopilotConfig.
    • Optional args: connector=<CONNECTOR_NAME> (defaults to the modified connectors in the PR), strategy=fast|slow|default (defaults to fast).
    • Example: /enable-autopilot-rollouts or /enable-autopilot-rollouts connector=source-faker strategy=slow
• ☕️ JVM connectors:
  • /update-connector-cdk-version connector=<CONNECTOR_NAME> - Updates the specified connector to the latest CDK version.
    Example: /update-connector-cdk-version connector=destination-bigquery
• 🐍 Python connectors:
  • /poe connector source-example lock - Run the Poe lock task on the source-example connector, committing the results back to the branch.
  • /poe source example lock - Alias for /poe connector source-example lock.
  • /poe source example use-cdk-branch my/branch - Pin the source-example CDK reference to the branch name specified.
  • /poe source example use-cdk-latest - Update the source-example CDK dependency to the latest available version.
• ⚙️ Admin commands:
  • /force-merge reason="<REASON>" - Force merges the PR using admin privileges, bypassing CI checks. Requires a reason.
    Example: /force-merge reason="CI is flaky, tests pass locally"

📚 Show Repo Guidance

Helpful Resources

• Breaking Changes Guide - Breaking changes, migration guides, and upgrade deadlines
• Developing Connectors Locally
• Managing Connector Secrets
• On-Demand Regression Tests
• #connector-ci-issues
• #connector-publish-updates
• #connector-build-statuses

📝 Edit this welcome message.

[github-actions]

Deploy preview for airbyte-docs ready!

Project:	airbyte-docs
Status:	✅  Deploy successful!
Preview URL:	https://airbyte-docs-ke6lr7kor-airbyte-growth.vercel.app
Latest Commit:	762adcb

Deployed with vercel-action

[octavia-bot-admin]

Auto-approved by auto-merge workflow.