Can't create release: git repository tag appears in repo browser, but not vcs tables

7.x-1.x version not appearing is due to #2132881: New project snapshot releases not displayed on the Project page.

The 7.x-1.1 tag shows up in the repository browser, but not in the versioncontrol_labels table for your repository, which indicates a potential git problem when the tag was created. Re-framing this issue to focus on that issue.

I am having the exact same problem, and it's preventing me from making a module release.

STR: pushed up all the commits I wanted on my dev branch, did some testing, and later made a non-annotated tag and pushed just the tag to d.o like:

git push origin $TAGNAME

With the D6 version this always worked fine.

Testing a couple possible work-arounds, these have no affect:

- pushing a new commit
- edit/save the project node

I am changing this status to a bug because it represents a breaking change of a core workflow.

As with above I am unable to release my distribution as my project page does not detect my git tag from my repository.

closed as dup #2135503: New git tag does not appear when trying to make a release

note, my problem is with https://drupal.org/project/apachesolr

Also tried deleting a tag - no effect

adding an annotated tag also no effect

Yeah I have to be honest I know the upgrade just happened and a lot of changes went in and I appreciate all of the hours of work put in. However this issue has been filed since Nov 9th and essentially noone is able to do a release.

I get a bit concerned when a core workflow is not working and has not been working for about 6-7 days. Is there anything I can do to push this issue along?

Was also posted here #2133809: Can not create releases on a new project.

I'm having this same problem. Cannot see the 7.x-2.01 tag for oa_discussion nor can I see the 7.x-1.0-beta3 tag for message_digest module.

Any status on this? Cannot release any module updates at this point, including security updates, so this is pretty critical.

(for what it's worth, this was actually working a week ago, so it's either a new problem or a side effect of some other recent "fix")

I'm experiencing the same problem at Relation Formatter Entity

1. Created a tag (7.x-1.3)
2. d.o didn't detect it when trying to add a new release
3. Deleted the tag
4. Recreated the dag
5. Waited more than 12 hours
6. d.o still didn't detect it when trying to add a new release

When going to the repository viewer, the tag does show up...

Just to verify. If someone can confirm?

I created some patches for the Basic Cart module against the git version which has a 7.x-2.x-dev branch. In the issue settings under 'Version' I do not have this branch available in the select drop-down. I had to choose some other branch and mentioned I had to tag with the wrong version. See #2127887: Integration with the Domain Access module and #2133501: Fatal error on uninstall.

My question.

1. Is this caused by the issue described here?
2. Is this caused by another issue I could not find?
3. Should I open a new issue?

Thanks.

EDIT: Answer = 1. See #19.

Compiling a list of affected projects.

title update

Added https://drupal.org/project/basic_cart as affected project.

As I checked the other affected projects, they all seem to have the mentioned tags missing in the issue settings 'Version' drop-down select.

It results in issues being tagged with the wrong version. I will adjust mine after this issue has been fixed.

That probably answers my question in #12: This is caused by the issue described here.

Added https://drupal.org/project/automodal to the list of affected projects.

Is there any movement on this issue? Curious if more information needs to be provided?

This is working for me now this morning. I pushed new tags for message_digest and oa_discussion. Waited about 10 min for the tags to show up in the repository viewer. Then I was able to add a release for those tags.

Note that the tags I created yesterday (which show up in the repository viewer) still aren't available for a release. Can't really say if the issue is fixed or if I just got lucky with my specific projects, but if you have this problem, try a new tag and see if it works.

Added https://drupal.org/project/lightroom to the list of affected projects.

I think this issue might have been resolved. After reading #22 I tried deleting and recreating (scroll down to "Deleting a tag/branch") the 7.x-1.3 tag for Relation Formatter Entity and I was able to create the new release instantly. It showed up as the latest stable release on the project page a few minutes later. I can advise everyone to do the same and see if it works for them as well.

So in short, here's what I did:

git tag -d 7.x-1.3
git push --delete origin 7.x-1.3
git tag 7.x-1.3
git push origin 7.x-1.3

I just did #25 and that is working for https://drupal.org/project/sticky_edit_actions. I did try just seeing if it would show up under 'add new release' and it did not but the tag deletion and a new tag, then push worked right away.

So sticky edit actions may be crossed from the list in the summary as wel then?

Added https://drupal.org/project/eu-cookie-compliance to the list of affected projects.

Just tried #25. It worked. I can make a release now

The solution described in #11 worked for the Anki module. It was a little more delicate removing the 7.x-1.x branch and re-creating it for the Automodal module - but it appears to have worked as well! Thanks everyone for your hard work on this!

Also works for the WetKit distribution. Thanks all!

Thanks everyone for commenting. Moved instructions from #25 to the issue summary.

After following the instructions in #25, releases can be created for async_js as well.

I tried #25 solution at cloud module for 7.x-1.x as follows:

git tag -d 7.x-1.x
git push --delete origin 7.x-1.x

< When "git push --delete origin 7.x-1.x" above, it gives the following error >

error: dst refspec 7.x-1.x matches more than one.
error: failed to push some refs to 'yas@git.drupal.org:project/cloud.git'

"git tag" command shows:

6.x-1.0
6.x-1.01
6.x-1.1
6.x-1.2
6.x-1.2-rc1
6.x-1.3
7.x-1.x

Any thoughts?

#37: You have both a branch and a tag named 7.x-1.x. The tag is named incorrectly, and should be deleted.

git tag -d 7.x-1.x
git push origin :refs/tags/7.x-1.x

@jthorson

I am sorry for my late response; finally I got an updated tar.gz! (after d.o upgraded) I really appreciate you for your reply.

There seem to be no new reports about this issue. Tagging so we won't forget about it. Lowering priority and postponing to wait a bit if there will be any new reports. Not closing at this time since #2125405: Not all commits showing up still exists, and the two look connected.

This is preventing me from being able to cut a 7.x-1.0 of the Panopoly distribution. The 7.x-1.0 tag shows up in the repository browser, but attempting to create a new release node for it shows "No valid branches or tags found.". I tried the workaround in comment #25 several times but to no avail. I was able to create a 7.x-1.x0 tag and new new release node for all 10 panopoly_* features without issue. It's only he distribution that has the problem.

Added OG 2.5 to list of affected modules.

Added Demo Framework to the list.

Added Scheduler to the list.

Our tool to clean these up as broken by #2159599: Replace ctools_static() calls with drupal_static(). It now gets further, and runs into the next problem. And upgrade to the versioncontrol_git module will help a lot, but I want to land #2169079: Fix escaping in VersioncontrolGitRepositoryHistorySynchronizerDefault first.

Quick update: this issue is still blocked on #2169079: Fix escaping in VersioncontrolGitRepositoryHistorySynchronizerDefault. We still have 2 critical issues to deal with before we can move onto Majors. Maybe marvil07 will be able to look into it this week.

Thanks to marvil07 and drumm #2169079: Fix escaping in VersioncontrolGitRepositoryHistorySynchronizerDefault has now been fixed. What's next?

Looks like that commit didn't actually get pushed. After that, it is a small deployment, no cache clears or anything needed.

Since re-syncing a repo deletes Drupal-managed records in MySQL, not the Git repo, and rebuilds from scratch, I will want to test this out one last time on git7staging, and start out with smaller repositories.

Crossing off projects fixed in #2125405: Not all commits showing up.

basic_cart already has a 7.x-2.x-dev release that looks okay.

@drumm and everyone else involved in fixing this: You are THE BEST! Thanks so much. :-) Time to start rolling releases!

Fixed og, addemar_subscription, hubdrop_test, mobile_navigation, webform_import, commercebox, null_mailer, role_activity, site_banner, and active_sessions. There are no more locked non-sandbox repos.

Thanks!!

Great work Neil. Yes Scheduler now has all its commits and a new release. Thank you.

Re-openning as I experience the same thing with project idea and tag 7.x-2.x-rc1
I removed and recreated the tag as explained above, but the tag does not appear in the Add new release form.
Is this the right issue to get help with that?

me@MacBook-Pro:/var/www/drupal.org/idea/idea-7.2$ git push origin tag 7.x-2.x-rc1
Total 0 (delta 0), reused 0 (delta 0)
To zstolar@git.drupal.org:project/idea.git
 * [new tag]         7.x-2.x-rc1 -> 7.x-2.x-rc1

You can't combine .x with rc1. I think you want 7.x-2.0-rc1.