Some apps in prod will have a lag in the version of the taxonomy_re_api commit that they use, e.g., they will point to the "release" version of taxonomy_re_api, but there will be a delay in getting the most recent commit of taxonomy_re_api released. If these apps are using an old commit of taxonomy_re_api, that old commit of taxonomy_re_api might expect the deprecated taxonomy_search_species stored query to be available in the respective RE. But the latest RE, with the deprecated taxonomy_search_species stored query deleted, might get deployed into prod.
If we undelete the deprecated taxonomy_search_species stored query in the RE then we don't have to worry about deploying the latest RE to prod.
Some apps in prod will have a lag in the version of the
taxonomy_re_api
commit that they use, e.g., they will point to the"release"
version oftaxonomy_re_api
, but there will be a delay in getting the most recent commit oftaxonomy_re_api
released. If these apps are using an old commit oftaxonomy_re_api
, that old commit oftaxonomy_re_api
might expect the deprecatedtaxonomy_search_species
stored query to be available in the respective RE. But the latest RE, with the deprecatedtaxonomy_search_species
stored query deleted, might get deployed into prod.If we undelete the deprecated
taxonomy_search_species
stored query in the RE then we don't have to worry about deploying the latest RE to prod.