Upgrade listen: 3.2.0 → 3.2.1 (patch) #190
Closed
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 upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ listen (3.2.0 → 3.2.1) · Repo · Changelog
Commits
See the full diff on Github. The new version differs by 13 commits:
Remove gem which pulls in very old dependencies.Simplify travis configuration.Bump version.Merge pull request #471 from guard/reduce_multiple_fsevent_processesUse one `fsevent_watch` process per listener instead of one per dirBump RuboCop TargetRubyVersion to supported minimum.Remove unsupported check.Merge pull request #469 from nilbus/mutagenRemove unnecessary encoding doc string; UTF-8 is defaultAdd spec examples covering real mutagen filenamesIgnore mutagen sync temporary filesMerge pull request #466 from mattbrictson/chores/set-up-release-drafterMaintain release notes using GitHub ActionsRelease Notes
1.12.2 (from changelog)
1.12.1 (from changelog)
1.12.0 (from changelog)
1.11.3 (from changelog)
1.11.2 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 44 commits:
Bump VERSION to 1.12.2Update CHANGELOG for 1.12.2Replace st_table with simple cache and fix segfault after GC.compactRemove old references to ruby-1.9Bump VERSION to 1.12.1Do parallel builds in CI docker containersRespect MAKE environment variable for libtest buildBetter document enable/disable libffi switches in the READMEBump VERSION to 1.12.0Update CHANGELOG for version 1.12.0Update libffi to latest master branchMerge pull request #735 from larskanis/disallow-re-layoutWarn about Struct layout redefinition onlyNamespace all benchmarks since they are loaded into one processDisallow struct layout changesRequire "ffi/version" per defaultSet ruby-2.3.8 to allow_failures because of ffi unrelated errorUpdate rake to avoid warnings on ruby-2.7Update to rake-compiler-dock-1.0.0 to build ruby-2.7 binary gemsBump VERSION to 1.11.3Prepare CHANGELOG for 1.11.3Merge branch 'y-yagi-remove_taint_support'Remove taint supportUpdate CHANGELOG [ci skip]Update libffi to latest masterUpdate CHANGELOG for 1.11.2Bump VERSION to 1.11.2Merge pull request #722 from adam12/regenerate-freebsd12-typesFix library name mangling for non glibc Linux/UNIXMerge pull request #724 from ahorek/dragonflyadd typesidentify dragonflybsd as a platformRegenerated type conf for freebsd12 targetRemove MACOSX_DEPLOYMENT_TARGET that was targeting very old version 10.4Fix compiler warnings raised by ruby-2.7Add ruby-2.6 to Appveyor CIDescribe "types_conf" so that it's shown in "rake -T"Update platform x86_64-linux on Ubuntu-18.04Sort all types.conf files, so that changes are more visibleMerge pull request #711 from wonda-tea-coffee/fix-bigdecimal-newFix BigDecimal.newMerge pull request #703 from jcn/patch-1Update ffi.gemspec with correct homepage URLAdd a notice about yanked ffi-1.11.0Commits
See the full diff on Github. The new version differs by 7 commits:
Fix formatting.Bump version.Remove rbx-3.Limit changing auto close behavior off to just JRuby. This limits risk of MRIFixes #91. Make IO resources not autoclose.allow stopping a notifier from within an event callbackUpdate documentation regarding resource limits. Fixes #61.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