feat: deprecate async_enabled replication argument removed server-side

[LijuanTang94]

Summary

Closes #2047

The asyncEnabled field was removed from the Weaviate server schema in v1.38 (weaviate/weaviate#11214). The client still accepted async_enabled and forwarded it on the write path, so the server silently dropped it — the user's intent was lost without any indication.

This PR adds a DeprecationWarning so the silent loss becomes visible, following the exact precedent the maintainers established for max_workers / alive_nodes_checking_frequency (Dep029) when those async_config fields were removed in v1.37.3.

Approach

I deliberately chose deprecate-and-warn over hard removal (the issue's step 3 offers both):

• Removing the public async_enabled kwarg outright would break any existing user code calling Configure.replication(async_enabled=...).
• The existing Dep029 handling keeps the kwarg + keeps forwarding (server drops it) + warns. This PR mirrors that pattern for consistency and zero breakage.

If the maintainers prefer to also drop the read-path field (_ReplicationConfig.async_enabled + the parser in config_methods.py, which now always reports a misleading False), I'm happy to extend the PR — I left it out to keep this change focused and non-breaking, and because removing a read attribute is a larger compatibility decision.

Changes

• weaviate/warnings.py — new Dep030 deprecation warning
• weaviate/collections/classes/config.py — Configure.replication and Reconfigure.replication emit the warning when async_enabled is passed; docstrings updated
• test/collection/test_config.py — tests that the warning fires when async_enabled is passed and stays silent otherwise (both factories)

Testing

pytest test/collection/test_config.py test/collection/test_config_update.py test/collection/test_config_methods.py
# 210 passed
ruff check / ruff format --check   # clean
flake8 (+ pydoclint, flake8-docstrings)  # clean

[orca-security-eu]

Orca Security Scan Summary

Status	Check	Issues by priority
Passed	Infrastructure as Code	0   0   0   0	View in Orca
Passed	SAST	0   0   0   0	View in Orca
Passed	Secrets	0   0   0   0	View in Orca
Passed	Vulnerabilities	0   0   0   0	View in Orca

[weaviate-git-bot]

To avoid any confusion in the future about your contribution to Weaviate, we work with a Contributor License Agreement. If you agree, you can simply add a comment to this PR that you agree with the CLA so that we can merge.

beep boop - the Weaviate bot 👋🤖

PS:
Are you already a member of the Weaviate Forum?

[LijuanTang94]

I have read the CLA Document and I hereby agree to the terms of the CLA. 获取 Outlook for iOS<https://aka.ms/o0ukef>

…

________________________________ 发件人: Weaviate Git Bot ***@***.***> 发送时间: Sunday, May 31, 2026 4:00:56 PM 收件人: weaviate/weaviate-python-client ***@***.***> 抄送: Lijuan Tang ***@***.***>; Author ***@***.***> 主题: Re: [weaviate/weaviate-python-client] feat: deprecate `async_enabled` replication argument removed server-side (PR #2050) [https://avatars.githubusercontent.com/u/83967968?s=20&v=4]weaviate-git-bot left a comment (weaviate/weaviate-python-client#2050)<#2050 (comment)> To avoid any confusion in the future about your contribution to Weaviate, we work with a Contributor License Agreement<https://weaviate.io/service/contributor-license-agreement>. If you agree, you can simply add a comment to this PR that you agree with the CLA so that we can merge. beep boop - the Weaviate bot 👋🤖 PS: Are you already a member of the Weaviate Forum?<https://forum.weaviate.io/> — Reply to this email directly, view it on GitHub<#2050?email_source=notifications&email_token=BEY3V5HHLE24WPHDMEBFOYD45S2SRA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINJYHA2DQOJQGIY2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-4588489021>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BEY3V5D7NK32NISWJNKZ3PD45S2SRAVCNFSM6AAAAACZUX23SSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DKOBYGQ4DSMBSGE>. You are receiving this because you authored the thread.Message ID: ***@***.***>