For this specific use case? sed would work just as well and probably already exi...

rout39574 · 2024-08-19T15:57:37 1724083057

Having done similar things to this in the past, I rebut: no it wouldn't. :)

It's not trivial to change a particular

version: 2.33

line in a JSON file, when it's possible that string is present in many places with different meanings.

You can just wing it and be right 90% of the time; but that thoughtlessness will bite you in time.

Multiply that by the number of different context you might want to make "the same" change in a project, and sed/awk get to be a poor fit. YAML and JSON are just plain not line oriented.

You really need something with a featureset like xpath to set the semantically correct node to the right value, and every few years the kids decide they need YET ANOTHER thing that's not XML, or Yaml, or JSON, or TOML, or..

kate_bits · 2024-08-21T08:15:16 1724228116

Maybe I am too prescriptive of your setup, but I don't really see "version: 2.33" making sense. Why not something akin to "version: __BUILD_NUMBER__" being actually checked into your tree, and then your build pipeline filling it in at build time?

Keeping a copy of the build number checked into your source tree seems like asking for trouble when the build number is so intrinsically tied to a single build pipeline run.