I'm a Systems Reliability and DevOps engineer for Netdata Inc. When not working, I enjoy studying linguistics and history, playing video games, and cooking all kinds of international cuisine.
Forcing a version bump when the build process changes is actually a good thing. In fact, even if you have the build scripts separated from the code, you should still be mandating a version bump on the first build after changing the build scripts.
Quite simply, it's insanely easy for a seemingly innocuous change to the build process to generate completely different code or introduce subtle errors in the application (trivial examples include switching between GCC and clang, enabling or disabling LTO, or tweaking the optimization level of a build). Dealing with the fallout from such a situation is a whole lot easier when you can just look at the version and say 'Oh, that's version x.y.z, it has a bug, you need to either upgrade or downgrade to avoid it.'.
As for deployment scripts, I'm of the opinion that it doesn't matter much, provided that your app treats them like a black box (that is, it only cares about the end-state of the deployment, not the intermediary steps).
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Forcing a version bump when the build process changes is actually a good thing. In fact, even if you have the build scripts separated from the code, you should still be mandating a version bump on the first build after changing the build scripts.
Quite simply, it's insanely easy for a seemingly innocuous change to the build process to generate completely different code or introduce subtle errors in the application (trivial examples include switching between GCC and clang, enabling or disabling LTO, or tweaking the optimization level of a build). Dealing with the fallout from such a situation is a whole lot easier when you can just look at the version and say 'Oh, that's version x.y.z, it has a bug, you need to either upgrade or downgrade to avoid it.'.
As for deployment scripts, I'm of the opinion that it doesn't matter much, provided that your app treats them like a black box (that is, it only cares about the end-state of the deployment, not the intermediary steps).