-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
[BUG] Publish doesn't work for a renamed package #63
Comments
Thanks a ton for the bug report, I really appreciate the information, and will look into this issue. |
If you need a retry please ping me on discord ;) |
I will absolutely let you know |
@confused-Techie there could be the possibility to delete the tidalcycles packages and upload it again? Would that work? |
You could do that, although the name Now I'm just trying to clean up a few things to give us more faith in that new system. But I can try to sprint these changes this weekend and get them pushed to prod. But let me know what you'd like to do and I'll work with you |
Great to hear that, I'll wait to see if the issue will be fixed by the next rollout 🙌 |
@ndr-brt If possible would you be willing to give this another try? We now have success with users publishing new package versions. Keep in mind the new pinned issue on this repo. As in if it says you successfully published the new version, keep in mind the website and Pulsar might not show it, but using the API you'll be able to see the new version, or if you have the package installed you'll be prompted for the upgrade to your newer version. Otherwise using |
@confused-Techie it worked! no errors 🥳 thanks a lot. I will close the issue |
Is this Bug Present in the upstream API Server?
What is the Bug
The url of our plugin changed (from
atom-*
topulsar-*
) and the publication started to fail again.How to Replicate the Bug
After login, running
pulsar -p publish patch
caused:The text was updated successfully, but these errors were encountered: