test-nightly-conda-env failing on `main`: environment pinned back to July 23 (6 days ago)

[jameslamb]

Description

See https://github.com/rapidsai/integration/actions/runs/30438522969/job/90576973355

All builds of test-nightly-conda-env on main here are failing like this:

Error: The following packages are more than 3 days old:
 - cucim:                  	2026-07-23
 - cudf:                   	2026-07-23
 - cudf-polars:            	2026-07-23
 - cudf-streaming:         	2026-07-23
...

The following packages are less than 3 days old:
 - cucim:                  	2026-07-23
 - cudf:                   	2026-07-23
 - cudf-polars:            	2026-07-23
 - cudf-streaming:         	2026-07-23
....
Error: Process completed with exit code 1.

I've omitted the full list, but it looks like every (or almost every) RAPIDS package is solving back to its version from July 23rd (6 days ago as of this writing). It's also weird to see the same packages show up in both the "more than 3 days old" and "less than 3 days old" lists, suspect there's a bug there.

Most builds succeeded overnight (https://github.com/rapidsai/workflows/actions/runs/30426717524) and there are definitely newer packages available, e.g. at https://anaconda.org/channels/rapidsai-nightly/packages/cudf/files

I think there may be 2 issues here:

• something is holding the environment solve back to old packages... this will turn into failing CI once older nightlies are deleted
• the reporting of packages more / less than 3 days old has some bug that allows the same package to show up in both lists

Reproducible Example

See recent test jobs on main at https://github.com/rapidsai/integration/actions/runs/30438522969

This does not affect release/26.08.

Notes

N/A

[jameslamb]

Oh wait, that screenshot I shared is for 26.08 package!

The latest 26.10 packages I see really are from July 23rd.

On the latest cudf nightly build for main, I see both uploads being skipped:

https://github.com/rapidsai/cudf/actions/runs/30427642101/job/90501623334

The timing plus that location makes me suspect rapidsai/shared-workflows#602, looking