chore(source-azure-blob-storage): pin CDK prerelease to validate state throttle (do not merge)

[devin-ai-integration]

What

Validation-only PR requested by gl_anatolii.yatsuk, to check how the CDK per-slice state throttle (airbytehq/airbyte-python-cdk#1104) lands on the legacy file-based connectors that are not already covered by #83749 (source-gcs) and #83750 (source-s3).

The throttle is inherited, not opted into: every connector whose streams derive from DefaultFileBasedStream picks it up on its next CDK bump, with no code change of its own. This connector is one of those, so the purpose here is to get a regression run against the prerelease CDK and confirm records and final state are unchanged.

Do not merge — the CDK constraint is pinned to an unreleased dev build.

How

Pin only, no connector code touched:

-airbyte-cdk = {extras = ["file-based"], version = "^7.0.0"}
+airbyte-cdk = {extras = ["file-based"], version = "==7.23.8.post16.dev31038498812"}

plus the matching patch version bump in pyproject.toml / metadata.yaml, a regenerated poetry.lock, and one changelog row. The changelog row's PR link is a PRNUM placeholder until this PR has a number.

Review guide

1. pyproject.toml — the pin, and nothing else in the dependency list
2. metadata.yaml + docs changelog — version bump bookkeeping
3. poetry.lock — regenerated with poetry lock, resolves airbyte-cdk to 7.23.8.post16.dev31038498812

User Impact

None intended beyond the throttle itself: state messages emitted per file are capped at one per 600s, with the first slice and the final state always emitted, so the destination still receives the complete cursor. Records are unaffected.

The accepted tradeoff, same as on gcs and s3: a failed sync can re-read up to 10 minutes of files.

Not to be rolled out — validation only.

Can this PR be safely reverted and rolled back?

• YES 💚

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

[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]

Note

Autopilot progressive rollouts are not enabled for the following modified connector(s):

• source-azure-blob-storage

This is a courtesy heads-up only — it does not block merge or fail any check.
To enable automatic progressive rollouts for the connector(s) above, comment
/enable-autopilot-rollouts on this PR. This sets defaultRolloutMode: autopilot
and enableProgressiveRollout: true in each connector's metadata.yaml,
preserving any existing autopilotConfig.

[github-actions]

Deploy preview for airbyte-docs ready!

Project:	airbyte-docs
Status:	✅  Deploy successful!
Preview URL:	https://airbyte-docs-1327gqzpd-airbyte-growth.vercel.app
Latest Commit:	5a63e0b

Deployed with vercel-action

[github-actions]

source-azure-blob-storage Connector Test Results

37 tests   23 ✅  1m 48s ⏱️
 2 suites  14 💤
 2 files     0 ❌

Results for commit 5a63e0b.