It’s a different model and the inputs now have a different relationship that is handled different in a way that triggers that numpy warning.
It’s still nothing to be worried about. We have a GitHub issue that you can track to see when it gets solved: Numpy deprecation warning when converting python integers · Issue #146 · pymc-devs/pytensor · GitHub