Yeah, I stopped working on "infrastructure" utility libraries and similar projects because the maintenance burden is too high. Some people just don't get it - I'm not in it to provide a free service to anyone.
Luckily I live in a country where the law doesn't allow an employer to forbid releasing projects done on free time, so I don't have your issue. I would seriously reconsider my employment if I were given such restrictions. As little as I finish stuff, the ability to share and receive feedback from strangers in the internet is still positive to me.
Out of curiosity, how did they pressured on you and which community was it in (linux/frontend/java/python/etc)? Many project I seen (and used) seem to be abandoned after a while or are maintained slowly, so you not being able to maintain long term seems pretty much standard to me.
I currently work full time for a company whose policy forbids releasing anything I work on in my free time, so it's kind of nice--the decision is pretty much made for me.
I guess the advice is learn to _finish_ things but don't get too hung up on releasing them. Unless you're trying to build a business in which case you need to follow a totally different path (release MVP early, get feedback, iterate, market fit, etc.).