When a collaborator publishes a new version to a package, the package disappears
Description
I saw this the other day and didn't have a chance to debug it. I was using my personal API token and tried to publish a private packaged owned by Ortus that I was a collaborator for. The publish said it was successful, but then the package disappeared from forgebox.io Re-publishing with the ortus API token brought it back with all the versions still in tact. I think maybe it updated the slug to have the wrong username. Need to test collaborators publishing on both public and private packages.
Activity
Show:
Luis MajanoMarch 22, 2019 at 3:47 PM
Can you please give me more info or debugging, I can’t reproduce this.
Fixed
Pinned fields
Click on the next to a field label to start pinning.
I saw this the other day and didn't have a chance to debug it. I was using my personal API token and tried to publish a private packaged owned by Ortus that I was a collaborator for. The publish said it was successful, but then the package disappeared from forgebox.io Re-publishing with the ortus API token brought it back with all the versions still in tact. I think maybe it updated the slug to have the wrong username. Need to test collaborators publishing on both public and private packages.