Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build(deps): Bump zeitwerk from 2.6.13 to 2.6.14 #541

Closed
wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github May 14, 2024

Bumps zeitwerk from 2.6.13 to 2.6.14.

Changelog

Sourced from zeitwerk's changelog.

2.6.14 (14 May 2024)

  • Implements Zeitwerk::Loader#all_expected_cpaths, which returns a hash that maps the absolute paths of the files and directories managed by the receiver to their corresponding expected constant paths.

    Please, check its documentation for further details.

Commits
  • 4e67937 Ready for 2.6.14
  • 34c967c Restore the original Zeitwerk::NameError message
  • 30f80cc Documentation tweaks
  • 8d0b8a5 Document Zeitwerk::Loader#all_expected_cpaths
  • 20ac160 Exclude macOS/2.5 from CI matrix
  • 9d4d7a9 Standardize breadth-first loops
  • 7baa17a Let the ls helper yield the file type too
  • 57106d5 Implements Zeitwerk::Loader#all_expected_paths
  • 949faba Fix indentation
  • 36e44fc Add a test for Zeitwerk::NameError
  • Additional commits viewable in compare view

Dependabot compatibility score

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @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)

Bumps [zeitwerk](https://github.com/fxn/zeitwerk) from 2.6.13 to 2.6.14.
- [Changelog](https://github.com/fxn/zeitwerk/blob/main/CHANGELOG.md)
- [Commits](fxn/zeitwerk@v2.6.13...v2.6.14)

---
updated-dependencies:
- dependency-name: zeitwerk
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file ruby Pull requests that update Ruby code labels May 14, 2024
Copy link
Contributor Author

dependabot bot commented on behalf of github May 21, 2024

Looks like zeitwerk is up-to-date now, so this is no longer needed.

@dependabot dependabot bot closed this May 21, 2024
@dependabot dependabot bot deleted the dependabot/bundler/zeitwerk-2.6.14 branch May 21, 2024 09:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file ruby Pull requests that update Ruby code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants