@@ -12,20 +12,20 @@ This policy applies to all kube-state-metrics maintainers and all third-party pa
12
12
13
13
kube-state-metrics maintainers must follow these guidelines when consuming third-party packages:
14
14
15
- - Only use third-party packages that are necessary for the functionality of kube-state-metrics.
16
- - Use the latest version of all third-party packages whenever possible.
17
- - Avoid using third-party packages that are known to have security vulnerabilities.
18
- - Pin all third-party packages to specific versions in the kube-state-metrics codebase.
19
- - Use a dependency management tool, such as Go modules, to manage third-party dependencies.
15
+ * Only use third-party packages that are necessary for the functionality of kube-state-metrics.
16
+ * Use the latest version of all third-party packages whenever possible.
17
+ * Avoid using third-party packages that are known to have security vulnerabilities.
18
+ * Pin all third-party packages to specific versions in the kube-state-metrics codebase.
19
+ * Use a dependency management tool, such as Go modules, to manage third-party dependencies.
20
20
21
21
## Procedure
22
22
23
23
When adding a new third-party package to kube-state-metrics, maintainers must follow these steps:
24
24
25
- 1 . Evaluate the need for the package. Is it necessary for the functionality of kube-state-metrics?
26
- 2 . Research the package. Is it actively maintained? Does it have a good reputation?
27
- 3 . Choose a version of the package. Use the latest version whenever possible.
28
- 4 . Pin the package to the specific version in the kube-state-metrics codebase.
25
+ 1 . Evaluate the need for the package. Is it necessary for the functionality of kube-state-metrics?
26
+ 2 . Research the package. Is it actively maintained? Does it have a good reputation?
27
+ 3 . Choose a version of the package. Use the latest version whenever possible.
28
+ 4 . Pin the package to the specific version in the kube-state-metrics codebase.
29
29
5 . Update the kube-state-metrics documentation to reflect the new dependency.
30
30
31
31
## Enforcement
0 commit comments