the last two times a release of wcl was cut, the code wasn't functional. the code was updated at npmjs.com, but updating the wcl version in the apps where it's being used didn't actually reflect the update. the first time this happened cutting a new release, of the same code, allowed the new code to be used.
instead of doing that again, I'm hoping that updating release-it will fix this issue going forward.
the last two times a release of wcl was cut, the code wasn't functional. the code was updated at npmjs.com, but updating the wcl version in the apps where it's being used didn't actually reflect the update. the first time this happened cutting a new release, of the same code, allowed the new code to be used.
instead of doing that again, I'm hoping that updating
release-itwill fix this issue going forward.related: