Apm publish fails after renaming a repo

[TheoWinterhalter]

It seems publishing is not possible after renaming a repository (and updating the package.json in consequence).

I get the following (I just renamed my repo on github to match my package name):

apm publish patch
Preparing and tagging a new version ✓
Pushing v1.6.2 tag ✓
Publishing [email protected] ✗
Creating new version failed: Git tag not found

Of course the tag still exists.

http://discuss.atom.io/t/cant-publish-package/4890 for more information

[thedaniel]

This is a known issue with the API that we hope to remedy soon. In the meantime, I've manually updated the repo info in the database - try again and let me know how it goes.

[TheoWinterhalter]

It indeed worked. Thanks a lot.

[kevinsawicki]

Fixed by #161

[bmathews]

I'm having an issue republishing my theme after renaming my github username from moonsspoon to bmathews. Users are getting a Unable to download https://www.atom.io/api/packages/atom-dark-ui-slim/versions/0.4.0/tarball: 400 Bad Request Repository inaccessible when trying to install.

https://www.atom.io/api/packages/atom-dark-ui-slim/

Trying to publish gives me this git tag not found error, even though the tag exists.

$ apm publish --tag v0.4.3
Publishing [email protected] ✗
Creating new version failed: Git tag not found

[kevinsawicki]

@bmathews would you mind opening a new issue for this? https://github.com/atom/apm/issues/new

Thanks