The idea is that now Manifest holds the information on the Julia version itself but "ignores" this information if activating the environment from another Julia version.
While it is true that it does issue a warning in instantiating it, sometimes you don't need to instantiate.
For example, I did start a new environment in Julia 1.7, add DataFrames and then activated it from Julia 1.8 beta, I had no warning. Yes, the package I were using were the same, but Julia wasn't, and I think this breaks the promise of replicability of Manifest.toml.
An option could always be added to activate NOT to warn/error in such cases (eg strict = false)...
Making an issue here as suggested on the discourse thread.
The idea is that now Manifest holds the information on the Julia version itself but "ignores" this information if activating the environment from another Julia version. While it is true that it does issue a warning in instantiating it, sometimes you don't need to instantiate. For example, I did start a new environment in Julia 1.7, add DataFrames and then activated it from Julia 1.8 beta, I had no warning. Yes, the package I were using were the same, but Julia wasn't, and I think this breaks the promise of replicability of Manifest.toml.
An option could always be added to
activate
NOT to warn/error in such cases (egstrict = false
)...