@openvtc/trust-tasks 0.2.59 → 0.2.60
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/README.md +20 -9
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -156,15 +156,26 @@ validator.
|
|
|
156
156
|
|
|
157
157
|
## Versioning
|
|
158
158
|
|
|
159
|
-
The package version (
|
|
160
|
-
|
|
161
|
-
|
|
162
|
-
|
|
163
|
-
|
|
164
|
-
|
|
165
|
-
|
|
166
|
-
|
|
167
|
-
The
|
|
159
|
+
The package version follows [Semantic Versioning](https://semver.org/) over
|
|
160
|
+
**this package's own API** — the exported types, the runtime, and the generated
|
|
161
|
+
module surface. A breaking change to any of those bumps the leading non-zero
|
|
162
|
+
component (`0.2.x` → `0.3.0` while below 1.0); anything additive is a patch.
|
|
163
|
+
Behavioural changes count: when a specification starts declaring `proof`
|
|
164
|
+
REQUIRED, `consumeInbound` rejects documents it previously accepted, and the
|
|
165
|
+
version has to reflect that even though the wire format is unchanged.
|
|
166
|
+
|
|
167
|
+
The version is **not** tied to the [`SPEC.md`](https://trusttasks.org/SPEC)
|
|
168
|
+
framework revision, which it once claimed to track. The two move for different
|
|
169
|
+
reasons — a framework revision can change the spec-authoring contract without
|
|
170
|
+
altering a single generated type. Read a document's framework version from the
|
|
171
|
+
specification's `targetFrameworkVersion` declaration instead.
|
|
172
|
+
|
|
173
|
+
A bump in an individual spec's own `MAJOR.MINOR` ships as a new exported module
|
|
174
|
+
name (`AclGrant_v1_0` alongside `AclGrant_v0_1`) and so is additive here.
|
|
175
|
+
|
|
176
|
+
`trust-tasks-rs` and `@openvtc/trust-tasks` are released together and carry
|
|
177
|
+
matching version numbers, so a given pair is known to be generated from the
|
|
178
|
+
same registry revision.
|
|
168
179
|
|
|
169
180
|
## License
|
|
170
181
|
|