mamba-org
Add micromamba nightly releases
For each main commit where the static-build.yml workflow succeeds, the workflow will afterwards create a new tag on a separate repository (for example mamba-org/micromamba-nightlies) where the built artifacts get uploaded. This fixes the issue of static build artifacts being deleted after 90 days.
Since every release needs to point to a specific commit sha in this new repository, we need to pin each release to a specific commit. We have two options here:
- For each run, create a new commit that modifies the readme in the nightlies repo (for example displaying the current SHA and commit details) and create a release on this commit.
- Create a tag every time on
HEADleading to hundreds of tags onHEAD.
Still to do:
- [ ] add counter to version number to show (for example make releases like this:
v0.26.0-<counter-increment>-<first-letters-of-sha>) - [ ] Add new version string to
micromamba --version(this closes #1929)
Proof of concept can be seen in pavelzw/micromamba-releases with corresponding workflow runs in pavelzw/mamba #7.
One easy-to-implement counter would be the actions run id, i.e., the thing that is in the url in https://github.com/mamba-org/mamba/actions/runs/<run-id>.
Do we actually need a separate commit/tag per release? Is that a GH requirement?
I wonder if we should not include counter and version in the release name. We should optimize for ease of installation of a specific SHA (or date if we decide to do actual nightlies)
Do we actually need a separate commit/tag per release? Is that a GH requirement?
Yes, each release needs a separate tag (we can use the same commit with multiple tags, though).
Details
I wonder if we should not include counter and version in the release name.
The problem then is that it is not obvious which version is newer when comparing versions...
Not completely, I just took a break from it 😅
The release on a custom channel part works but I still wanted to add the commit hash to micromamba --version.