Bump zeitwerk from 2.5.1 to 2.6.0

[dependabot]

Bumps zeitwerk from 2.5.1 to 2.6.0.

Changelog

Sourced from zeitwerk's changelog.

2.6.0 (13 June 2022)

• Directories are processed in lexicographic order.

  Different file systems may list directories in different order, and with this change we ensure that client code eager loads consistently across platforms, for example.

• Before this release, subdirectories of root directories always represented namespaces (unless ignored or collapsed). From now on, to be considered namespaces they also have to contain at least one non-ignored Ruby file with extension .rb, directly or recursively.

  If you know beforehand a certain directory or directory pattern does not represent a namespace, it is intentional and more efficient to tell Zeitwerk to ignore it.

  However, if you don't do so and have a directory tasks that only contains Rake files, arguably that directory is not meant to represent a Ruby module. Before, Zeitwerk would define a top-level Tasks module after it; now, it does not.

  This feature is also handy for projects that have directories with auxiliary resources mixed in the project tree in a way that is too dynamic for an ignore pattern to be practical. See fxn/zeitwerk#216.

  In the unlikely case that an existing project has an empty directory for the sole purpose of defining a totally empty module (no code, and no nested classes or modules), such module has now to be defined in a file.

  Directories are scanned again on reloads.

• On setup, loaders created with Zeitwerk::Loader.for_gem issue warnings if lib has extra, non-ignored Ruby files or directories.

  This is motivated by existing gems with directories under lib that are not meant to define Ruby modules, like directories for Rails generators, for instance.

  This warning can be silenced in the unlikely case that the extra stuff is actually autoloadable and has to be managed by Zeitwerk.

  Please, check the documentation for further details.

  This method returns an instance of a private subclass of Zeitwerk::Loader now, but you cannot rely on the type, just on the interface.

2.5.4 (28 January 2022)

... (truncated)

Commits

• d65188d Ready for 2.6.0
• a97fe57 Edit
• d80cb42 Edits the CHANGELOG
• 1c7b2ea Pass over some docs
• 2850873 Undo concurrent autoload while reloading detection
• c82e2ef Iterates the docs for implicit namespaces
• 69fdf98 Add test coverage and more for processing order
• 5643e4a Merge pull request #219 from Shopify/consistent-load-order
• de83279 Eager load constants in a consistent order
• ae2bb08 Add a comment about the return type of for_gem
• 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)