ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Use per-project Pkg environments (Project.toml + Manifest.toml) as the reproducibility boundary for Julia applications: activate, add direct deps, commit both files, and reproduce with Pkg.instantiate().
Julia's Pkg.instantiate() recreates environments from Manifest.toml , which records exact package UUIDs, versions, and git SHAs. However, the manifest omits the Julia patch version used during resolution. Project.toml optionally accepts a julia compat entry, but no field in Manifest.toml locks the resolver to a specific Julia release. This means the same Man
Context An application pins exact dependency versions by committing Manifest.toml alongside Project.toml . Both development (Apple Silicon) and production (x86_64 Linux) use Julia 1.10 and run Pkg.instantiate(--project=.) in clean containers. The Manifest.toml file is byte-for-byte identical in both environments. Problem Despite identical manifests and Julia
Project and Manifest synchronization Julia utilizes Project.toml for direct dependencies and Manifest.toml to lock the entire dependency tree, ensuring that Pkg.instantiate() can recreate a specific environment state. A challenge arises when distributing these files across different operating systems. While the package versions are tracked via UUIDs, certain
Goal After a failed Julia package upgrade, the user wants to restore a functional environment that previously compiled successfully. Constraints During the upgrade, the Manifest.toml was modified to include an impossible or incompatible version entry for a package, causing subsequent using statements to error. The user has a backup of the original Manifest b
julia