autobump failing for esphome

[jharris4]

brew gist-logs <formula> link OR brew config AND brew doctor output

It seems that something is broken with autobump for the esphome formula. It's currently stuck at `2025.10.0` despite two new version having been released since then (latest is `2025.10.2`).

The action logs showing the error are here:

https://github.com/Homebrew/homebrew-core/actions/runs/18667033034/job/53220391786#step:6:5211

Relevant snippet:


==> Retrieving PyPI dependencies for "esphome==2025.10.2"...
Error: Unable to determine dependencies for "esphome==2025.10.2" because of a failure when running
`/home/linuxbrew/.linuxbrew/opt/python@3.14/libexec/bin/python -m pip install -q --disable-pip-version-check --dry-run --ignore-installed --report=/dev/stdout esphome==2025.10.2`.
Please update the resources manually.

Verification

• My brew doctor output says Your system is ready to brew. and am still able to reproduce my issue.
• I ran brew update and am still able to reproduce my issue.
• I have resolved all warnings from brew doctor and that did not fix my problem.
• I searched for recent similar issues at https://github.com/Homebrew/homebrew-core/issues?q=is%3Aissue and found no duplicates.
• My issue is not about a failure to build a formula from source.

What were you trying to do (and why)?

get latest version of esphome, but autobump failed, and I seemingly cannot open a version bump PR myself since the formula is marked as auto bumped.

What happened (include all command output)?

Formula is out of date, see long snippet linked above for errors.

What did you expect to happen?

For autobump to work so I can get the latest version

Step-by-step reproduction instructions (by running brew commands)

`brew install esphome`

[alebcay]

Thanks, looking into why the version was not bumped on recent CI runs:

 ==> Retrieving PyPI dependencies for "esphome==2025.10.2"...
Error: Unable to determine dependencies for "esphome==2025.10.2" because of a failure when running
`/home/linuxbrew/.linuxbrew/opt/python@3.14/libexec/bin/python -m pip install -q --disable-pip-version-check --dry-run --ignore-installed --report=/dev/stdout esphome==2025.10.2`.
Please update the resources manually.

[alebcay]

linuxbrew@129c0036d867:~$ /home/linuxbrew/.linuxbrew/opt/python@3.14/libexec/bin/python -m pip install -q --disable-pip-version-check --dry-run --ignore-installed --report=/dev/stdout esphome==2025.10.2
  error: subprocess-exited-with-error

  × Getting requirements to build wheel did not run successfully.
  │ exit code: 1
  ╰─> [20 lines of output]
      Traceback (most recent call last):
        File "/home/linuxbrew/.linuxbrew/opt/python@3.14/lib/python3.14/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 389, in <module>
          main()
          ~~~~^^
        File "/home/linuxbrew/.linuxbrew/opt/python@3.14/lib/python3.14/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 373, in main
          json_out["return_val"] = hook(**hook_input["kwargs"])
                                   ~~~~^^^^^^^^^^^^^^^^^^^^^^^^
        File "/home/linuxbrew/.linuxbrew/opt/python@3.14/lib/python3.14/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 143, in get_requires_for_build_wheel
          return hook(config_settings)
        File "/tmp/pip-build-env-ogam_fly/overlay/lib/python3.14/site-packages/setuptools/build_meta.py", line 331, in get_requires_for_build_wheel
          return self._get_build_requires(config_settings, requirements=[])
                 ~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "/tmp/pip-build-env-ogam_fly/overlay/lib/python3.14/site-packages/setuptools/build_meta.py", line 301, in _get_build_requires
          self.run_setup()
          ~~~~~~~~~~~~~~^^
        File "/tmp/pip-build-env-ogam_fly/overlay/lib/python3.14/site-packages/setuptools/build_meta.py", line 317, in run_setup
          exec(code, locals())
          ~~~~^^^^^^^^^^^^^^^^
        File "<string>", line 79, in <module>
      ImportError: cannot import name 'Str' from 'ast' (/home/linuxbrew/.linuxbrew/opt/python@3.14/lib/python3.14/ast.py)
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error

× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> See above for output.

note: This error originates from a subprocess, and is likely not a problem with pip.

[daeho-ro]

Mostly ruamel.yaml.clib is not required, but this package depends on it recently.

• https://github.com/esphome/esphome/blame/0e703ddbba1815c34b1d4670dc9f6cceff66a0a9/requirements.txt

and it doesn't support Python 3.14 yet.

Collecting ruamel.yaml.clib==0.2.12 (from esphome==2025.10.2)
  Using cached ruamel.yaml.clib-0.2.12.tar.gz (225 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... error
  error: subprocess-exited-with-error
  
  × Getting requirements to build wheel did not run successfully.
  │ exit code: 1
  ╰─> [20 lines of output]
      Traceback (most recent call last):

[daeho-ro]

It is bumped on dev branch,

• esphome/esphome@9ff6f34

and I guess ruamel.yaml.clib is compatible with Python 3.14 from 0.2.13, so the next version will be fine.

[n0tf0und]

At PyPi.org it's at 2025.10.2, so that didn't fix it...

[daeho-ro]

Yes, upstream added Python 3.14 not compatible dependency at the version 2025.10.1 and 2025.10.2. But we have migrated this at 2025.10.0. So the next two versions are failed and need to wait for the next one, e.g. 2025.10.3 because of uamel.yaml.clib need to be updated.

[n0tf0und]

Thank you for a clear explanation of the issue. I will wait for the updated files. All my devices are working fine with the previous version.

…

On Oct 21, 2025, at 7:02 AM, Daeho Ro ***@***.***> wrote: daeho-ro left a comment (Homebrew/homebrew-core#250445) <#250445 (comment)> Yes, upstream added Python 3.14 not compatible dependency at the version 2025.10.1 and 2025.10.2. But we have migrated this at 2025.10.0. So the next two versions are failed and need to wait for the next one, e.g. 2025.10.3 because of uamel.yaml.clib need to be updated. — Reply to this email directly, view it on GitHub <#250445 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEENM7HRDFS4RA4LIFPUXMT3YYHFHAVCNFSM6AAAAACJXSJCNWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTIMRVHE3DGMZQGE>. You are receiving this because you commented.