New version of zeitwerk (2.7.3) broke the build

Open depfu[bot] opened this issue 7 months ago • 0 comments

We've tested your project with an updated dependency and the build failed.

This version is either within the version range you specified or you haven't specified a version/range. To be able to test your project with the new version, we've taken the liberty of pinning the version for this branch and pull request.

name	version specification	new version
zeitwerk	~> 2.6	2.7.3

Unfortunately, we encountered failing tests after pinning. This means that this new version is not compatible with your project and the test failure will potentially also happen on fresh installs.

If you have correctly specified a semantic versioning version range, you should probably also file an issue with the upstream project as they might have released an update that's breaking SemVer rules, which is not cool. (But then again, not all projects explicitly follow SemVer)

We've left the pull request open for you to investigate this issue. Please don't merge it as is, because, again, we've pinned the version of zeitwerk for this test run.

What changed?

✳️ zeitwerk (~> 2.6 → 2.7.3) · Repo · Changelog

Release Notes

2.7.3 (from changelog)

The helper Zeitwerk::Loader#cpath_expected_at did not work correctly if the inflector had logic that relied on the absolute path of the given file or directory. This has been fixed.

This bug was found by Codex.

Perpetual internal work.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 16 commits:

May 21 '25 10:05 depfu[bot]