pyenv

3242 Révisions

2 Branches

84 MiB

Aborescence: 8316450887

Graphique des révisions

Auteur SHA1 Message Date

Auteur	SHA1	Message	Date
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)`	il y a 2 ans
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.	il y a 3 ans

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)

il y a 2 ans

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.

il y a 3 ans

2 Révisions (8316450887d8843b7e21bbad21002c9708ff59cf)