Update the upstream pins

The watch reports a newer ATT&CK release, a pinned bundle that a release changes or drops, a licence that is not the pinned one, a newer ADM release, a moved tag and a check that could not finish.¹

1. For a new ATT&CK release, read MITRE’s notes and move the manifest’s tag, commit and each bundle’s address, size, SHA-256 and git object hash together.² Move the schema header’s version, source and data commit with them; tests/test_upstream.py holds the three equal.³
2. Run just test-attack-data. Where the new data departs from the ADM in a new way, change the schema to follow the data and list the departure, with its reason and count, in tests/test_upstream.py.
3. For a new ADM release, read its change log, check the schema against it, and move PINNED_ADM_TAG and PINNED_ADM_COMMIT, the header’s annotations and NOTICE together.
4. For a changed licence, read it, copy it again to tests/data/attack-stix-data/LICENSE.txt, move its hash in the manifest and update NOTICE.
5. For a stix release, copy its six modules into src/attack/schema/stix/ whole and move STIX_COMMIT and the hashes in tests/test_stix_import.py.⁴

Footnotes

Section titled “Footnotes”

1. scripts/check_upstream_release.py, the docstring ↩

2. tests/data/attack-stix-data/manifest.json ↩

3. CONTRIBUTING.md, Render the pinned versions ↩

4. tests/test_stix_import.py, STIX_COMMIT and PINNED_BLOBS ↩