Bump zeitwerk from 2.4.2 to 2.6.7

[dependabot]

Bumps zeitwerk from 2.4.2 to 2.6.7.

Changelog

Sourced from zeitwerk's changelog.

2.6.7 (10 February 2023)

• Reset module state on Zeitwerk::NameError.

  If an autoload is triggered, the file is loaded successfully, but the expected constant does not get defined, Ruby resets the state of the module. In particular, autoload? returns nil for that constant name, and constants does not include the constant name (starting with Ruby 3.1).

  Zeitwerk is more strict, not defining the expected constant is an error condition and the loader raises Zeitwerk::NameError. But this happens during the require call and the exception prevents Ruby from doing that cleanup.

  With this change, the parent module is left in a state that makes more sense and is consistent with what Ruby does.

• A message is logged if an autoload did not define the expected constant.

  When that happens, Zeitwerk::NameError is raised and you normally see the exception. But if the error is shallowed, and you are inspecting the logs to investigate something, this new message may be helpful.

• By default, Zeitwerk::Loader#dirs filters ignored root directories out. Please, pass ignored: true if you want them included.

  It is very strange to configure a root directory and also ignore it, the edge case is supported only for completeness. However, in that case, client code listing root directories rarely needs the ignored ones.

• Documentation improvements.

• Enforcement of private interfaces continues with another gradual patch.

2.6.6 (8 November 2022)

• The new eager_load_namespace had a bug when eager loading certain namespaces with collapsed directories. This has been fixed.

2.6.5 (6 November 2022)

• Controlled errors in a couple of situations:

  • Attempting to eager load or reload without previously invoking setup now raises Zeitwerk::SetupRequired.

  • The method Zeitwerk::Loader#push_dir raises Zeitwerk::Error if it gets an anonymous custom namespace.

  These should be backwards compatible, because they raise in circumstances that didn't work anyway. The goal here is to provide a meaningful error upfront.

... (truncated)

Commits

• 7cac78e Ready for 2.6.7
• 5967ef6 CHANGELOG edit
• a044dc7 CI: Remove exclusion of Ruby 3.2 on windows-latest
• 01696a7 CHANGELOG edits
• 9f93a06 Mark private methods individually in Zeitwerk::Loader
• 4acfd42 Make the private shadowed_file? internal
• 88905f1 Make the private mutex2 Ruby-private
• 3a4cd12 Make the private mutex Ruby-private
• 7955120 Make the private shadowed_files internal
• 1b5d46f Make the private namespace_dirs internal
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)