craigbloodworth
commented
4 years ago @HSJD19 while I can sympathise with this need the extensions is provided free of charge in terms of source code, hosting and support. If we were to then also add version locking to the mix we'd effectively be multiplying these free resources for every version released. In reality if we locked in at say v2.2 and made that a supported release then we'd have to handle bug fixes for that specific release across all supported versions of Tableau Desktop & Online while also supporting requests for new features in other versions. It's simply not sustainable without a fully supported, paid service, something The Information Lab today isn't setup to create.
The best way to lock in a specific version is to deploy it yourself to either an internal or external web host. I plan to publish more clear instructions on how to do this in the near future
HSJD19
ericknizard
Based on my regulatory requirements , it would be really nice to be able to have a stable version and only upgrade when I chose. For example, if I test and validate my dashboards with v2.2 , I would like for no changes to be made to that version and that changes or updates made to new versions would not effect the version. At present it seems that anytime new code is pushed , all extensions get updated no matter what version was originally downloaded.