Beet build mysteriously starts failing

[Newtbytes]

A project of mine uses beet and has automated builds, but recently these build have started to fail due to some bug with beet. The builds fail with this error:

Error: An unhandled exception occurred. This could be a bug.

Traceback (most recent call last):
  File "/opt/hostedtoolcache/Python/3.10.19/x64/lib/python3.10/site-packages/beet/toolchain/cli.py", line 50, in error_handler
    yield
  File "/opt/hostedtoolcache/Python/3.10.19/x64/lib/python3.10/contextlib.py", line 79, in inner
    return func(*args, **kwds)
  File "/opt/hostedtoolcache/Python/3.10.19/x64/lib/python3.10/site-packages/click/decorators.py", line 93, in new_func
    return ctx.invoke(f, obj, *args, **kwargs)
  File "/opt/hostedtoolcache/Python/3.10.19/x64/lib/python3.10/site-packages/click/core.py", line 814, in invoke
    return callback(*args, **kwargs)
  File "/opt/hostedtoolcache/Python/3.10.19/x64/lib/python3.10/site-packages/beet/toolchain/commands.py", line 50, in build
    click.echo(project.link(world=link))
  File "/opt/hostedtoolcache/Python/3.10.19/x64/lib/python3.10/site-packages/beet/toolchain/project.py", line 196, in link
    link_manager.setup_link(world, minecraft, data_pack, resource_pack)
  File "/opt/hostedtoolcache/Python/3.10.19/x64/lib/python3.10/site-packages/beet/contrib/link.py", line 84, in setup_link
    world = Path(world).resolve()
  File "/opt/hostedtoolcache/Python/3.10.19/x64/lib/python3.10/pathlib.py", line 960, in __new__
    self = cls._from_parts(args)
  File "/opt/hostedtoolcache/Python/3.10.19/x64/lib/python3.10/pathlib.py", line 594, in _from_parts
    drv, root, parts = self._parse_args(args)
  File "/opt/hostedtoolcache/Python/3.10.19/x64/lib/python3.10/pathlib.py", line 578, in _parse_args
    a = os.fspath(a)
TypeError: expected str, bytes or os.PathLike object, not Sentinel
make: *** [makefile:29: build-resourcepack] Error 1
Error: Process completed with exit code 2.

You can look at all of the failing builds here:
https://github.com/Newtbytes/gcats/actions/workflows/build.yml

It looks like it has something to do with the update to beet 0.112.0