25.1.0: conda_build.deprecations.DeprecatedError when executing commands

[OddBloke]

Checklist

• I added a descriptive title
• I searched open reports and couldn't find a duplicate

What happened?

We just attempted to build a new package from the 25.1.0 tag, and saw this error in our testing:

$ conda-build --help
Traceback (most recent call last):
  File "/usr/bin/conda-build", line 5, in <module>
    from conda_build.cli.main_build import execute
  File "/usr/lib/python3.10/site-packages/conda_build/cli/main_build.py", line 19, in <module>
    from .. import api, build, source, utils
  File "/usr/lib/python3.10/site-packages/conda_build/api.py", line 24, in <module>
    from .config import DEFAULT_PREFIX_LENGTH as _prefix_length
  File "/usr/lib/python3.10/site-packages/conda_build/config.py", line 28, in <module>
    from .utils import (
  File "/usr/lib/python3.10/site-packages/conda_build/utils.py", line 70, in <module>
    from .exceptions import BuildLockError
  File "/usr/lib/python3.10/site-packages/conda_build/exceptions.py", line 50, in <module>
    class UnableToParseMissingJinja2(UnableToParse):
  File "/usr/lib/python3.10/site-packages/conda_build/deprecations.py", line 111, in deprecated_decorator
    raise DeprecatedError(message)
conda_build.deprecations.DeprecatedError: conda_build.exceptions.UnableToParseMissingJinja2 was slated for removal in 25.1.

This can be reproduced simply with python3 -c 'import conda_build.exceptions'

Conda Info

Conda Config

Conda list

Additional Context

No response

[OddBloke]

This also appears to be the cause of the CI failure at https://github.com/conda/conda-build/actions/runs/12773009125/job/35603905717#step:5:1281

[kenodegard]

@OddBloke thanks for bringing this to our attention, working on a fix, please use conda-build=24.11 in the meantime

[jezdez]

Fixed via #5588

[tkelman]

Should removing deprecations be added to the release process or was this a case of tagging before noticing the tests failing?

[OddBloke]

Thanks for the speedy resolution here! I can confirm that 25.1.1 went through our build and test pipelines without a hitch: wolfi-dev/os#39596

[kenodegard]

@tkelman Should removing deprecations be added to the release process or was this a case of tagging before noticing the tests failing?

unsure what went wrong, we have opened #5590 to investigate further