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

[ruby] Update bootsnap 1.13.0 → 1.17.0 (minor) #2203

Merged
merged 1 commit into from
Dec 18, 2023

Conversation

depfu[bot]
Copy link
Contributor

@depfu depfu bot commented Dec 18, 2023

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ bootsnap (1.13.0 → 1.17.0) · Repo · Changelog

Release Notes

1.17.0 (from changelog)

  • Ensure $LOAD_PATH.dup is Ractor shareable to fix an conflict with did_you_mean.
  • Allow to ignore directories using absolute paths.
  • Support YAML and JSON CompileCache on TruffleRuby.
  • Support LoadPathCache on TruffleRuby.

1.16.0 (from changelog)

  • Use RbConfig::CONFIG["rubylibdir"] instead of RbConfig::CONFIG["libdir"] to check for stdlib files. See #431.
  • Fix the cached version of YAML.load_file being slightly more permissive than the default Psych one. See #434. Date and Time values are now properly rejected, as well as aliases. If this causes a regression in your application, it is recommended to load trusted YAML files with YAML.unsafe_load_file.

1.15.0 (from changelog)

  • Add a readonly mode, for environments in which the updated cache wouldn't be persisted. See #428 and #423.

1.14.0 (from changelog)

  • Require Ruby 2.6.
  • Add a way to skip directories during load path scanning. If you have large non-ruby directories in the middle of your load path, it can severly slow down scanning. Typically this is a problem with node_modules. See #277.
  • Fix Bootsnap.unload_cache!, it simply wouldn't work at all becaue of a merge mistake. See #421.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 50 commits:


Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu cancel merge
Cancels automatic merging of this PR
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

@depfu depfu bot added the depfu label Dec 18, 2023
Copy link

codeclimate bot commented Dec 18, 2023

Code Climate has analyzed commit f629a88 and detected 0 issues on this pull request.

View more on Code Climate.

@adrianthedev adrianthedev merged commit 790aa4d into main Dec 18, 2023
14 of 17 checks passed
@adrianthedev adrianthedev deleted the depfu/update/bootsnap-1.17.0 branch December 18, 2023 21:39
Copy link
Contributor

This PR has been merged into main. The functionality will be available in the next release.

Please check the release guide for more information.

@Paul-Bob Paul-Bob added the Chore label Dec 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants