pyenv

25 MiB

Drzewo: ac5c87e044

Autor	SHA1	Wiadomość	Data
Ivan Pozdeev	57594c0600	More detailed explanation of the band-aid code	2 lat temu
Alex Hedges	dbbe2b63f4	Skip check for miniforge version `4.13.0-0` We always detect missing build scripts for `4.13.0-0` because the release[^1] doesn't have any mambaforge artifacts. Given that we've already created the build files, we don't need to check the release again. [^1]: https://github.com/conda-forge/miniforge/releases/tag/4.13.0-0	2 lat temu
Alex Hedges	a43259a186	Fix overly broad check for existing miniforge build files The glob pattern we were using was too permissive and detecting miniconda build scripts as miniforge build scripts when they shared the same version. I have rewritten the pattern matching code to ensure we only look at files starting with `miniforge` and `mambaforge`.	2 lat temu
Alex Hedges	8316450887	Fix `KeyError` when running `add_miniforge.py` I was attempting to run the script to generate build files for new versions, but it failed because version `23.1.0-4`[^1] contained a malformed `.sha256` file.[^2] I looked at the miniforge repo's script `releases.py`[^3] and copied the logic about which release artifacts should be skipped when generating a list of downloads. [^1]: https://github.com/conda-forge/miniforge/releases/tag/23.1.0-4 [^2]: https://github.com/conda-forge/miniforge/releases/download/23.1.0-4/Miniforge3-uninstaller-patch-Windows-x86_64.exe.sha256 [^3]: `a15762906b/docs/releases.py (L35-L36)`	2 lat temu
Sean McGivern	c7f2c4db45	Add a script to add the latest miniforge and mambaforge versions This takes inspiration from the similar script for miniconda, but it simplifies in a couple of ways: 1. Use the GitHub Releases API instead of scraping HTML. 2. Don't perform a diff, simply add the latest release. Lots of intermediate miniconda releases have been skipped in the past, and it doesn't seem particularly valuable to backfill those.	3 lat temu

5 Commity (ac5c87e044c72062da16b28602a853ee505673b1)