support miniforge-version: latest, add more architectures #140
Conversation
|
Hi @bollwyvl the motivation was 32/64 bit installers |
Right, but why are they named like they are? As in, |
|
Cant recall :) |
bollwyvl
changed the title
|
Guess it's good to go! And hooray, no parsing (though the page is coming along over on conda-forge/miniforge#89) |
| steps: | ||
| - uses: actions/checkout@v2 | ||
| - uses: ./ | ||
| id: setup-miniconda | ||
| with: | ||
| environment-file: etc/example-environment.yml | ||
| miniforge-version: ${{ matrix.miniforge-version }} | ||
| miniforge-version: latest |
There was a problem hiding this comment.
Should this be miniforge-version: "latest" to conform with miniconda-version: "latest" or does that not matter here?
There was a problem hiding this comment.
it doesn't really matter EVER, as everything is a string in GHAYAML. my kingdom for some * and & anchors... we could likely normalize everything to not be quoted.
There was a problem hiding this comment.
the whole === 'true' thing (and a lack of real schema semantics) is really tiresome
Happy New Miniforge 🎉 ! Turns out we can get
miniforge-version: latestat a predictable (though slightly different) URL.https://docs.github.com/en/free-pro-team@latest/github/administering-a-repository/linking-to-releases
Questions
archinputs on the miniconda architectures? On the miniforge ones, not knowing what to put, i just made it a pass-through, but renamed the constant so we don't get them mixed up...Code changes
latestURL scheme