Sometimes the hash across versions is identical when the transcript sequence does not change, e.g. Ensembl release 100-102 for mouse. Ensembl mouse release 101 is currently available in AHub as an EnsDb while release 102 is not. Should tximeta look across all the releases with identical hash for downloading the TxDb/EnsDb from AHub? Currently it looks for the first match (which is the latest release).
Sometimes the hash across versions is identical when the transcript sequence does not change, e.g. Ensembl release 100-102 for mouse. Ensembl mouse release 101 is currently available in AHub as an EnsDb while release 102 is not. Should tximeta look across all the releases with identical hash for downloading the TxDb/EnsDb from AHub? Currently it looks for the first match (which is the latest release).