Update to conda 23.11, mamba 1.5.5, libmamba_solver 23.12

[hmaarrfk]

This reverts #522 and in effect updates to 23.10 (or soon 23.11)

• Work must be done to address Release 23.10 #511 (comment)
• Resolve KeyError in some conda-build cases conda/conda-libmamba-solver#386
• Other bugs? (@mbargull please feel free to edit this message)

Closes #511

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

[mbargull]

Thanks @hmaarrfk.
I'll get back to you once we know more on when/how/if we get a new conda release with the mentioned issue resolved.

[mbargull]

We have an build for mamba=1.5.5 pending at conda-forge/mamba-feedstock#206 .
Once that one is up, we can include that update here.

With conda=23.11.0 and mamba=1.5.5 we should have all major issues I know of covered and I'd say we could then finally proceed with a new Miniforge release :).

[jaimergp]

conda-libmamba-solver 23.12.0 is out now, solving the "KeyError" issues too.

[jaimergp]

I think we should specify this key too: https://conda.github.io/constructor/construct-yaml/#user-requested-specs

This would allow us to have a cleaner history, without pinning key specs to certain versions. For example:

user_requested_specs:
{% if name.endswith("pypy3") %}
  - python 3.9.* *_pypy
{% else %}
  - python 3.10.*
{% endif %}
  - pip
  - conda >={{ version.split("-")[0] }}
  - mamba >={{ mamba_version }}
  - miniforge_console_shortcut 1.*  # [win]

Note we have left conda-libmamba-solver out so it's not in history and can freely move (conda requires it now). We only specify the "leave" nodes, and with >= constraints so they can be easily upgraded. This should alleviate issues like mamba-org/mamba#3033 (comment).

[mbargull]

@hmaarrfk, @jaimergp, good to go?

[jakirkham]

This would be a prerelease initially right?

Think ideally we would make the release official Monday or Tuesday in case we need hands available to resolve issues (should any arise)

[hmaarrfk]

I think it makes sense to make the pre-release this weekend, then to make a release on monday

[jaimergp]

Yep, I have some time to babysit the release this week.

[hmaarrfk]

if somebody else presses merge, i can start the pre-release.

[beckermr]

@mbargull @jaimergp @hmaarrfk can we get push this ahead? Shall I merge?

[mbargull]

@mbargull @jaimergp @hmaarrfk can we get push this ahead? Shall I merge?

Ah, didn't notice @hmaarrfk's last comment.
Thanks for the ping.
Merge, merge

[hmaarrfk]

how are we feeling about the latest conda-smithy woes. I haven't been keeping up with the details so I was hesitant to merge myself.

[hmaarrfk]

Just FYI, prerelease started. we can mark it as release when we want to in an hour or so
https://github.com/conda-forge/miniforge/releases/tag/23.11.0-0

[mbargull]

how are we feeling about the latest conda-smithy woes. I haven't been keeping up with the details so I was hesitant to merge myself.

That was just due to a minor change in conda-build=3.28.2 that broke an assumption in downstream smithy code.
ref: conda/conda-build#5125
It should be taken care of with the new smithy release and adjusted dependencies for older builds.
Shouldn't affect Miniforge.

Just FYI, prerelease started. we can mark it as release when we want to in an hour or so https://github.com/conda-forge/miniforge/releases/tag/23.11.0-0

Thanks!
(We had one build stalled; I restarted it and it just finished so that all release artifacts should be available now.)

[hmaarrfk]

Ok. Seems like we are set. I won't have time to pull a release today in case of errors but I can help tomorrow.

If somebody else wants to take responsibility today then the tag seems ready to be marked as latest