Process seems stuck; not creating next version

### Solution to issue cannot be found in the documentation.

- [X] I checked the documentation.

### Issue

There's a PR here that's been sitting for a couple of years. I'm just looking into this repo, as the developer who used to support SAS_kernel left the company. I've created a new release of it and pushed that to PyPI, yet I don't see a build here being triggered by that. Don't know if the stuck PR is the reason for that or not. I support SASPy, and I can merge those PR's in when new versions are triggered; that's all working. But I don't have access to this feedstock, nor do I know what the problem is such that there aren't new PR's being triggered for new versions.

Thanks!
Tom

### Installed packages

```shell
don't know what you want here
```

### Environment info

```shell
don't know what you want here
```

The issue concerns the sas_kernel-feedstock repository and a release pushed to PyPI that did not trigger a new build PR. Start by reviewing the feedstock configuration and the automation responsible for detecting new PyPI versions. Done means identifying the cause and confirming that a subsequent version triggers the expected PR.

Written by the indexing model from the issue text.