Yep, we (as soon as we’re able) intend to implement version pinning similar to a yarn.lock or package-lock.json file, whereby imports and requires (and indirect imports and requires) are automatically pinned at the current version the first time they are evaluated, with some explicit option to upgrade dependencies when desired.
In the meantime, if you want a quick way to access the current version of your notebook, you can choose “View history” in the notebook menu, and the current version will be shown in the address bar.
We have some improvements related to downloading code that will hopefully be launching later today. I’ll post an update when that goes live.