Kristoffer Carlsson

> One missing reasoning step in the current version is that, adding features [^1] is not considered breaking and can be done without incrementing the major version according to semver....

> Any particular reason for not backporting this? It is still kind of controversial so it feels a bit too "strong" to put backport labels on it and have it...

Base is in a unique position in that it only makes releases very rarely and has the luxury of PkgEval to detect upcoming issues. Also, people often run CI on...

Hm, didn't mean to cause that. There were a few commits on the backport branch that were erroneous.

> Adds a default compact stack trace display that selects the top-most frame that isn't in base Julia (frame.file starts with something other than ./, or starts with ./REPL) That...

> Though in the case of something like BenchmarkTools, sometimes the evaluated code is shown as originating from inside BenchmarkTools. (e.g. @btime a[3]) Yes, with e.g. callbacks it is often...

``` ┌ Debug: Rejecting cache file /home/kc/.julia/compiled/v1.12/Pkg/tUTdb_sLFSB.ji because required dependency Base.PkgId(Base.UUID("2a0f44e3-6c83-55bd-87e4-b1978d98bd5f"), "Base64") failed to load from cache file for /home/kc/.julia/juliaup/julia-nightly/share/julia/compiled/v1.12/Base64/D7K0n_Ip9tx.ji. │ exception = Error reading package image file. ``` weird..

I am also surprised this doesn't print anything at all for Base64: ``` julia> ENV["JULIA_DEBUG"] = "loading" "loading" julia> using Base64 julia> using Example ┌ Debug: Loading object cache file...

I had some thought that the nightly build juliaup uses was corrupt somehow but building a local Julia on master it gives the exact same behavior.

This method of loading Pkg seems to work: ``` ❯ julia +nightly --project -iqe 'using REPL; using Pkg' julia> pkgdir(Pkg) "/home/kc/JuliaPkgs/Pkg.jl" ```