build(deps): bump zeitwerk from 2.4.2 to 2.5.4 in /docs

[dependabot]

Bumps zeitwerk from 2.4.2 to 2.5.4.

Changelog

Sourced from zeitwerk's changelog.

2.5.4 (28 January 2022)

• If a file did not define the expected constant, there was a reload, and there were on_unload callbacks, Zeitwerk still tried to access the constant during reload, which raised. This has been corrected.

2.5.3 (30 December 2021)

• The change introduced in 2.5.2 implied a performance regression that was particularly dramatic in Ruby 3.1. We'll address #198 in a different way.

2.5.2 (27 December 2021)

• When Module#autoload triggers the autovivification of an implicit namespace, $LOADED_FEATURES now gets the correspoding directory pushed. This is just a tweak to Zeitwerk's Kernel#require decoration. That way it acts more like the original, and cooperates better with other potential Kernel#require wrappers, like Bootsnap's.

2.5.1 (20 October 2021)

• Restores support for namespaces that are not hashable. For example namespaces that override the hash method with a different arity as shown in #188.

2.5.0 (20 October 2021)

Breaking changes

• Requires Ruby 2.5.

• Deletes the long time deprecated preload API. Instead of:

  loader.preload("app/models/user.rb")

  just reference the constant on setup:

  loader.on_setup { User }

  If you want to eager load a namespace, use the constants API:

  loader.on_setup do
    Admin.constants(false).each { |cname| Admin.const_get(cname) }
  end

Bug fixes

• Fixes a bug in which a certain valid combination of overlapping trees managed by different loaders and ignored directories was mistakenly reported as having conflicting directories.

• Detects external namespaces defined with Module#autoload. If your project reopens a 3rd party namespace, Zeitwerk already detected it and did not consider the namespace to be managed by the loader (automatically descends, ignored for reloads, etc.). However, the loader did not do that if the namespace had only an autoload in the 3rd party code yet to be executed. Now it does.

Callbacks

... (truncated)

Commits

• 965b58e Version 2.5.4
• 40b80df Be resilient to Zeitwerk::NameError in on_unload callbacks
• e88c817 Fix typo in README
• 960dbdc Merge pull request #203 from Shopify/update-kernel-require-comment
• 689ab5d Update the Kernel#require comment about prepend
• e335dca Update documentation of the Kernel#require wrapper
• 902e9d0 Update documentation of the Kernel#require wrapper
• e4ae494 Version 2.5.3
• 8933b3b Revert "Store directories in $LOADED_FEATURES"
• 1ff6336 Update version
• 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)

[dependabot]

Superseded by #58.