From 19e3e060e67c6849edb567dba0359f151540abdc Mon Sep 17 00:00:00 2001 From: Dimitri Yatsenko Date: Sun, 19 Jul 2026 10:56:44 -0500 Subject: [PATCH] docs: fix misleading deprecation example in versioning guide The version-deprecated admonition example claimed `allow_direct_insert` is deprecated in favor of `dj.config['safemode']`. Both are wrong: allow_direct_insert is a current insert() parameter (guards direct inserts into auto-populated tables), and safemode is an unrelated setting (the delete/drop confirmation prompt). Replace with a generic old_method()/new_method() placeholder so the style example can't be read as a factual deprecation claim. --- src/about/versioning.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/about/versioning.md b/src/about/versioning.md index 365618c2..1314abfb 100644 --- a/src/about/versioning.md +++ b/src/about/versioning.md @@ -58,7 +58,7 @@ Version admonitions are used for features introduced **after 2.0** (i.e., versio !!! version-deprecated "Deprecated in 2.1, removed in 3.0" - The `allow_direct_insert` parameter is deprecated. Use `dj.config['safemode']` instead. + The `old_method()` is deprecated. Use `new_method()` instead. **Note:** Features deprecated at the 2.0 baseline (coming from pre-2.0) are documented in the [Migration Guide](../how-to/migrate-to-v20.md) rather than with admonitions, since this documentation assumes 2.0 as the baseline.