> How is it any different from bait-and-switch or rug pulls corporate is being shamed for?

Hard agree. If you want to turn a profit from your project, make it commercial from the beginning. I have no problems with commercial tools or products, but I do have a problem with starting something as open source, gaining adoption, then changing the license later on.

It's the same BS behavior from SaaS we love to call out, when companies make a generous free tier, get users locked in, then pull the rug.

Should the community help out and contribute back to FOSS projects they use? Absolutely, but at the same time, they are not obligated to either and if a dev has a problem with that, then don't release it as FOSS.

I've published a few small tools for sysadmins, and I never expected any kind of contribution back whether monetary or otherwise, and that's OK. I wrote them for myself, and will maintain them for myself as long as they are useful to me. Others are free to use them and I don't expect anything in return.