- Issue created by @Kartagis
- 🇮🇳India vishal.kadam Mumbai
Apologies.
I have replicated this issue and believe it should be considered as a bug.
Technically, when we update the release node, there is no code change, yet it still proceeds with packaging.
- 🇺🇸United States drumm NY, US
This message is technically correct, packaging is queued. A new zip file for Composer is not regenerated, so it is effectively a no-op. However, packaging also includes updating packages.drupal.org, updates.drupal.org, and some other processes. For some edge cases, this does something for the release.
We could potentially skip showing the message, or show a different message, when you are viewing a tagged release with files already attached.
- 🇹🇷Turkey Kartagis Istanbul
Yes, skipping the message is a better option @drumm.