Delete erroeneous major release tag in project

Created on 26 December 2023, 9 months ago
Updated 29 December 2023, 9 months ago

I erroneously pushed and published a tag that is 3 major versions above what was meant to be. The project is on 1.x and I pushed 4.x. :(
Could you please delete that release/tag as to not confuse the users? This particular module is not popular and I unpublished the release right away so this should not be a problem.

Module page: https://www.drupal.org/project/mail_composer โ†’
Erroneous release: https://www.drupal.org/project/mail_composer/releases/4.0.1 โ†’

I wouldn't be bothering you if it was a minor release typo. Thanks a lot.

๐Ÿ“Œ Task
Status

Closed: won't fix

Component

Git

Created by

๐Ÿ‡ฉ๐Ÿ‡ชGermany gbyte Berlin

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

Comments & Activities

  • 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.

  • ๐Ÿ‡ฉ๐Ÿ‡ชGermany gbyte Berlin

    How can I reach them?

  • ๐Ÿ‡ฎ๐Ÿ‡ณIndia vishal.kadam Mumbai

    Moving to infrastructure issue queue

  • Assigned to drumm
  • Status changed to Closed: won't fix 9 months ago
  • ๐Ÿ‡บ๐Ÿ‡ธ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.

Production build 0.71.5 2024