@nprofile1q...

This is fixed now - for both the above feed and for future new releases updating publisher feeds.

Thanks for reporting the issue!