Skip to content

docs(source-hubspot): fix 6.5.3 changelog date and clarify subject - #76836

Closed
devin-ai-integration[bot] wants to merge 2 commits into
masterfrom
devin/1776770961-hubspot-changelog-fix
Closed

devin-ai-integration[bot] wants to merge 2 commits into
masterfrom
devin/1776770961-hubspot-changelog-fix

Conversation

@devin-ai-integration

Copy link
Copy Markdown
Contributor

Documentation Confidence Assessment

Overall Confidence: 3/5

Dimension Score Rationale
Code Comprehension 3/5 HubSpot is a Python CDK connector with complex multi-file logic, but this change does not require deep code comprehension.
API Documentation Quality 5/5 HubSpot has comprehensive public API docs covering auth, scopes, rate limits, and endpoints.
Change Scope & Risk 5/5 Single-line changelog edit: corrects a date and rewords a subject.
Existing Doc Maturity 5/5 627-line mature document with comprehensive coverage of prerequisites, setup, streams, and troubleshooting.
Connector Sensitivity 1/5 HubSpot is a top-tier certified connector; errors affect many users.
Triggering Context 5/5 Triggered from a small, merged chore PR (base image bump for a CDK deadlock fix).

Composite (rounded down): 3/5 — warrants a quick human review despite the minimal change, because HubSpot is a top-tier connector.

What I Verified vs. What I Inferred

  • Verified from code / repo: The triggering commit 1922b2a bumps the source-declarative-manifest base image to a pre-release CDK build containing the deadlock fix from airbyte-python-cdk#977, and bumps dockerImageTag from 6.5.2 to 6.5.3.
  • Verified from git log: Commit 1922b2a landed on master on 2026-04-21 (Tue Apr 21 14:26:13 2026 +0300, i.e. 2026-04-21 11:26 UTC). The previous version, 6.5.2 (PR #76641), merged earlier the same day (2026-04-21 06:42 UTC), so the changelog ordering is now internally consistent.
  • Verified from the PR body: The triggering PR description explicitly frames the deadlock as "syncs [that] hang indefinitely when the internal message queue fills up", which is the user-visible effect.
  • Inferred: None of the 6.5.3 changelog content is authored from inference — all edits are based on the commit timestamp and the PR description for chore(source-hubspot): Update SDM base image to CDK with deadlock fix #76073.

Areas of Concern

  • The 6.5.3 release uses a pre-release CDK base image (7.16.0.post1.dev23950401533). The original PR description noted this "should be switched to a stable release before merging to production," but the PR was merged with the pre-release image. This does not need to be documented in the user-facing changelog, but reviewers may want to follow up separately in the connector if a stable CDK swap is planned.

What

Small factual fix to the HubSpot connector changelog for version 6.5.3, introduced by #76073:

  • Date correction: 2026-04-20 → 2026-04-21 to match the actual merge date of the PR that introduced version 6.5.3. The previous version (6.5.2) already shows 2026-04-21, so the prior date made the chronology inconsistent (a later version dated earlier than the version it superseded).
  • Subject rewording: Replaces the implementation-centric phrasing "Update CDK to pre-release with deadlock fix" with a user-facing description of the effect ("Upgrade CDK base image to fix a concurrent-sync deadlock that could cause syncs to hang indefinitely"), grounded in the triggering PR's own description.

How

One-line change in docs/integrations/sources/hubspot.md, in the changelog row for version 6.5.3.

Review Guide

  1. docs/integrations/sources/hubspot.md — changelog row for 6.5.3 only. Confirm the 2026-04-21 date matches the merge date of PR #76073 and that the new subject accurately reflects the user-visible impact of the CDK deadlock fix.

User Impact

Documentation-only. Helps users scanning the changelog see a correct release date and understand the user-visible effect of the CDK upgrade (no more hangs when the internal message queue fills up on concurrent syncs).

Can this PR be safely reverted and rolled back?

  • YES 💚

Note: I am an AI assistant (Devin) and have proposed these documentation updates based on a review of the triggering commit and HubSpot's public API documentation. Reviewers may merge, modify, or close this PR as they see fit.

Link to Devin session: https://app.devin.ai/sessions/0a34b0dca7f24edb9f2f6cef66d7eea2

@devin-ai-integration

Copy link
Copy Markdown
Contributor Author

🤖 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 and CI monitoring

@devin-ai-integration devin-ai-integration Bot added area/documentation Improvements or additions to documentation team/documentation labels Apr 21, 2026
@github-actions

Copy link
Copy Markdown
Contributor

👋 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.
  • 🚀 Connector Releases:
    • /publish-connectors-prerelease - Publishes pre-release connector builds (tagged as {version}-preview.{git-sha}) for all modified connectors in the PR.
  • ☕️ 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

📝 Edit this welcome message.

@airbyte-support-bot

Copy link
Copy Markdown
Contributor

↪️ Triggering /ai-review per Hands-Free AI Triage Project triage next step.

Reason: Docs/chore PR; no runtime behavior change requires prove-fix. Triggering review for PR hygiene and content validation.

Devin session

@octavia-bot
octavia-bot Bot marked this pull request as ready for review April 22, 2026 11:55
@octavia-bot

octavia-bot Bot commented Apr 22, 2026 •

Copy link
Copy Markdown
Contributor

AI PR Review starting...

Reviewing PR for connector safety and quality.
View playbook

✅ Devin AI session created successfully!

@devin-ai-integration

devin-ai-integration Bot commented Apr 22, 2026 •

Copy link
Copy Markdown
Contributor Author

AI PR Review Report

Review Action: APPROVED
Risk Level: 0 — Docs-only single-line changelog edit in docs/integrations/sources/hubspot.md; no runtime behavior changed.

Gate Status
PR Hygiene PASS
Code Hygiene PASS
Test Coverage PASS
Code Security PASS
Per-Record Performance PASS
Breaking Dependencies PASS
Backwards Compatibility PASS
Forwards Compatibility PASS
Behavioral Changes PASS
Out-of-Scope Changes PASS
CI Checks PASS
Live / E2E Tests PASS

📋 PR Details

Connector & PR Info

Connector(s): source-hubspot (user-facing docs only)
PR: #76836
HEAD SHA: 3c5dd3cc797dc9ac6b6948e97d3eff4b935c699f
Session: https://app.devin.ai/sessions/e0433f9d4d754c8d975a755574fadb86

Risk Level

Level: 0 — No production impact
Rationale: The only changed file is docs/integrations/sources/hubspot.md, with a single-line diff (6.5.3 changelog row: date 2026-04-20 → 2026-04-21, subject reworded). Worst case is a docs-side issue; no code, spec, or metadata paths are modified.

Risk Level is reported for downstream consumers (e.g., auto-merge policy, reviewer routing). It does not change the review action — APPROVE here means "no blocking objection," not "safe to merge unattended."

Review Action Details

APPROVED — All enforced gates pass. The workflow will submit an APPROVE PR review via octavia-bot based on the pr_ai_review_result: APPROVE marker. This does NOT authorize auto-merge; the merge decision remains with humans.

Note: PR currently shows a merge conflict against master. That is outside the scope of gate enforcement but the author will need to resolve it before merging.

🔍 Gate Evaluation Details

Gate-by-Gate Analysis

Gate Status Enforced? Details
PR Hygiene PASS Yes PR body is well-populated (What / How / Review Guide / User Impact sections, >>50 chars of visible content). Changelog requirement is inherently satisfied — the edited file IS the docs changelog (docs/integrations/sources/hubspot.md). No unresolved human reviewer comments (all 4 PR comments are from bot accounts: devin-ai-integration[bot], github-actions[bot], airbyte-support-bot, octavia-bot[bot]).
Code Hygiene PASS WARNING No source code modified. Docs-only change is exempt from the test-coverage heuristic.
Test Coverage PASS Yes PR title starts with docs(...) and has no fix/feat/bug/feature behavioral-change indicators. Docs-only change is explicitly exempt under this gate.
Code Security PASS Yes No changed files match security-sensitive path patterns (no *auth*, *oauth*, *token*, *credential*, *secret*, etc.). No security keywords in the diff hunks of docs/integrations/sources/hubspot.md.
Per-Record Performance PASS WARNING No per-record code paths modified (no source.py, streams.py, manifest.yaml, etc.).
Breaking Dependencies PASS WARNING No build.gradle, pyproject.toml, requirements.txt, or poetry.lock changes.
Backwards Compatibility PASS Warning (elevates Risk Level) No spec.json/spec.yaml/manifest.yaml/metadata.yaml changes. No schema, stream, primary-key, or cursor-field changes.
Forwards Compatibility PASS Warning (elevates Risk Level) No state/cursor/pagination/transformation keywords in the changed hunk.
Behavioral Changes PASS Warning (elevates Risk Level) No operational-risk keywords (rate-limit / retry / backoff / timeout / error-handler / page-size / memory) in the diff hunks.
Out-of-Scope Changes PASS Skip Changed file docs/integrations/sources/hubspot.md matches the in-scope docs/** pattern (and is also a *.md markdown file). PR is in scope.
CI Checks PASS Yes All 36 core CI check-runs on HEAD 3c5dd3c are green, 0 failures (14 skipped are conditional jobs that did not need to run for a docs-only PR). Relevant docs checks are green: Docs / MarkDownLint, Docs / Vale, Build Airbyte Docs, Check Changelog Updated, and the Vercel airbyte-docs preview build.
Live / E2E Tests PASS Yes Documentation-only change per the "validation not required" file patterns — no source.py/http_client.py/manifest changes, no bug-fix / API / discovery / sync behavior indicators. The PR title is docs(...) and all diffs are confined to docs/.

Evidence of the Diff

Single-hunk, single-line change in docs/integrations/sources/hubspot.md:

-| 6.5.3 | 2026-04-20 | [76073](...) | Update CDK to pre-release with deadlock fix |
+| 6.5.3 | 2026-04-21 | [76073](...) | Upgrade CDK base image to fix a concurrent-sync deadlock that could cause syncs to hang indefinitely |

PR Description Evidence (PR Hygiene)

  • PR Body Length (raw): ~3000+ chars
  • PR Body Length (after stripping): well above the 50-char minimum
  • PR Body Preview: ## Documentation Confidence Assessment\n\n**Overall Confidence: 3/5**\n\n| Dimension | Score | Rationale ...
  • Includes required sections: What, How, Review Guide, User Impact, rollback confirmation.
📚 Evidence Consulted

Evidence

  • Changed files: 1 file — docs/integrations/sources/hubspot.md (single-line diff in the 6.5.3 changelog row)
  • CI checks on HEAD 3c5dd3c: 36 passed, 0 failed, 0 pending, 14 skipped. Key docs checks (Docs / MarkDownLint, Docs / Vale, Build Airbyte Docs, Check Changelog Updated, Vercel – airbyte-docs) all ✅.
  • PR labels: None of the validation/override labels (live-tests-passed, prerelease-validated, community, etc.) apply; no labels were required for this docs-only change.
  • PR description: Present and well-populated (What / How / Review Guide / User Impact sections).
  • Existing bot reviews for this HEAD SHA: none — this is the first AI review on 3c5dd3c.
  • Merge status: conflict against master (outside of gate enforcement, but flagged for the author).

Devin session

…bspot-changelog-fix

# Conflicts:
#	docs/integrations/sources/hubspot.md
@github-actions

Copy link
Copy Markdown
Contributor

Deploy preview for airbyte-docs ready!

Project:airbyte-docs
Status: ✅  Deploy successful!
Preview URL:https://airbyte-docs-auw85fxbf-airbyte-growth.vercel.app
Latest Commit:9ea5521

Deployed with vercel-action

@davinchia

Copy link
Copy Markdown
Contributor

Closing as obsolete.

The changelog correction this PR proposes has already landed on master independently — the entry now carries the corrected date/PR link. Verified against origin/master today.

No other content in this PR remains applicable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/documentation Improvements or additions to documentation team/documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants