Repository navigation
updated project toml with julia compatibility for all major versions - #50
Conversation
|
Merge guidelines were met in the new register request for JuliaHub JuliaRegistries/General#148907 |
|
So the PR is successfully merged in with JuliaHub. @goedman how long does the release take to show up in the releases. I've seen previous releases done via github actions is this something that we need to trigger somehow or would the JuliaHub pr we just did cover that? Is it something I should make the tagbot script trigger? Sorry again I'm just trying to get this down so I can apply this process to the other packages we need to. |
|
In most cases a few minutes, a few times it took a bit longer. But it is pretty quick. Of course I'm talking about roughly 2 years ago. |
|
Okay understood, so we got through on the JuliaHub side of things and the release is tagged and available there. Though on our Github page the release is not getting triggered. @goedman am I forgetting to do something to trigger the github-actions release process? I'm just trying to make sure we get the process down correctly for each package. I was manually doing the releases before which I realize was a mistake. |
|
It might be related to this #51 |
|
So I'll do a manual release for now. Though we'll do a fast-follow release to fix the issue with the tagbot not being able to automatically do the release. |
making a patch to correct an error introduced when trying to update project toml.