DOIs no longer created automatically by zenodo?

The latest releases for both MeshArrays (now 0.2.6) and IndividualDisplacements (now 0.1.6) do not seem to have gotten DOI'ed the way I would have expected. I noticed this because and kept pointing to earlier release archives

edit: the fix for this is explained in the first few posts below

I am rather confused by the fact that v0.2.5 of MeshArrays (NO DOI) and v0.1.5 of IndividualDisplacements (with DOI) were both released after transfer to the org & before the tagbot action PRs. Most recently, neither MeshArrays 0.2.6 nor IndividualDisplacements 0.1.6 seem to have gotten a DOI (or I just don't know where to find them).

In addition when I look under the GitHub list in zenodo under my account, I cannot find either of these packages. This made me wonder if somehow we have another account for the org at zenodo that I do not know how to access. Where is the list that allow me to switch zenodo on / off for MeshArrays & IndividualDisplacements?

In contrast, I noted that ClimateTools has been getting DOI'ed as I would expect for the other packages. @Balinus do you have an idea of what I might be missing or overlooked?

Maybe I need to do something else at the org, team, or repo level?

edit: the first few posts below provide explanations & links related to this. Thanks @Balinus

Start by reading the first few comments referenced in the issue, then inspect the GitHub and Zenodo release settings for MeshArrays and IndividualDisplacements. Compare them with ClimateTools and the tagbot action PRs mentioned in the report. Done means explaining why the DOI archives differ and identifying the required release configuration.