This worked great for a few years, but when I came to think about it this way is still a bit to over engineered.
You could, if desired, also just run this in a CI pipeline and have CI take care of automating version upgrades instead of making it a semi-automatic process via script. It's also super fast for newcomers in the team or to native development to just run the script (however they won't know the deeper details of what's happening). Why automate something you could just change in VS Code or Xcode in the relative files? Well, version upgrades might not happen that often and then you need to either take your chances or ask around with coworkers if they remember the files that need to be changed. The files changed were standards for iOS & node, but for Android we used an older way of putting the version in a variable inside of gradle.properties and then read that variable during the gradle assemble task. It was also reliant on which sed you have available on the system, GNU or BSD (see the check at the end of the script).
However, for people not familiar with Bash this script is some advanced dark magic. #!/usr/bin/env bash set -e function _replace_in_file () Įnter fullscreen mode Exit fullscreen mode
0 kommentar(er)
