Howdy! I wish I would have caught this sooner, as I have recently experienced a similar issue!
It's worth noting that the client / pins user can solve this problem by setting version = FALSE when they register their rsconnect board. Please note that this is a board-wide setting, so you need to deregister / re-register if/when you want to change the setting. We are doing some work to make this easier to find / more clear / pin-specific, and will hopefully have that as an improvement in the future!
In the meantime, it is worth noting that version = FALSE will make pins:
-
pin the new version
- if successful, delete all old versions
- as a result, only one version of the pin is persisted on Connect long-term