You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 81d55de
Browse filesBrowse the repository at this point in the historyBrowse files
ci(conda): move platform pins up and give them a review-by date (#1851)
- Move PLATFORM_PINS into conda/platform-pins.toml, so the weekly job can
rewrite it; each pin carries a version, a review-by date and a reason.
- Add util/conda_vendor.py --refresh-pins: it reads PyPI's JSON, finds the
newest release up to the installed one with a wheel every conda Python
installs on the pinned platform, abi3 and universal2 included, and moves
the pin there, due for review REVIEW_HORIZON out. A pin that reaches the
installed release, or already pins it, is dropped. A PyPI failure warns
and keeps the pin.
- Run it in conda-update before the requirements are written.
- --check stays offline and now fails on a pin past its review-by date.
- Keep the table out of BOT_MANAGED_PATHS, pinned by a test, and correct
that comment's claim about which files tests read.
- Read the pin from the table in the #1827 tests, and fix today in the
#1814 --check tests, so a moved or overdue pin does not break them.
Closes#1851
# The packages conda/requirements.txt pins apart on some conda platforms, as a
2
+
# table per package and conda subdir (#1827): the version that platform vendors
3
+
# in place of the installed release, the date the pin is due for review by, and
4
+
# why the platform cannot take the installed release.
5
+
#
6
+
# util/conda_vendor.py reads this file. Conda Update's `conda-update` job runs
7
+
# its `--refresh-pins` first, which asks PyPI for the newest release, up to the
8
+
# installed one, with a wheel each conda Python installs on the pinned platform.
9
+
# It moves the pin up to that release with a fresh review-by date, and drops a
10
+
# pin that reaches the installed release or already pins it (#1851). `--check`
11
+
# fails on a pin past its review-by date: check by hand that the pin still
12
+
# holds, then set a new date. The job writes this whole file, this comment
13
+
# included, so anything a pin needs said goes in its `reason`.
14
+
15
+
[cryptography.osx-64]
16
+
version = "48.0.1"
17
+
review-by = 2027-01-15
18
+
reason = "Its newest releases ship no Intel or universal2 macOS wheel, so the osx-64 build would compile them from source; 49.0.0 was the first (#1827)."
0 commit comments