Thanks for reporting. This was related to a change deployed yesterday that included package updates related to a reported security vulnerability. That package update changed its default behavior in some unexpected ways (some context here if you’re interested). Hopefully these links are working again