Skip to content

Conversation

@depfu
Copy link
Contributor

@depfu depfu bot commented May 21, 2025

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:

@depfu depfu bot added the depfu label May 21, 2025
@katafrakt
Copy link
Contributor

@depfu rebase

@depfu depfu bot force-pushed the depfu/check/zeitwerk-2.7.3 branch from 66cdde3 to 6ed91cf Compare October 23, 2025 12:14
@depfu
Copy link
Contributor Author

depfu bot commented Oct 23, 2025

All good now, closing.

@depfu depfu bot closed this Oct 23, 2025
@depfu depfu bot deleted the depfu/check/zeitwerk-2.7.3 branch October 23, 2025 13:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants