Problem/Motivation
The 8.x-2.x branch has no releases. This makes a harder to contribute patches, since there is no version available for the latest 8.x-2.x branch when uploading a patch file.
Proposed resolution
Add a 8.x-2.x dev release
The 8.x-2.x branch has no releases. This makes a harder to contribute patches, since there is no version available for the latest 8.x-2.x branch when uploading a patch file.
Add a 8.x-2.x dev release
Comments
Comment #2
sjerdoPublished https://www.drupal.org/project/cookie_content_blocker/releases/2.6.x-dev
Comment #4
idebr commentedComment #5
idebr commented2.6.x does not match the semantic version expected by drupal.org infrastructure. As a result, no development pipeline is reported on the project page: https://www.drupal.org/project/cookie_content_blocker
The expected branch structure is:
2.x (<-- default branch and dev release, also supports legacy branch naming: 8.x-2.x)
2.6.x (latest release branch)
Comment #6
sjerdoOk, I didn't want to remove branch 8.x-2.x, but I had to, to publish 2.x-dev
Drupal.org blocked me from publishing a 8.x-2.x-dev version
Open MR destination branches are updated
https://www.drupal.org/project/cookie_content_blocker/releases/2.x-dev
Comment #7
sjerdoComment #9
idebr commentedhttps://www.drupal.org/project/cookie_content_blocker now displays dev releases for 2.4.2 and 2.5.0, but not 2.6.1. I suspect this is due to https://www.drupal.org/project/cookie_content_blocker/releases/2.6.x-dev
Can this release be deleted or unpublished? https://www.drupal.org/project/cookie_content_blocker/releases/2.6.x-dev
Comment #10
sjerdoUnfortunately, I am not able to delete version 2.6.x-dev