Add compat entries for all deps (even stdlibs)

[lgoettgens]

Adapt for upcoming changes in julia nightly, see:

https://discourse.julialang.org/t/psa-compat-requirements-in-the-general-registry-are-changing/104958

[codecov]

Codecov Report

Merging #1554 (29c37ce) into master (110d3be) will decrease coverage by 0.07%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1554      +/-   ##
==========================================
- Coverage   84.20%   84.14%   -0.07%     
==========================================
  Files          94       94              
  Lines       36602    36602              
==========================================
- Hits        30820    30798      -22     
- Misses       5782     5804      +22     

see 14 files with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[lgoettgens]

I know that this looks weird, but it is the only option as long as we support julia 1.6 and 1.7. See JuliaCrypto/SHA.jl#87

[fingolfin]

Any reason to remove this? I keep adding it back when I build the documentation locally, which is why I finally committed it. Note that the CI job building the docs also adds it (we just don't commit there, obviously).

[fingolfin]

Oh wait, I misread this. What I mean is that I keep adding Nemo to docs/Project.toml... But I agree that AA should be removed here (with the other changes you made below this is possible)

[lgoettgens]

Somewhere in the julia docs I read that the package itself shouldn't be j it's docs/test project deps.
But yeah, this is something different

[lgoettgens]

Oh wait, I misread this. What I mean is that I keep adding Nemo to docs/Project.toml... But I agree that AA should be removed here (with the other changes you made below this is possible)

CI seems to fail due to this. Any idea what's going wrong? I hoped that the change in the setdocmeta would be enough

[fingolfin]

Yeah I slowly start to remember, I've run into this before (probably more than once). As the error in the CI logs indicate, using AbstractAlgebra won't just silently proceed when there is already a module AbstractAlgebra present. Perhaps it works if you do using Nemo.AbstractAlgebra? But probably also not.... So either you need to hack the system to convince it that AA is already loaded. Or we change AA: Maybe we can change it to do using ..AbstractAlgebra in the individual jldoctest blocks, i.e.:

```jldoctest; setup = :(using ..AbstractAlgebra)

Empirical evidence why this might work: in a fresh Julia session:

julia> using AbstractAlgebra

julia> using ..AbstractAlgebra

In another fresh Julia session (with a different environment that only has Nemo but not AA):

julia> using Nemo

Welcome to Nemo version 0.37.1

Nemo comes with absolutely no warranty whatsoever


julia> using AbstractAlgebra
 │ Package AbstractAlgebra not found, but a package named AbstractAlgebra is available from a registry.
 │ Install package?
 │   (1.9) pkg> add AbstractAlgebra
 └ (y/n/o) [y]: n
ERROR: ArgumentError: Package AbstractAlgebra not found in current path.
- Run `import Pkg; Pkg.add("AbstractAlgebra")` to install the AbstractAlgebra package.
Stacktrace:
 [1] macro expansion
   @ ./loading.jl:1630 [inlined]
 [2] macro expansion
   @ ./lock.jl:267 [inlined]
 [3] require(into::Module, mod::Symbol)
   @ Base ./loading.jl:1611

julia> AbstractAlgebra
ERROR: UndefVarError: `AbstractAlgebra` not defined

julia> using Nemo.AbstractAlgebra

julia> AbstractAlgebra
AbstractAlgebra

julia> using AbstractAlgebra
 │ Package AbstractAlgebra not found, but a package named AbstractAlgebra is available from a registry.
 │ Install package?
 │   (1.9) pkg> add AbstractAlgebra
 └ (y/n/o) [y]: n
ERROR: ArgumentError: Package AbstractAlgebra not found in current path, maybe you meant `import/using .AbstractAlgebra`.
- Otherwise, run `import Pkg; Pkg.add("AbstractAlgebra")` to install the AbstractAlgebra package.
Stacktrace:
 [1] macro expansion
   @ ./loading.jl:1630 [inlined]
 [2] macro expansion
   @ ./lock.jl:267 [inlined]
 [3] require(into::Module, mod::Symbol)
   @ Base ./loading.jl:1611

julia> using ..AbstractAlgebra

Of course that would require making an AA PR now and then releasing it

[fingolfin]

Somewhere in the julia docs I read that the package itself shouldn't be j it's docs/test project deps. But yeah, this is something different

It would be interesting to know where you read this, and how whoever wrote it then builds their docs? Looking at [the Documenter.jl documentation](julia --project make.jl) they suggest to build package docs via

cd docs
julia --color=yes --project make.jl

Which of course only works if you just before did something like this:

julia --color=yes --project -e 'using Pkg ; Pkg.develop(path="..")'

which is precisely what I do (and essentially also what our CI does), except that then I have a diff in my Project.toml...

[lgoettgens]

I really do not like that we need to change AA for this. Thus I would just re-add it to docs/Project.toml and deal with it sometime later.

[fingolfin]

Not an objection, just a genuine question: I am wondering where we need this? Is it because of the doctests in AA which have setup = :(using AbstractAlgebra)? If so, is that the only reason? Perhaps we could add this as a comment before the setdocmeta!, for the next time I or someone else wonders about this ;-).

But if you don't know either, don't waste your time on this.

[lgoettgens]

Yeah, that was my hope, but it doesn't work in the docs ci job.

[lgoettgens]

I'll try something else later today