fmt v11.2.0

[regro-cf-autotick-bot]

It is very likely that the current package version for this feedstock is out of date.

Checklist before merging this PR:

• Dependencies have been updated if changed: see upstream
• Tests have passed
• Updated license if changed and license_file is packaged

Information about this PR:

1. Feel free to push to the bot's branch to update this PR if needed.
2. The bot will almost always only open one PR per version.
3. The bot will stop issuing PRs if more than 3 version bump PRs generated by the bot are open. If you don't want to package a particular version please close the PR.
4. If you want these PRs to be merged automatically, make an issue with @conda-forge-admin,please add bot automerge in the title and merge the resulting PR. This command will add our bot automerge feature to your feedstock.
5. If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase @conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

_{This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/cf-scripts/actions/runs/14814842107 - please use this URL for debugging.}

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

[jjerphan]

FYI, this version of fmt comes with at least an API break, see fmtlib/fmt#4466.

Do you think version can be released?

[jjerphan]

@conda-forge-admin, please rerender

[h-vetinari]

FYI, this version of fmt comes with at least an API break, see fmtlib/fmt#4466.

Do you think version can be released?

Given that we switched to minor-level pinning, this should be fine.

[h-vetinari]

Do you think version can be released?

It would be great if we could draw down the 11.1 migration, but since this has been open for ~months, I guess we can just focus that effort on 11.2

[jjerphan]

Note that in environments where spdlog is installed, updating fmt to this version downgrade spdlog to its latest build not depending on fmt.

mamba create -n fmt_spdlog spdlog fmt==11.1.4
mamba update -n fmt_spdlog fmt

  Package         Version  Build       Channel           Size
───────────────────────────────────────────────────────────────
  Install:
───────────────────────────────────────────────────────────────

  + libgcc-ng      15.1.0  h69a702a_3  conda-forge       29kB
  + libstdcxx-ng   15.1.0  h4852527_3  conda-forge       29kB

  Upgrade:
───────────────────────────────────────────────────────────────

  - fmt            11.1.4  h07f6e7f_1  conda-forge     Cached
  + fmt            11.2.0  h07f6e7f_0  conda-forge      193kB

  Downgrade:
───────────────────────────────────────────────────────────────

  - spdlog         1.15.3  h10b92b3_0  conda-forge     Cached
  + spdlog         1.10.0  h924138e_0  conda-forge      356kB

  Summary:

  Install: 2 packages
  Upgrade: 1 packages
  Downgrade: 1 packages

  Total download: 607kB

───────────────────────────────────────────────────────────────

Would the best fix be to repodata-patch the builds before spdlog==1.10.0=h*_0 (included) so that they cannot be installed with fmt? E.g.:

# See: https://github.com/conda-forge/fmt-feedstock/pull/66#issuecomment-3019364053
if:
  name: spdlog
  # Timestamp of spdlog 1.10.0 h*_1
  timestamp_lt: 1666388269911
then:
  - add_constrains:
      - "fmt <0.0a0"

[h-vetinari]

If old spdlog didn't depend on fmt, then I don't think it's the right approach to put in a constraint. The right fix here is to rebuild spdlog for fmt 11.2