Releases

[gpucce]

@JuliaRegistrator register()

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/52850

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.1.0 -m "<description of version>" 7bbcd9f48f9ebce0507e164aee4107482cb27cdf
git push origin v0.1.0

[gpucce]

@Wikunia @TheCedarPrince I should have registered the package. Note that right now test fails because I tagged Javis as 0.8.0 which will be the release that will work with this package. Hope this is how it is supposed to go.

[gpucce]

Oh and also thank you both guys for all the help @Wikunia and @TheCedarPrince!!!

[gpucce]

@Wikunia @TheCedarPrince
So the auto merge thing
wants us to to add the .jl at the end of the repo name but I believe I can't do it.

Also there are some issues with the fact that the compat for Javis is currently too high so the automatic merge in the registry can't happen. I can either remove the compat for now or you can push Javis to 0.8 and then I will retrigger the registration.

Let me know what you prefer!

[Wikunia]

Oh yeah we should have named it JavisNB.jl
Hmm interesting case with the version. I don't want to Release v0.8 of Javis when JavisNB isn't tagged as we would still need to wait for 3 days.
The test cases will fail though if we run JavisNB with the current version of Javis, right? Which probably also breaks auto merging. Also tagging JavisNB with compat Javis pre 0.8 we would have a version that someone might install and expect it to work with Javis pre 0.8 😂

[Wikunia]

I have renamed the repo. Do you mind changing the links @gpucce ? Mostly in docs maybe readme

[gpucce]

Oh yeah we should have named it JavisNB.jl Hmm interesting case with the version. I don't want to Release v0.8 of Javis when JavisNB isn't tagged as we would still need to wait for 3 days. The test cases will fail though if we run JavisNB with the current version of Javis, right? Which probably also breaks auto merging. Also tagging JavisNB with compat Javis pre 0.8 we would have a version that someone might install and expect it to work with Javis pre 0.8 😂

On the issue in the registry it says we can comment and explain and then it will be merged manually. If this is the way I will write the comment where I explain the situation

[Wikunia]

Yeah that would be good. Make sure to update the links first though and then trigger the register command again.

[gpucce]

Yeah that would be good. Make sure to update the links first though and then trigger the register command again.

I think they were all already set with JavisNB.jl already.

[Wikunia]

Looks like it yes.

[gpucce]

@JuliaRegistrator register()

[JuliaRegistrator]

Registration pull request updated: JuliaRegistries/General/52850

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.1.0 -m "<description of version>" 7bbcd9f48f9ebce0507e164aee4107482cb27cdf
git push origin v0.1.0

[Wikunia]

@JuliaRegistrator register()

[JuliaRegistrator]

Error while trying to register: Register Failed
@Wikunia, it looks like you are not a publicly listed member/owner in the parent organization (JuliaAnimators).
If you are a member/owner, you will need to change your membership to public. See GitHub Help

[Wikunia]

@JuliaRegistrator register()

[JuliaRegistrator]

Registration pull request updated: JuliaRegistries/General/52850

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.1.0 -m "<description of version>" 9aa6c6c90efac517c172e8207a225cc8fcc3265b
git push origin v0.1.0

[Wikunia]

@JuliaRegistrator register()

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/94774

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.1.1 -m "<description of version>" f7926ce136a057c922d0fa7aa8119d096ea722d2
git push origin v0.1.1