Update guard 2.19.0 → 2.19.1 (patch) #710
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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?
✳️ guard (2.19.0 → 2.19.1) · Repo · Changelog
Release Notes
2.19.1
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 3 commits:
Bump VERSION to 2.19.1
Chore: get rid of compatibility warnings under Ruby 3.4. (#998)
Provide a 'Changelog' link on rubygems.org/gems/guard (#999)
Commits
See the full diff on Github. The new version differs by 16 commits:
Bump VERSION to 1.17.1
Add release notes for ffi-1.17.1
Fix `FFI::DataConverter` non-generic usage
Merge pull request #1133 from larskanis/ruby-3.4
CI: Add ruby-3.4 to test matrix
Add ruby-3.4 native gem
Merge pull request #1125 from voxik/closures-vs-fork-on-ppc64le-s390x-2
Some platforms don't support `fork()`
Ensure GC-ing closures before fork
Merge pull request #1123 from larskanis/fix-va_start
Fix warning about va_start parameter in libtest raised by clang
Remove code comment, since the issue is resolved
Merge pull request #1117 from KJTsanaktsidis/ktsanaktsidis/restart_cbthread_after_fork
Restart async callback dispatcher thread after fork
Merge pull request #1092 from larskanis/ci-mswin
CI: Add a CI run on mswin build tools
🆕 logger (added, 1.6.4)
🆕 ostruct (added, 0.6.1)
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