- Issue created by @steveoriol
- ๐ฉ๐ฐDenmark ressa Copenhagen
I am also seeing this on Drupal 10, I don't think the update from Drupal 9 is connected.
But it looks like a 1.1.21 was accidentally tagged, so now Composer downloads 1.1.21 as the latest release, whereas 1.0.22 really is the latest ...
https://www.drupal.org/project/tagify/releases/1.1.21 โ
- 1.0.22 - 13 November 2023
- 1.0.21 - 10 November 2023
- 1.1.21 - 10 November 2023
- 1.0.20 - 9 November 2023
- ๐ช๐ธSpain gxleano Cรกceres
Hi @steveoriol
As @ressa said release
1.1.21
was accidentally tagged, the latest version is1.0.22
, I will work to remove the wrong release1.1.21
.For now, please downgrade to version
1.0.22
, I will close this issue when everything works fine.Thanks to report it.
- ๐ช๐ธSpain gxleano Cรกceres
@steveoriol it has been fixed. I've created the next release https://www.drupal.org/project/tagify/releases/1.1.23 โ . Could you check that everything is fine now?
- Status changed to Needs review
8 months ago 8:42pm 15 November 2023 - Status changed to Fixed
8 months ago 8:52pm 15 November 2023 - Status changed to Fixed
8 months ago 8:56pm 15 November 2023 - ๐ฉ๐ฐDenmark ressa Copenhagen
Thanks for reporting @steveoriol, and @gxleano for a quick response, it looks fine now. Perhaps 1.1.x should now be the default branch on Gitlab as well? https://git.drupalcode.org/project/tagify
For a fresh start with correct numerical continuity, a new 1.2.x dev-branch and next official release 1.2.0 could be considered?
- ๐ช๐ธSpain gxleano Cรกceres
@ressa
1.1.x is already the default branch, next release I will clean up the mess on the branching name.
- ๐ฉ๐ฐDenmark ressa Copenhagen
I believe the default branch was 1.0 on Gitlab when I checked, but great that it is also 1.1 there now.