> a problem with our CI/CD pipeline because an old package that's a sub dependency wouldn't install anymore
> The whole build system is pinned by on git commit. If it builds today, it will build tomorrow. No matter what.
If that commit is still available. This still doesn't answer the question of how I easily pin a version. The package versions in the post point to what amounts to a random package version.
And that's on top the fact that "if you tried to follow this article step by step, you’ll have noticed that the versions of ruby and node you installed are probably slightly different from the ones above"
> The whole build system is pinned by on git commit. If it builds today, it will build tomorrow. No matter what.
If that commit is still available. This still doesn't answer the question of how I easily pin a version. The package versions in the post point to what amounts to a random package version.
And that's on top the fact that "if you tried to follow this article step by step, you’ll have noticed that the versions of ruby and node you installed are probably slightly different from the ones above"
> Nix stores each package in its own path.
This is a part that I like.