It really isn't amazing seeing something like this in the BETA version, stable version yes beta no. It will get fixed by the time is rolls out to stable.
It's still discouraging, this isn't some small little tweak. It's a significant change to a core gameplay component. There's basically three scenarios:
1. Developer changed the code/parameters and left it to QA to verify entirely. QA saw parts unlocked while smithing, called it a day, didn't even re-load save once. Granted yes in a game like this, there's possibly a million way to test things. But verifying save integrity should be like one of the foremost. Reloading frequently should be common in testing too, unless they are trying to marathon something.
2. Maybe was found by QA, but won't be patched til later.
3. Developer went changed something at the last minute, and didn't understand full impact or simply forgot some code somewhere.
But as I understand it, there is an internal alpha stage for patches (biggest reason for large time gaps between patches), so really something like this should be caught. So either QA is lacking or for some reason it's a slightly complicated/lengthy fix. Or a developer did some hasty last minute thing.
IDK after two years it seems to me there are some real problems with the development process. My biggest suspicion is there aren't enough QA testers, that would be fairly plausible since TW isn't exactly a major studio/publisher. Although that makes the whole Early Access all the more scummy, since we're basically being used as QA (and we paid to do it LOL). That or there's a serious "wall" between Devs and QA which prevents actual communication.
The bugs I expect to encounter are stupid little ones (like you buy a particular helmet from a particular Town; and it crashes the game). Things that even the best, largest, QA teams couldn't realistically weed out. Ideally that's what Betas are for.