Repository navigation
Date: 2026-11-15
Previous release: v0.6.1
Summary
The release publishes manifest.json, and versions.yaml records every reference with the fields results.json and the manifest take from it. OT Fabric's own image is scanned before it is pushed. Images, the container contract and the fixtures are unchanged.
Added
manifest.jsonin the GitHub release, written byscripts/release-manifest.py: the release version and commit, the contract and fixture schema versions, the platforms, and per published reference its image by digest and its upstream (name, repository, version, revision, licence, roles). The release fails without a digest for every reference thatversions.yamlmarkspublished: true.images.txtstays.versions.yaml:native_snap7gainsname,version(f6ff90317ca5, the short revision: the SCADACS fork has no releases),rolesandpublished;python_snap7gainsrepository,license,rolesandpublished.scripts/check-versions.shalso checks that the Snap7 version is the short revision of the Dockerfile's, and that a reference ispublished: trueexactly whenPUBLISHED_ADAPTERSof the Makefile andimages:name it.
Changed
scripts/report-to-results.pytakes the name, repository, version, revision and licence of the references fromversions.yaml(scripts/references.py) instead of constants, and refuses an entry without them.results.jsonis unchanged except that python-snap7 now has itsupstream.- The Own stack (go-s7comm) workflow scans
snap7-interop-otfabricwith the release gate (Trivy, fixable CRITICAL and HIGH) before it pushes it. SECURITY.md says that this image is scanned like the release images and that it has a floating:latest, which a rebuild replaces. own/go-s7commrequires go-cotp v1.4.2 and go-tpkt v1.2.2 (fewer allocations per segment and packet; nothing changes on the wire or in the API). The image is published by hand, outside this release.- CONTRIBUTING.md, When CI runs: what the release workflow runs.
Documentation
docs/COMPATIBILITY.md, Write to a read-only area, and the README: a real CPU 1214C DC/DC/DC (S7-1200, firmware V4.2) answers a write to a write-protected DB with item code0x03and no header error. The capture was posted on python-snap7#976 and is kept in go-s7comm'stestdata/captures. Theotfabricimage's0x03is the code this CPU sends. An S7-300 or S7-1500 is still open (#19).
Images
| Image | Digest |
|---|---|
ghcr.io/otfabric/snap7-interop-native:v0.7.0 |
sha256:5d15923abaf53186a0732fc4e0c64b3b4a2a70432f643a9a3eda1c2cf9e5b9ef |
ghcr.io/otfabric/snap7-interop-python:v0.7.0 |
sha256:2c8c5bcb250d99a6bc11604b5270eb91c00ee58cc7396345f5d6861559c82673 |
Pinning in a consumer
docker pull ghcr.io/otfabric/snap7-interop-native@sha256:5d15923abaf53186a0732fc4e0c64b3b4a2a70432f643a9a3eda1c2cf9e5b9ef
docker pull ghcr.io/otfabric/snap7-interop-python@sha256:2c8c5bcb250d99a6bc11604b5270eb91c00ee58cc7396345f5d6861559c82673manifest.json (and images.txt) and versions.yaml record the images and the upstream pins they were built from. The native image contains Snap7 (LGPL-3.0-or-later), the Python image python-snap7 (MIT); see THIRD_PARTY_NOTICES.md.