Installing latest.release Nextflow with grape installs edge prerelease

[SamStudio8]

Bug report

Expected behavior and actual behaviour

I have some Groovy scripts that use parts of the Nextflow library and specify the dependency with @Grab directives to use the Grape dependency manager. I expected that requesting the latest.release of Nextflow with Grape would install the release that is currently served by get.nextflow.io (22.10.7), but instead Grape installs the 23.02.0-edge prerelease.

% grape install io.nextflow nextflow latest.release
:: resolving dependencies :: caller#all-caller;working33
        confs: [default]
        found io.nextflow#nextflow;23.02.0-edge in ibiblio

The latest.release Ivy matcher returns the newest module revision with "at least release" status (https://ant.apache.org/ivy/history/2.1.0/settings/version-matchers.html). Is it expected that these prereleases are marked as a release? Is there another status I could be using?

Program output

NA

Environment

• Nextflow version: NA
• Java version: OpenJDK Runtime Environment Homebrew (build 17.0.3+0)
• Operating system: macOS
• Bash version: zsh 5.8

Additional context

NA

[SamStudio8]

Ah. Looking at the Maven metadata model and the Nextflow maven-metadata.xml, it seems this "status" is not part of the Maven metadata spec. But perhaps the versioning.release in Nextflow's Maven metadata should be set to whatever you consider the latest supported release (and not a prerelease)?

<versioning>
<latest>23.02.0-edge</latest>
<release>23.02.0-edge</release>

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.