- Issue created by @gbyte
- ๐ณ๐ดNorway gisle Norway
AFAIK, site moderators don't have the ability to delete releases. But maybe someone with more knowledge than me and be more helpful.
- ๐ฎ๐ณIndia vishal.kadam Mumbai
I believe only drupal infra team can delete releases.
- Assigned to drumm
- Status changed to Closed: won't fix
9 months ago 4:22pm 27 December 2023 - ๐บ๐ธUnited States drumm NY, US
Tagged releases are permanent and can not be deleted. The major version would eventually get to 4.0.1 again, and having 2 codebases with the same version would defeat the purpose of versioning.
I recommend continuing on from 4.0.1, releasing 4.0.2 or 4.1.0 next.
- ๐ฉ๐ชGermany gbyte Berlin
@drumm
The major version would eventually get to 4.0.1 again, and having 2 codebases with the same version would defeat the purpose of versioning.
You may be misunderstanding the problem. The module was on 1.0.0 and instead of pushing the tag 1.0.1 I pushed 4.0.1 (4.x branch did not exist). So it would be tremendously helpful to delete the 4.x branch & that release so I don't have to pretend the module is on its 4th breaking iteration. Please reconsider.
- ๐บ๐ธUnited States drumm NY, US
As mentioned when creating the release, โTagged releases are permanentโ and at https://www.drupal.org/docs/develop/git/git-for-drupal-project-maintaine... โ , this is not possible. We can not compromise the integrity of releases on Drupal.org.