From 32abc3b1e682b38f127ba09128c1007af5db46a2 Mon Sep 17 00:00:00 2001 From: Mike McQuaid Date: Wed, 14 Feb 2024 17:11:09 +0000 Subject: [PATCH] Update docs/Deprecating-Disabling-and-Removing-Casks.md Co-authored-by: Bo Anderson --- docs/Deprecating-Disabling-and-Removing-Casks.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/Deprecating-Disabling-and-Removing-Casks.md b/docs/Deprecating-Disabling-and-Removing-Casks.md index 7e9264e6b5..fcccf0517d 100644 --- a/docs/Deprecating-Disabling-and-Removing-Casks.md +++ b/docs/Deprecating-Disabling-and-Removing-Casks.md @@ -20,9 +20,10 @@ The most common reasons for deprecation are when the upstream project is depreca Casks should only be be deprecated if at least one of the following are true: -- the cask does not install on any of our supported macOS versions +- the software installed by the cask cannot be run on any of our supported macOS versions - the cask has outstanding CVEs - the cask has [zero installs in the last 90 days](https://formulae.brew.sh/analytics/cask-install/90d/) +- the software installed by the cask has been discontinued upstream To deprecate a cask, add a `deprecate!` call. This call should include a deprecation date in the ISO 8601 format and a deprecation reason: