Skip to content

Commit 2249cc1

Browse files
committed
Update documenation
1 parent 634b433 commit 2249cc1

File tree

1 file changed

+1
-11
lines changed

1 file changed

+1
-11
lines changed

content/terms/explanation/technical-upgrades.md

Lines changed: 1 addition & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -115,12 +115,6 @@ When you upgrade the engine or dependencies, extraction logic may change even if
115115
- Re-extracts using updated code
116116
- Creates a new version marked as a technical upgrade if output differs
117117

118-
### Special cases
119-
120-
**No existing version:** For terms that have never been tracked before, the technical upgrade is skipped because there is no existing version to upgrade.
121-
122-
**Missing snapshots:** Technical upgrades cannot extract content without snapshots. If a source document has no snapshot, no version can be created. However, for combined terms, if you add a new source document to the declaration, technical upgrades will fetch and record snapshots only for these newly added documents, then combine them with existing snapshots to create the upgraded version.
123-
124118
## Technical upgrade markers
125119

126120
Versions created during technical upgrades are marked with:
@@ -132,8 +126,4 @@ Versions created during technical upgrades are marked with:
132126

133127
Technical upgrades run automatically with `npx ota track`.
134128

135-
To run them separately:
136-
137-
```bash
138-
npx ota apply-technical-upgrades
139-
```
129+
To run them separately, see the [apply-technical-upgrades command]({{< relref "api/cli#applying-technical-upgrades" >}}).

0 commit comments

Comments
 (0)