Skip to content

JSON.md: Fixed outdated explanation of replace_version #253

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
olehermanse merged 1 commit into from
Jul 14, 2025
Merged

JSON.md: Fixed outdated explanation of replace_version #253

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions JSON.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 <to_replace> <filename>`
- `replace_version <n> <to_replace> <filename>`
- 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:
Expand Down