From a87d626dfd16910824eefb6c3a22d3585c247ed8 Mon Sep 17 00:00:00 2001 From: Erik Montnemery Date: Wed, 25 Jun 2025 17:04:19 +0200 Subject: [PATCH] =?UTF-8?q?Align=20"Building=20a=20Python=20library"=20doc?= =?UTF-8?q?umentation=20with=20the=20"Dependency=20=E2=80=A6=20(#2711)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- docs/api_lib_index.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/api_lib_index.md b/docs/api_lib_index.md index fbbcf658..16415c1f 100644 --- a/docs/api_lib_index.md +++ b/docs/api_lib_index.md @@ -8,6 +8,8 @@ One of the foundational rules of Home Assistant is that we do not include any pr ## Basic library requirements - The library must have source distribution packages available, it's not allowed to rely on packages that only have binary distribution packages. +- The library versions published on PyPi should correspond to tagged releases in a public online repository. +- The publishing on PyPi must be automated. - Issue trackers must be enabled for external Python libraries that communicate with external devices or services. - If the library is mainly used for Home Assistant and you are a code owner of the integration, it is encouraged to use an issue template picker with links to [Home Assistant Core Issues](https://github.com/home-assistant/core/issues). For example: [zwave-js-server-python - New Issue](https://github.com/home-assistant-libs/zwave-js-server-python/issues/new/choose) - The library and possible subdependencies of the library must be licensed using an [OSI-approved license](https://opensource.org/license). This should be reflected in the metadata of the library.