From 30eecb95238ed7bfe9ee8472618809967ac90562 Mon Sep 17 00:00:00 2001 From: "Jason R. Coombs" Date: Fri, 2 Aug 2024 17:33:08 -0400 Subject: [PATCH] Finalize --- NEWS.rst | 9 +++++++++ newsfragments/668.feature.rst | 1 - 2 files changed, 9 insertions(+), 1 deletion(-) delete mode 100644 newsfragments/668.feature.rst diff --git a/NEWS.rst b/NEWS.rst index d9e51cd7..34093be3 100644 --- a/NEWS.rst +++ b/NEWS.rst @@ -1,3 +1,12 @@ +v25.3.0 +======= + +Features +-------- + +- Deprecated support for empty usernames. Now all backends will reject an empty string as input for the 'username' field when setting a password. Later this deprecation will become a more visible user warning and even later an error. If this warning is triggered in your environment, please consider using a static value (even 'username') or comment in the issue and describe the use-case that demands support for empty usernames. (#668) + + v25.2.1 ======= diff --git a/newsfragments/668.feature.rst b/newsfragments/668.feature.rst deleted file mode 100644 index f4b98274..00000000 --- a/newsfragments/668.feature.rst +++ /dev/null @@ -1 +0,0 @@ -Deprecated support for empty usernames. Now all backends will reject an empty string as input for the 'username' field when setting a password. Later this deprecation will become a more visible user warning and even later an error. If this warning is triggered in your environment, please consider using a static value (even 'username') or comment in the issue and describe the use-case that demands support for empty usernames. \ No newline at end of file