From 0a2cfa3fc177de4d81dfeb4fcf4c8746c79dae69 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ville=20Skytt=C3=A4?= Date: Sat, 26 Apr 2025 00:49:58 +0300 Subject: [PATCH] Clarify dep transparency build/publish requirement (#2656) --- .../integration-quality-scale/rules/dependency-transparency.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/core/integration-quality-scale/rules/dependency-transparency.md b/docs/core/integration-quality-scale/rules/dependency-transparency.md index 7ed726ea..f50c6269 100644 --- a/docs/core/integration-quality-scale/rules/dependency-transparency.md +++ b/docs/core/integration-quality-scale/rules/dependency-transparency.md @@ -13,7 +13,7 @@ In order for the project to trust the dependencies, we have a set of requirement - The source code of the dependency must be available under an OSI-approved license. - The dependency must be available on PyPI. -- The package published to PyPi should be built and published inside a CI pipeline. +- The package published to PyPI should be built in and published from a public CI pipeline. - The version of the dependency published on PyPI should correspond to a tagged release in an open online repository. ## Exceptions