#289: Changed prefetch token status change to a Major change, rather than a Patch change.

Author: brynrhodes

docs/specification/1.0.md

@@ -848,7 +848,7 @@ The following types of changes are possible for a hook definition:
 Change | Version Impact
 ------ | ----
 Clarifications and corrections to documentation that do not impact functionality | Patch
-Change of prefetch token status of an existing context field | Patch
+Change of prefetch token status of an existing context field | Major
 Addition of a new, REQUIRED field to the context | Major
 Addition of a new, OPTIONAL field to the context | Minor
 Change of optionality of an existing context field | Major
@@ -859,6 +859,8 @@ Change of semantics of the hook | Major
 
 When a major change is made, the hook definition MUST be published under a new name. When a minor or patch change is made, the hook version MUST be updated. Hook definers MUST use [semantic versioning](https://semver.org/) to communicate the impact of changes in an industry standard way.
 
+> Note that the intent of this table is to outline possible breaking changes. The authors have attempted to enumerate these types of changes exhaustively, but as new types of breaking changes are identified, this list will be updated.
+
 #### Change Log
 
 Changes made to a hook MUST be documented in a change log to ensure hook consumers can track what has been changed over the life of a hook. The change log MUST contain the following elements: