Consider tagging a new release

[SebastianM-C]

Would it be possible to tag a new release?

[andyferris]

OK I think this magic incantation will work. This will be 0.6. We'll need to some more work before 1.0 (see #56).

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/15016

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 the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.6.0 -m "<description of version>" 37b74a9aa0a509308f99c287199550cf11879b82
git push origin v0.6.0

[andyferris]

@c42f Is the best way to deal with this by manually editing the Project.toml file? Do you have experience with CompatHelper?

The following dependencies do not have a compat entry that has an upper bound: Rotations. You may find CompatHelper helpful for keeping your compat entries up-to-date.Note: If your package works for the current version x.y.z of a dependency foo, then a compat entry foo = x.y.z implies a compatibility upper bound for packages following semver. You can additionally include earlier versions your package is compatible with. See https://julialang.github.io/Pkg.jl/v1/compatibility/ for details.

[SebastianM-C]

Shouldn't #61 have removed Rotations?
I see that the compat entry was removed, but not the deps one
I made a PR (#63) removing it.

Also. if you'd like, I can make a PR adding CompatHelper.

[c42f]

Thanks, I merged that. I don't know about CompatHelper; haven't felt the need for it yet, but let's try it out.

[c42f]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request updated: JuliaRegistries/General/15016

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 the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.6.0 -m "<description of version>" a5288777235661fb3956b48585b0c6b7e87651b2
git push origin v0.6.0

[SebastianM-C]

The advantage of having CompatHelper would be that it would automatically open new PRs when new versions of deps appear. But in this case there is only one dependency to consider, StaticArrays, so it might be overkill.