Snap Pack versions are independent of Snaplex versions. As an Org admin, you can keep track of the version for your Snap Packs in Manager > Snap Catalog, as well as your Snaplex versions.
You should consider the following when tracking Snap Pack versions:
Design time
Execution time
Design Time
Design time consists of Pipeline development activity. Usually, the Pipeline designer manually executes the Pipeline from SnapLogic Designer to test it.
Pipeline designers should be aware of the following factors during pipeline design:
Since the Snaplex on which the pipeline run is unknown, an Org-level Snap Catalog is used. This Snap Catalog controls the Snaps that SnapLogic Designer displays and the properties that are displayed in those Snaps.
The design-time Snap Catalog uses old SnapPack versions if there is any Snaplex in the Org on an older Snaplex version (which is the version of the platform).
If all Snaplexes are on newer Snaplex version, the latest Snap Pack versions are used.
Execution Time
Execution time consists of Pipeline executions that are the result of invoked executions, in other words, Tasks. During Pipeline execution, the Snaps used depends on the Pipeline location and the Snaplex version.
If the project containing the Pipeline has private SnapPacks, then those Snap Pack versions are used. Otherwise, the Snap Pack corresponding to the snap distribution is used.
If the JCC node is on new Snaplex version, the new SnapPack versions are used.
If the JCC node is on a previous Snaplex version, then the previous versions of the SnapPacks are used.
Order of Snap Version Reference
Private SnapPack version in a project where the Pipeline is located.
Private SnapPack version in project space shared folder
Private SnapPack version in Org-level global shared folder
The Snap version configured in the distribution (stable/latest) used by the Org. The Org-level version overrides are applied here.
A private SnapPack version always takes higher precedence over the configured Org-level SnapPack.