Contrib.social

Can not remove 2.0.x branch or make 2.x branch as supported

Open on Drupal.org →
Created on 26 February 2025, about 1 month ago

Problem/Motivation

I have a problem with https://www.drupal.org/project/bs_lib → contrib project. By mistake I've created 2.0.x branch first and dev release and later figured that I should create 2.x brach as a new major dev release. I've then pushed 2.x branch to ddo and managed to create 2.x-dev release from it. However I can not mark this release as supported on https://www.drupal.org/node/2894018/edit/releases → because 'Supported' checkbox for this release is disabled.

Also I can not remove 2.0.x branch and release, I've tried deleting branch but it is denied in Gitlab with a message 'Prevented by server hooks' or in console

➜  bs_lib git:(2.x) ✗ git push origin :2.0.x 
remote: The branch 2.0.x is tied to a development release on Drupal.org, and cannot be deleted.
remote: error: hook declined to update refs/heads/2.0.x
To git.drupal.org:project/bs_lib.git
 ! [remote rejected] 2.0.x (hook declined)
error: failed to push some refs to 'git.drupal.org:project/bs_lib.git

Now I get that because there is a release for 2.0.x I can not delete this branch and that makes sense, but how can I mark 2.x-dev release that it is now supported?

💬 Support request
Status

Active

Component

Git

Created by

🇷🇸Serbia pivica

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @pivica
  • Comment about 1 month ago →
    🇷🇸Serbia pivica

    BTW exactly the same error I made in bs_base → contrib theme on https://www.drupal.org/node/2839205/edit/releases → - I can't mark 2.x-dev as a Supported version because that checkbox is disabled.

  • Comment about 1 month ago →
    🇺🇸United States drumm NY, US

    The branch 2.0.x is tied to a development release on Drupal.org, and cannot be deleted.

    Since 2.0.x is more specific, it takes precedence over 2.x. I recommend using 2.0.x. When 2.0.x is ready to diverge from what will become 2.1.*, then you can ensure 2.x is caught up, and continue using 2.x for the remainder of the 2.* series.

    “Supported” release series are really for the tagged releases. The branch itself is never really supported as dev releases are expected to have some amount of instability. There will always be more-specific series, 2.1.*, 2.2.*, etc, and those are supported or not. 2.* itself never has a tagged release associated with it, and isn’t tracked as supported.

  • Comment about 1 month ago →
    🇷🇸Serbia pivica

    @drumm thx for your feedback, I will organize 2.x development then how you suggested.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024