From c3290b876531fbb2cad5ebc6af9aba7a7d0636f6 Mon Sep 17 00:00:00 2001 From: Joe Mooring Date: Tue, 4 Feb 2025 07:13:22 -0800 Subject: [PATCH] Changes related to release of v0.144.0 --- content/en/troubleshooting/deprecation.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/troubleshooting/deprecation.md b/content/en/troubleshooting/deprecation.md index 81f2724a3..9a0c7ce9e 100644 --- a/content/en/troubleshooting/deprecation.md +++ b/content/en/troubleshooting/deprecation.md @@ -29,8 +29,8 @@ Common [reasons for deprecation]: After the project team deprecates something in code, Hugo will: -1. Log an INFO message for 6 minor releases[^1] -1. Log a WARN message for another 6 minor releases +1. Log an INFO message for 3 minor releases[^1] +1. Log a WARN message for another 12 minor releases 1. Log an ERROR message and fail the build thereafter To see the INFO messages, you must use the `--logLevel` command line flag: