Apm: Creating new version failed: Git tag not found

[madiedgar]

Prerequisites

• [x] Put an X between the brackets on this line if you have done all of the following:
  
  
  
  • Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
  
  
  • Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
  
  
  • Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
  
  
  • Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
  
  
  • Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages
  
  

Description

Attempting to publish a new version of my package language-legesher-python which is an extension from language-python.

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

The git tag of the package, the v0.56.8 tag, is published on my github repository. I logged in again with apm login, but the issue remained. I tried running the command with explicit versioning but received the following:

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

I had changed my repository from public to private (and now back to public in hopes that it would fix the problem). However, the inability prevails. Before I go ahead and unpublish / publish the package, is there anything I’m missing?

Best Practice Question: Should I have deleted all the old tags from the previous repository instead of starting off where they left off?

Reproduces how often:

Now, this issue occurs 100% of the time. I've made quite a few meaningless versions trying to debug.

Versions

os: MacOS Catalina 10.15

Atom    : 1.40.1
Electron: 3.1.10
Chrome  : 66.0.3359.181
Node    : 10.2.0

apm  2.4.3
npm  6.2.0
node 10.2.1 x64
atom 1.40.1
python 2.7.16
git 2.20.1

Additional Information

I added my reply here on the discuss.atom.io forum , but haven't received a reply. This issue is similar to #670 & #770, but no solution was provided.

Many of the other issues I've found related to this error are caused by the deletion of the repo / change of ownership. Both of which I've experienced - I've previously deleted/renamed the repo and changed ownership from my personal account to organizational. However, I was able to publish new versions after these events.

Sorry if this is too much information, please let me know if there is a better place for this issue.

_Any help would be appreciated._ 😄THANK YOU!!

[rsese]

Many of the other issues I've found related to this error are caused by the deletion of the repo / change of ownership. Both of which I've experienced - I've previously deleted/renamed the repo and changed ownership from my personal account to organizational. However, I was able to publish new versions after these events.

Hmm it looks like the last time you were able to successfully publish a new version was 0.56.1, is that correct?

$ apm view language-legesher-python
language-legesher-python
├── 0.56.1
├── https://github.com/legesher/language-legesher-python
├── Python language support in Atom for the Legesher project
├── 574 downloads
└── 2 stars

Was that after the repository deletion?

[madiedgar]

Thanks for looking into this @rsese. Yes, the last successful version published to apm was v0.56.1.

• This was published after the repository transitioned from my personal account to an organizational account.
• The repository deletion was in the early stages of development, but thought it was something to mention as it was a key factor in most of the other related issues. I was able to successfully publish after this deletion.

Happy to add additional information!

[rsese]

Hmm, it looks like the current legesher/language-legesher-python was created on 2019-09-06 [1]. Then looking at v0.56.1, that looks like it was committed on July 31 [2].

So it seems like the latest successful version that was published was done before the current legesher/language-legesher-python repository was created? Just trying to confirm if you're running into the same problem that you've seen in previous issues (like https://github.com/atom/apm/issues/809 for example) but let me know if I have the timeline incorrect.

[madiedgar]

So it seems like the latest successful version that was published was done before the current legesher/language-legesher-python repository was created? Just trying to confirm if you're running into the same problem that you've seen in previous issues (like #809 for example) but let me know if I have the timeline incorrect.

🤯 This makes so much sense. I pushed v0.56.1 on July 31st, so when I created the current version of legesher/language-legesher-pythonin September it used the version number described in the package.json. Thus , I misunderstood the first "successful publish" of legesher/language-legesher-python to be the version published with the old repo.

Should I go through the process of unpublish / publishing the package noted in #809? If so, should I delete all of the release tags (or can I)? Thank you so much!

[rsese]

Thanks for confirming the timeline - if this is the same issue where the package in atom.io is pointing to the wrong repository (the previous repository before the newer legesher/language-legesher-pythonin) then unpublishing/publishing wouldn't help. The 2 options are described by Jason in https://github.com/atom/apm/issues/809#issuecomment-414657228:

• An atom.io admin can update the package registry so that the language-legesher-python package points at the new legesher/language-legesher-python repository
• You can publish the package with a new package name

So if we're correct about what the issue is, I can see if I can get some help for the first option (I'm not able to do that myself) assuming you don't want to use a different package name?

[madiedgar]

That would be amazing to try for the first option @rsese. Thank you for walking me through this thus far!

[rsese]

We can't make any promises about when someone might be able to take a look but I'll drop the timeline for whoever can take a look next:

1. 2019-04-11 08:52:09 madiedgar/language-python was created (repo id 180825785)
2. 2019-04-11 08:52:24 repo renamed to madiedgar/language-legesher-python
3. 2019-05-17 09:38:22 repo transferred to the legesher organiztaion
4. 2019-09-06 17:52:45 repo renamed to legesher/language-legesher-python-mirror
5. 2019-09-06 17:52:59 legesher/language-legesher-python was created (repo id 206895393)
6. 2019-09-18 06:02:54 repo legesher/language-legesher-python-mirror destroyed (repo id 180825785)

And you mentioned that for the last successful published version that "I pushed v0.56.1 on July 31st", so that would be before (4) and with the original repo with id 180825785.

[madiedgar]

That's fine, thank you again! 👏

[madiedgar]

Curious, any updates on this ?

[rsese]

Sorry no updates - if there any updates, whoever ends up looking into this will leave a comment but like I mentioned above, we unfortunately can't promise a specific timeframe.

[pelevesque]

I have a similar problem. I think I need a mod or an admin to clean up the apm database for me so I can try publishing again. I wrote messages in the forum, but am not getting any replies. I would love to be able to publish my syntax-highlighter for atom since it's for a language I created.

https://discuss.atom.io/t/creating-new-version-failed-git-tag-not-found/69534/3

[madiedgar]

Sorry to bother again, but is there another way I can try to get help on this? I value your time and I'm trying not spam all the support outlets, but if there's a better place to pose the issue I'd really appreciate the direction. I asked in the Atom slack channel via #packages but haven't gotten a response. 😬

[pelevesque]

I second madiedgar, I have the same problem at https://github.com/atom/apm/issues/873.

I'd love to get this resolved even if it means spending my own time working on the issue somehow.

[madiedgar]

@pelevesque not sure if you're issue is still unresolved, apparently there were some updates that were made regarding this issue (I was notified via slack)? I was able to publish my package again. 🤷‍♀ 🎉

Thank you @rsese for all your help! I'll close this issue as it is now resolved. 👏

[pelevesque]

@madiedgar Thanks for letting me know. I'll check it out.

[lkashef]

Hey @pelevesque I am looking into your case, actually the fix we applied for @madiedgar should solve it only for her, since we are doing this manually until we push a fix to apm.

I am investigating and we can collaborate on your case on the issue you have opened, I just wanted to make it clear, that the actual bug has not been fixed yet.

[pelevesque]

@lkashef Sorry for the really late reply.

I'm still having the issue and if someone could help it would be really appreciated.

My repo is here: https://github.com/orfeo-lang/atom-language-orfeo

I want to run: apm publish minor to publish v0.1.0 of this package.

It fails with Creating new version failed: Git tag not found

[Basit-qc]

Facing similar issue and looking for help: https://github.com/atom/apm/issues/920