NAPALM/driver-standard
1
0 Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity
4 Commits 1 Branch 0 Tags
a4858e9a1fdce2ab454c02d9d4cae5a3ffae943f
Commit Graph
2 Commits
Author SHA1 Message Date
christianmanivong ba133d9de3 fix(ci): audit the package's dependencies, not the tool venv
CI / test (3.12) (pull_request) Successful in 28s
Details
CI / test (3.13) (pull_request) Successful in 26s
Details
CI / test (3.11) (pull_request) Successful in 2m31s
Details 
The device-types pilot failed pip-audit on pip 25.0.1 of the venv that also
held bandit and pip-audit. The package now goes into a venv of its own with
a current pip; its frozen set (URL installs left out) is what pip-audit
checks.
 2026-10-22 19:14:55 +02:00
christianmanivong db6b2e4ea7 feat: standards, shared CI and release tooling for NAPALM drivers
CI / test (3.11) (push) Successful in 34s
Details
CI / test (3.12) (push) Successful in 30s
Details
CI / test (3.13) (push) Successful in 37s
Details 
STANDARDS.md binds every repository in the NAPALM org: one default branch,
Conventional Commits, the device-types contract, test-driven development,
clean-code limits, a quality ratchet for existing code, packaging rules and
releases by tag to PyPI.

napalm-standard holds what a tool can check: the conformance check (with
release rules on a tag), the quality ratchet (ported from netOrk's
quality_ratchet.py), and the Gitea release from the CHANGELOG section.
.gitea/workflows/driver.yml is the CI every driver calls; template/ is a new
driver's starting point and passes the check as it is.
 2026-10-22 19:01:14 +02:00