@mitre/hdf-schema 3.6.0-rc.5 → 3.6.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/ts/hdf.d.ts CHANGED
@@ -48,6 +48,18 @@ export interface HDFResults {
48
48
  * results. May be a relative path, absolute URI, or fragment identifier.
49
49
  */
50
50
  planRef?: string;
51
+ /**
52
+ * Hash of this results document as it stood immediately before the most recent amendment
53
+ * application. Written by `hdf amend apply` when it applies at least one override; an apply
54
+ * that matches nothing leaves the document untouched. The hash covers the results file's
55
+ * RAW BYTES as read, not a canonical form, so reproducing it requires the byte-identical
56
+ * original — reformatting or re-serializing the source changes the value. Only the most
57
+ * recent pre-application state is recorded: applying amendments to an already-amended
58
+ * document REPLACES this value, so it is a single link back one step, not a growing chain.
59
+ * Distinct from the `previousChecksum` inside an override, which chains amendments to each
60
+ * other and is computed over a canonical JSON form.
61
+ */
62
+ preAmendmentChecksum?: Checksum;
51
63
  /**
52
64
  * Optional reference to automated remediation resources (Ansible playbooks, Terraform
53
65
  * scripts, etc.) for fixing failing requirements found in this assessment.
package/dist/ts/hdf.ts CHANGED
@@ -46,6 +46,18 @@ export interface HDFResults {
46
46
  * results. May be a relative path, absolute URI, or fragment identifier.
47
47
  */
48
48
  planRef?: string;
49
+ /**
50
+ * Hash of this results document as it stood immediately before the most recent amendment
51
+ * application. Written by `hdf amend apply` when it applies at least one override; an apply
52
+ * that matches nothing leaves the document untouched. The hash covers the results file's
53
+ * RAW BYTES as read, not a canonical form, so reproducing it requires the byte-identical
54
+ * original — reformatting or re-serializing the source changes the value. Only the most
55
+ * recent pre-application state is recorded: applying amendments to an already-amended
56
+ * document REPLACES this value, so it is a single link back one step, not a growing chain.
57
+ * Distinct from the `previousChecksum` inside an override, which chains amendments to each
58
+ * other and is computed over a canonical JSON form.
59
+ */
60
+ preAmendmentChecksum?: Checksum;
49
61
  /**
50
62
  * Optional reference to automated remediation resources (Ansible playbooks, Terraform
51
63
  * scripts, etc.) for fixing failing requirements found in this assessment.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@mitre/hdf-schema",
3
- "version": "3.6.0-rc.5",
3
+ "version": "3.6.0",
4
4
  "description": "JSON schemas and multi-language type definitions for Heimdall Data Format (HDF)",
5
5
  "publishConfig": {
6
6
  "access": "public"
@@ -65,7 +65,7 @@
65
65
  "dependencies": {
66
66
  "ajv": "^8.17.0",
67
67
  "ajv-formats": "^3.0.0",
68
- "@mitre/hdf-utilities": "^3.6.0-rc.5"
68
+ "@mitre/hdf-utilities": "^3.6.0"
69
69
  },
70
70
  "devDependencies": {
71
71
  "@hyperjump/json-schema": "^1.17.2",