Closed
Labels
bugIssues reporting a defect (set by the bug report template; a default, not an assessment)Issues reporting a defect (set by the bug report template; a default, not an assessment)ciPull requests that change CI or workflow configuration (ci: subject prefix)Pull requests that change CI or workflow configuration (ci: subject prefix)
Milestone
Description
anaconda.org has pypcapkit 1.5.0b14 for linux-64 and osx-arm64 only, five files each. There are no osx-64 files. Every Create Release run on main that reaches the released-elsewhere path therefore warns that v1.5.0b14 is unfinished (#1634) … still lacks some of its Anaconda files (e.g. run 40060270948 at 8fdc2fb33). That is 5 of the last 60 runs.
- Cause, inferred: the
macos-26-intelconda legs were broken when 1.5.0b14 was released. ci(conda): macos-26-intel conda legs fail on libmambapy 2.10.0 and conda-build 26.9's rpath relocation #2123 / ci(conda): build the macos-26-intel legs again (#2123) #2124 fixed them afterwards. - The warning's advice is wrong for this case. It says to re-run the Create Release run created for the tagged commit. That run executes the tag's own workflow, whose Intel leg is the broken one.
Wanted:
- Get
osx-641.5.0b14 onto Anaconda. Saturday's scheduled Conda Update may already do this, since its Intel legs now pass; check after that run. Otherwise it needs a manual upload, which is the owner's call. - Make the warning name the right remedy when re-running the old run cannot fix it.
Found by the #2138 worker while scoping that PR's completeness change. #2138 counts only the platforms a version's tagged commit published, so it neither adds nor removes this warning.
Metadata
Metadata
Assignees
Labels
bugIssues reporting a defect (set by the bug report template; a default, not an assessment)Issues reporting a defect (set by the bug report template; a default, not an assessment)ciPull requests that change CI or workflow configuration (ci: subject prefix)Pull requests that change CI or workflow configuration (ci: subject prefix)
Projects
- StatusShow more project fieldsDone
Activity
JarryShaw commentedon Oct 24, 2026
Let's manually trigger the run now then
JarryShaw commentedon Oct 24, 2026
Dispatched, but a manual Conda Update is build-only and can't upload the osx-64 files. The scheduled run will most likely upload nothing either. Details and the decision are on #2060.
JarryShaw commentedon Oct 25, 2026
Item 1 is done. The
publishdispatch in #2060 uploaded 1.5.0b14 build 1 for every platform. anaconda.org now lists 5osx-64files, alongsidelinux-645,osx-arm645 andwin-645. So the latest tag is complete and Create Release's "unfinished" warning should stop.Item 2 is still open. When re-running the tagged commit's Create Release can't fix it, the warning should name the real remedy, which since #2150 is a Conda Update dispatch with
publishonmain. Dispatching a worker for it now. Movedpending→wip.JarryShaw commentedon Oct 25, 2026
Item 1 is confirmed on
main. Create Release 40152325584 atcace9c5abno longer warns. It now posts a notice that v1.5.0b14 names6a9b666a1and "that release is complete, so this run correctly released nothing (#1748)". Item 2 is #2151, atreview: good-to-go, with CI finishing.ci(release): name the right remedy when the latest release lacks Anac…