It seems there was a bug in the recent update that caused the version number to not update appropriately, I’ve revised the release to fix that
You should be running the most recent code now, just with the wrong version number. If you were to update again then you’d have the correct version number as well
As for your blueprint not working, it’s possible that the blueprint was made too restrictive for your setup; I’ve made an issue for what I think could’ve been happening there, though it’s possible that we’ll sidestep that issue when we retire blueprints later on