New version of zeitwerk (2.7.2) broke the build #464
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
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.2) · Repo · Changelog
Release Notes
2.7.2 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 30 commits:
Ready for 2.7.2Let get_or_set evaluate the fallback lazilyAdd a couple more of testsDefine get_or_set for cref mapsRevises some signaturesFixes signature annotationAdds a test for cref mapsDocs improvementsAdds code commentsIntroduce Zeitwerk::Cref::MapSynchronize the inceptions registry if not in CRubyRemove top-level constantMark the private callback for namespaces as internalMove inceptions to their own registryRemove truffleruby-head from this workflowAdd Ruby 3.4 to CIMerge pull request #311 from fxn/trufflerubyAdd TruffleRuby stable to CICreate a proper registry for explicit namespacesRevises some signaturesDefine Zeitwerk::Cref#to_sPass crefs to the registryRevert "Define Zeitwerk::Cref#{to_s,hash,eql?,==}"Revert "Support hashing crefs whose mod has an overridden name"Revert "Rename some variables"Rename some variablesSupport hashing crefs whose mod has an overridden nameDefine Zeitwerk::Cref#{to_s,hash,eql?,==}Edit a commentKeep an eye on TruffleRuby HEAD