From 1b94d74dc34b6a31b81ea7119e1db08466449b71 Mon Sep 17 00:00:00 2001 From: "Joseph T. Lyons" Date: Fri, 3 Oct 2025 08:32:24 -0400 Subject: [PATCH] Clarify extension license detection in docs (#39456) Release Notes: - N/A --- docs/src/extensions/developing-extensions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/extensions/developing-extensions.md b/docs/src/extensions/developing-extensions.md index 1fa6509011e45e61de2f745c99c3ab84a495fe05..ae801dd9da7f0e35bd15d705dc71601fba97dae5 100644 --- a/docs/src/extensions/developing-extensions.md +++ b/docs/src/extensions/developing-extensions.md @@ -123,7 +123,7 @@ As of October 1st, 2025, extension repositories must include one of the followin This allows us to distribute the resulting binary produced from your extension code to our users. Without a valid license, the pull request to add or update your extension in the following steps will fail CI. -Your license file should be at the root of your extension repository with a filename like `LICENSE`, `LICENSE.txt`, `LICENSE-MIT`, etc. For the logic on how license files are identified, see the [license validation source code](https://github.com/zed-industries/extensions/blob/main/src/lib/license.js). +Your license file should be at the root of your extension repository. Any filename that has `LICENCE` or `LICENSE` as a prefix (case insensitive) will be inspected to ensure it matches one of the accepted licenses. See the [license validation source code](https://github.com/zed-industries/extensions/blob/main/src/lib/license.js). > This license requirement applies only to your extension code itself (the code that gets compiled into the extension binary). > It does not apply to any tools your extension may download or interact with, such as language servers or other external dependencies.