NAPALM/driver-standard
1
0 Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity
15 Commits 1 Branch 0 Tags
0e74cbbd3efe13fda2ca8cdc38bf554cff9f815d
Commit Graph
4 Commits
Author SHA1 Message Date
Christian Manivong aa66944e3c chore: the template's floor on napalm is 5.1 (#6)
CI / test (3.12) (pull_request) Successful in 30s
Details
CI / test (3.13) (pull_request) Successful in 28s
Details 
napalm 5.0 and older import pkg_resources, which a Python 3.12 venv no
longer has; every driver's lowest job failed on it.
 2026-10-27 10:50:25 +01:00
Christian Manivong 8cbcd20a3a chore: Python 3.12 is the floor, part A (#6)
CI / test (3.13) (pull_request) Successful in 30s
Details
CI / test (3.12) (pull_request) Successful in 35s
Details 
The shared workflow tests on 3.12 and 3.13 by default and runs lowest on
3.12; the template declares requires-python >=3.12 with ruff and mypy on
3.12, and the tool itself needs 3.12. netOrk runs every driver on 3.12 in
its own containers.

check keeps accepting a 3.10 floor until every driver has moved; part B
raises it.
 2026-10-27 10:10:15 +01:00
christianmanivong 0b21f62553 fix(check): SPDX license string; E501 off in tests (device-types pilot) 
The pilot's build warned that setuptools refuses a license table and
License classifiers from 2027-02-18 (PEP 639); check now reports both and
the template builds with setuptools>=77. Recorded device output in tests
keeps its lines, so the template turns E501 off under tests/.
 2026-10-22 19:08:06 +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