Update compile_enumerate_no_versions snapshot

[charliermarsh]

Summary

I think the "available versions" may not filter on --exclude-newer, since it's marked as an incompatibility? In which case, this error message can change as versions are published.

[zanieb]

That doesn't sound right — we explicitly treat unavailable versions due to exclude newer as entirely missing during error messaging for reproducibility.

[zanieb]

uv/crates/uv-resolver/src/candidate_selector.rs

Lines 495 to 510 in 8b6383e

	// If candidate is not compatible due to exclude newer, continue searching.
	// This is a special case — we pretend versions with exclude newer incompatibilities
	// do not exist so that they are not present in error messages in our test suite.
	// TODO(zanieb): Now that `--exclude-newer` is user facing we may want to consider
	// flagging this behavior such that we _will_ report filtered distributions due to
	// exclude-newer in our error messages.
	if matches!(
	candidate.dist(),
	CandidateDist::Incompatible(
	IncompatibleDist::Source(IncompatibleSource::ExcludeNewer(_))
	| IncompatibleDist::Wheel(IncompatibleWheel::ExcludeNewer(_))
	)
	) {
	continue;
	}

[zanieb]

but I guess it's possible it manifests still somehow?

[charliermarsh]

Yeah, but this is based on available_versions? And available_versions is populated by versions_response.

[zanieb]

I see, that makes sense I think.

[charliermarsh]

I can fix it at some point (even later today), I just want to get this passing to unblock.