-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v0.3.0 release failed on registry #29
Comments
It looks like I accidentally added some unneeded dependencies when I was working on support for color scales. I removed them in the latest commit - should work now, I think? |
Bumping the version between commits can prevent auto-merging. I would recommend changing the version back to 0.3.0 and then tagging the registrator bot. Happy to fix this today if you'd like me to try. |
We can then delete the newer releases on GitHub. The releases aren't mandatory anyway but good practice. We can update the 0.3.0 release to match up with the latest commit. |
I think I have it fixed now? Version is back to 0.3.0 and the PR merged |
Yup, it looks like everything worked. Once we fix the TagBot, it'll handle the GitHub releases so you won't need to do any of that manually. |
I'm not 100% sure from the reading the logs why this failed.
From my quick scan of https://github.com/JuliaRegistries/General/actions/runs/6290588038/job/17078147947?pr=92098, I see:
Feel free to keep working on the package. We shouldn't bump the version any further until this is fixed. Once we fix, we will need to update the 0.3.0 release.
And I'll plan to fix the TagBot so that it will automatically take care of the releases.
The text was updated successfully, but these errors were encountered: