Don't mark micromamba rc's as latest release in github

[pavelzw]

setup-micromamba uses the latest release by default which results in the rc being rolled out to too many users.

[pavelzw]

@JohanMabille @Klaim @AntoinePrv

[JohanMabille]

Indeed, this was made by accident and has been fixed in the latest commit.1.5.8 has been flaged to be the latest release again.

[pavelzw]

you still need to mark it as not latest in

micromamba-releases/.github/workflows/release.yml

Lines 29 to 39 in b005df8

	- name: Release
	uses: softprops/action-gh-release@v1
	if: steps.fetch-release.outputs.MICROMAMBA_NEW_VERSION == 'true'
	with:
	name: "micromamba ${{ steps.fetch-release.outputs.MICROMAMBA_VERSION }}"
	body: |
	Release artifacts for micromamba ${{ steps.fetch-release.outputs.MICROMAMBA_VERSION }}, mirrored from conda-forge.
	The full changelog can be found [here](https://github.com/mamba-org/mamba/releases).
	tag_name: ${{ steps.fetch-release.outputs.MICROMAMBA_VERSION }}
	files: |
	releases/*

@wolfv just made it a pre-release manually

Once you trigger this workflow a second time for rc1, it will be latest again

[JohanMabille]

Shouldn't the latest commit prevent this issue?

[pavelzw]

not that i can see 🤔 you need to specify prerelease: true for these kinds of releases

https://github.com/softprops/action-gh-release/blob/288696be3916479e99fa944c72825e9b3e192be4/action.yml#L21

[Hind-M]

All dev and prereleases will be skipped when the workflow is triggered automatically unless it's done manually (cf. #46 and #47), but in that case, and if the version is a prerelease, it won't indeed be marked as a prerelease.
#50 should fix it.