- 🇺🇸United States drumm NY, US
However, you don't know and don't get informed when packaging scripts are running.
This was fixed, and packaging usually runs within a minute now.
In short: The "Supported versions" UI on the project node should also show unpublished release nodes, so they can be configured.
After creating a new release node for a branch, it is unpublished until the packaging scripts ran.
However, you don't know and don't get informed when packaging scripts are running.
The "Supported versions" configuration for a project does not expose unpublished releases currently.
Hence, you have no idea how your new release (node) is going to be visible (or not) as soon as it is published.
I had various different situations, in which I wanted a new release to appear on a project page, and then again others, in which I wanted a new release (say, dev snapshot) to NOT appear on the project page (because of highly experimental code for a new major version).
Closed: outdated
1.0
Releases
However, you don't know and don't get informed when packaging scripts are running.
This was fixed, and packaging usually runs within a minute now.