From 9b87cae49bcdf46e8bf507a7b51eb4f3327b29f5 Mon Sep 17 00:00:00 2001 From: Ole Herman Schumacher Elgesem Date: Mon, 14 Jul 2025 14:54:03 +0200 Subject: [PATCH] JSON.md: Fixed outdated explanation of replace_version Signed-off-by: Ole Herman Schumacher Elgesem --- JSON.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/JSON.md b/JSON.md index ca7704f7..d4eaed2b 100644 --- a/JSON.md +++ b/JSON.md @@ -274,9 +274,9 @@ In `cfbs.json`'s `"steps"`, the build step name must be separated from the rest (This is to try to catch mistakes). - `n` must be an integer, from 1 to 1000, and may optionally have a trailing `+` to signify "or more". At most 1000 replacements will be performed, regardless of whether you specify `+` or not. -- `replace_version ` +- `replace_version ` - Replace the string inside the file with the version number of that module. - - The module must have a version and the string must occur exactly once in the file. + - Works identically to `replace`, except the string to replace with, i.e. the version number, is found automatically. When `def.json` is modified during a `json`, `input`, `directory`, `bundles`, or `policy_files` build step, the values of some lists of strings are deduplicated, when this does not make any difference in behavior. These cases are: