Closed lbenet closed 4 years ago
You can just do @JuliaRegistrator register
on the last commit
Registration pull request created: JuliaRegistries/General/6203
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if Julia TagBot is installed, or can be done manually through the github interface, or via:
git tag -a v0.4.1 -m "<description of version>" 75064ad095c8b0bb912a1eded211bbea256de36a
git push origin v0.4.1
OK apparently I did it here.
Ok... always forget it...
I was about asking where have you done it :-)
Incidentally, this was needed to make some updates in TaylorModels.
I didn't know about about these requirements to have an automatic merge... We'll have to wait ~24 hrs.
Just change it to julia = "1"
I think.
That may solve part of the issue, but not
- A patch release is not allowed to narrow the supported range of Julia versions
Wasn't the supported range already 1.0 and above?
No. I had to create the Project.toml
itself. Perhaps the problem is the ≥
in that line, which I overlooked, and which is perhaps better to have as ^1.0.0
.
By the way, we will eventually need to update a bunch of things to julia ^1.1.0
, since that's a requirement in IntervalArithmetics.jl
(whose Project.toml needs also to be updated).
I noticed you changed that line of julia
, and seems to have solved part of the issue. Should we tag v0.5.0 instead, to satisfy the requirements for automatic merging?
Yes let's do that. And may as well change it to Julia 1.1 while doing so.
Can you do it?
Incidentally, maybe it is a good time to have Polynomials = "^0.5.0"
, instead of having v0.5.0 fixed...
This should be done by TagBot