Closed vincentcp closed 5 years ago
Is there anything we should do here other than tagging the new release?
Let me test ApproxFun with master, but tag when you are ready.
Can you tag as v0.1.0
? It makes it easier to specify version ranges.
Nevermind, I can just do DomainSets = "^0.0.1"
and that defaults to non-compatibility with v0.0.2
.
I've updated ApproxFun now so it should be fine to tag a new release
Release v0.0.2
is published
Tagging doesn’t publish a new version. Please delete the tag and follow the instructions on Registrator.jl
Ok, is Registrator.jl
already installed on DomainSets.jl
?
Yes its installed on all JuliaApproximation repositories. It will tag automatically when the release is merged.
@JuliaRegistrator register()
Registration pull request created: JuliaRegistries/General/220
After the above pull request is merged, it is recommended that you create a tag on this repository for the registered package version:
git tag -a v0.0.2 -m "<description of version>" 78963664239a3fbc257c6b42c8c06307b370220d
git push origin v0.0.2
We need to retrigger:
@JuliaRegistrator register()
Registration pull request updated: JuliaRegistries/General/220
After the above pull request is merged, it is recommended that you create a tag on this repository for the registered package version:
git tag -a v0.0.2 -m "<description of version>" 0276ec7067e66e76f3d488d8896ddd214224c14c
git push origin v0.0.2
I would like to use the new naming conventions that are in master.