I have seen a few issues come up that are sometimes resolved by 'pull the latest'. I am wondering whether or not it would be advisable to adjust the quickstart compose files to pin the version of the image to ensure it doesn't drift?
Sure. You can do that, if you like by updating the .env file value: ZITI_VERSION=latest to the version you want.
Using the latest tag might be part of the problem. For instance, <0.30.0 uses one variable and >0.30.1 uses a different. If the quickstart were pinned to a version with each revision and test then there would be no confusion. Also, you could diff the branches to see what changed. Rather than leaving it to the end-user to figure it out, make it part of the repo.
To be more specific, this line below should be pinned and updated along with image releases when they are ready to go.
For instance, how does NetFoundry do it to ensure their binaries are stable? If they pin to specific versions, can you adopt that for the open source version to indicate a stable version? Or do they compile their own with changes?