drupal/flag_block reports incorrect latest version

Created on 20 November 2023, about 1 year ago

composer show --outdated --format=json drupal/flag_block|jq -r .latest says 8.1.3

https://www.drupal.org/project/flag_block/releases/8.x-1.5 β†’ exists.

πŸ› Bug report
Status

Active

Version

1.0

Component

Packaging

Created by

πŸ‡¨πŸ‡¦Canada Charlie ChX Negyesi 🍁Canada

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

Comments & Activities

  • Issue created by @Charlie ChX Negyesi
  • πŸ‡¨πŸ‡¦Canada Charlie ChX Negyesi 🍁Canada
  • πŸ‡ΊπŸ‡ΈUnited States drumm NY, US

    There is an 8.1.3 release: https://www.drupal.org/project/flag_block/releases/8.1.3 β†’ , so the 8.1.x series of releases is the latest.

    The 8.x- prefix is discarded for version numbers in Composer. 8.x-1.5 is 1.5.0 for Composer. 8.1.3 > 1.5.0, so it is technically the latest, 8 > 1.

    Since release numbers need to keep moving forward, so I recommend making a 8.x or 8.1.x branch, and tagging a 8.1.4 or greater release. It would be fine to skip to 8.1.5 or 8.1.6 to reduce some confusion. Or could even jump to 8.2.0 or even 9.0.0 for more of a clean slate.

    Semantically-versioned version numbers, without the 8.x- prefix, have no relation to what versions of Drupal core it is compatible with. Don't for example make a 10.0.0 release when the project is compatible with Drupal 10. You do need to continue from 8.1.3 since it is already released.

    The 8.1.3 release can not be deleted, unpublished, or otherwise undone. Releases on Drupal.org are permanent. We would not want to take a release people are using away, or worse, we would not want it replaced with different code.

  • Status changed to Fixed about 1 month ago
  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.71.5 2024