The loader step shells out to go get github.com/pdat-cz/pda-fieldbus,
which doesn't resolve (canonical home is git.pda.cz). This repo has no
Go code; loader-level validation is documented as a local workflow in
the README via pda-fieldbus poll --dry-run.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
git describe falls back to literal "v0.0.0" when no tags exist; the
subsequent git log v0.0.0..HEAD then fails silently and the workflow
skips, so the very first feat: commit never produces a tag.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Seed the repo described in pda-fieldbus ADR-0009: a sibling repo that
ships device profiles independently of the fieldbus binary.
Layout:
- profiles/schneider-iem2135.json — distilled from the inline extract
rules in examples/poll-d27-g110.yaml
- profiles/lug-heat-meter-v4.json — heat-meter profile with derived
delta_temperature
Both validate against pda-fieldbus's profile.LoadDirs.
Packaging:
- nfpm.yaml builds pda-fieldbus-profiles.deb installing profiles/ to
/usr/share/pda-fieldbus/profiles/, where the loader's DirPackaged dir
picks them up. Recommends pda-fieldbus.
- .gitea/workflows/auto-tag.yml: same conventional-commit auto-tagging
as pda-fieldbus, on tag push installs nfpm, builds .deb, uploads to
repo.pda.cz/PDAT/main using the existing PDA_REPO_TOKEN secret.
- .gitea/workflows/ci.yml: JSON syntax check + schema validation by
importing pda-fieldbus's loader and calling LoadDirs against profiles/.
TomUvi