Update dependency guard to '~> 2.19', '>= 2.19.1' #3

mend-5034428 · 2024-10-16T17:48:07Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
guard (source, changelog)	`'~> 2.4'` -> `'~> 2.19', '>= 2.19.1'`

Release Notes

guard/guard (guard)

`v2.19.1`

Compare Source

🏠 Housekeeping

Get rid of compatibility warnings under Ruby 3.4. (#998) @kewlar
Provide a 'Changelog' link on rubygems.org/gems/guard (#999) @mark-young-atg

Bump dependency on pry to >= 0.13.0 (#974) @larouxn

`v2.17.0`

Compare Source

✨ New Features

Refactor pry_wrapper.rb to be XDG compliant (#962) @quintrino
Add Ruby 2.7.3 and 3.0.1 to the test matrix (#969) @rymai
Bring compatibility with Ruby 3 explicit keyword arguments (#969) @rymai

`v2.16.2`

Compare Source

🐛 Bug Fixes

Fix support for Pry 0.13 (#958) @rymai

`v2.16.1`

Compare Source

🐛 Bug Fixes

Don't swallow evaluator error by handling non-existant listener & interactor (#939) @rymai

🏠 Housekeeping

Add Codecov (#944) @rymai
Maintain release notes using GitHub Actions (#941) @rymai

`v2.16.0`

Compare Source

New feature

#938 Add support for guardfile.rb.

`v2.15.1`

Compare Source

Bugfixes

#930 Ensure Guard calls #stop even if an exception is raised.

Tests & CI

#914 Add a simplecov filter for the /spec folder.
#926 Test against Ruby 2.4.6, 2.5.5, 2.6.2, jruby-9.1.17.0, jruby-9.2.6.0, rbx-3.107.
#928 Fix Ruby 2.6 compatibility by stubbing Pathname instead of IO.read in spec.
#933 Remove codeclimate-test-reporter from Gemfile.

Other

#919 Add a "Reviewed by Hound" badge.
#925 Fix YARD annotation.
#927 Drop outdated badge for Gemnasium.

`v2.15.0`

Compare Source

New feature

#889 Add #== method for Guard::Watcher.

Bugfixes

#893 Fix rspec warning message.
#894 Fix rspec random test failure.
#916 Fix Pry 0.12.0 deprecation warnings.

Improvements

#872 Improve Plugin type checking.
#904 Replace deprecated Dir.exists? with Dir.exist?.

Tests & CI

#899 Test against latest rubies.
#900 Force rubocop to match HoundCI's rubocop version.
#911 Apply style guide to the specs.

`v2.14.2`

Compare Source

Bugfix

#892 Fix a bug that was preventing logger options from the Guardfile from being correctly set

Improvements

#871 Add aliasing section inside tired-of-typing bundle exec
#879 Run core with same Ruby version as it was started with
#880 Build badge now shows master branch status
#881 Update CI matrix to include latest release of JRuby
#882 Fix lumberjack version runtime dependency to ">= 1.0.12", "< 2.0"
#883 Run CI against Ruby 2.2.8, 2.3.5, and 2.4.2
#886 Improve headings in the README
#890 Add links to the wiki in CONTRIBUTING.md

`v2.14.1`

Compare Source

Bugfixes

#860 Fix default type on listen_to method_option for newer versions of Thor
#861 guard -c nows clears window buffer on OSX

Improvements

#852 Rework logging and UI configuration
#864 Execute the codeclimate-test-reporter bin as a separate CI step
#865 Test against Ruby 2.2.6, 2.3.3, and 2.4.0

`v2.14.0`

Compare Source

Bugfixes

#817 Correct pause state message [fix #816]
#791 Guard now fails with the 1 exit code when plugin is not available

Improvements

#835 allow regexp group names like /(?<name>.*).rb/ (so you can use m[:name] instead of m[1])
#835 allows custom matcher objects in watches (so you can pass matchers instead of a regexp - see Matcher class)
#835 better/smarter handling of Pathnames in watch/matches/rules
#798 (ignore_plugin_templates) dont reload when plugin templates change
#785 also trace spawn() calls when debugging

`v2.13.0`

Compare Source

Bugfixes

#782, #783 - rework bundler/rubygems handling by guard startup scripts

NOTE: please report issues if you're experiencing problems after theses changes

`v2.12.9`

Compare Source

Bugfixes

#778 - properly detect used plugins when name is a symbol

`v2.12.8`

Compare Source

Bugtfixes

#775 - don't load Bundler when RubyGems RUBYGEMS_GEMDEPS is set

Improvements

remove huge guard.png image from the gem itself

`v2.12.7`

Compare Source

Changes

#772 - support both Listen 2.x and 3.x versions

`v2.12.6`

Compare Source

Bugfixes

#759 - avoid running interactive (Pry) on JRuby (use '-i' option as workaround - see issue and refs)
#755 - restart guard when it's symlinked (proper Guardfile detection)

Improvements

#733 - commented example in Guardfile for directory checking

`v2.12.5`

Compare Source

Improvements

#752 - detect existing/used guards in Guardfiles more accurately

`v2.12.4`

Compare Source

Bugfixes

#749 - fix broken auto-reloading

`v2.12.3`

Compare Source

Bugfixes

quickfix for #748 - fix so spawn() works on Windows

`v2.12.2`

Compare Source

Bugfixes

#743 - fix Gemfile handling
#744 - fix broken Ctrl-C handling

`v2.12.1`

Compare Source

Bugfix

#740 - Allow guard to work globally without bundler

`v2.12.0`

Compare Source

Bugfixes

#728 - fixed incompatibility (second parameter to notify() should be optional)

Improvements

#735 - Guard reloads automatically after config change

`v2.11.1`

Compare Source

Bugfixes

#715 - allow minitest to work from Rakefile (when guard-minitest is used)

`v2.11.0`

Compare Source

Bugfixes

#710 - regression fixed - clearing :on should work again
#714 - fix missing require needed for Guard::Jasmine to work in cli mode
#621 - shows full help options for default start Guard command

Maintenance

extract notifiers into notiffany gem
extract sheller into shellany gem

`v2.10.5`

Compare Source

Bugfixes

#705 - fixed regression: scope() with singular arguments(:group, :plugin) works again

Improvements

#703 - split README into respective wiki entries

`v2.10.4`

Compare Source

Bugfixes

#697 - fixed regression where running 'scope' from Interactor crashed (and added missing specs to prevent this)

`v2.10.3`

Compare Source

Bugfixes

#690 - fixed regression - once again allows multiple ignore() statements work
don't crash when non-existing groups are specified in scope

Important changes

#688 - the internal Reevaluator plugin has been dropped for important reason: enormous maintenance costs, incompability with directories option, lots of unexpected side effects causing obscure bugs (see issue for easy workaround or file a feature request if you absolutely need this feature again)

Related issue: https://github.com/guard/guard/issues/696

`v2.10.2`

Compare Source

Bugfixes

avoid treating Guard::Compat as a valid plugin, so that guard init can work

`v2.10.1`

Compare Source

Bugfix

#686 - fixed ignore DSL keyword handling (regression since 2.9.2)

`v2.10.0`

Compare Source

Bugfixes

#684 - restored the accidentally refactored-out Guard.options + deprecate it
#685 - also includes a workaround to keep Guard.options[:clear] = true working

Improvements

new clearing DSL keyword, which works exactly like the -c option (and replaces the ugly hack previously mentioned in the README)
properly document the directories method in README (+mention important workarounds)

`v2.9.2`

Compare Source

Bugfixes

#682 - regression - callbacks were broken after refactoring (new specs were added)

`v2.9.1`

Compare Source

Bugfixes

#680 regression - notification didn't work (unless notifiers were set manually - because autodetect was never called)

`v2.9.0`

Compare Source

Improvements

#676 New directories DSL option allows configuring which directories should be watched by Listen (the catch is: Guard has to be restarted if this is changed - reloading currently won't work)

Known issues

although Guard is currently being very cautiously refactored, some issues or side-effects might have slipped between the automatic and manual tests - so be sure to report any issue and regressions

`v2.8.2`

Compare Source

Bugfixes

-#664 - properly call stop() when Guard exits normally

`v2.8.1`

Compare Source

Bugfixes

fix screen clearing ('-c' option) [Finally!]
fix debug mode ('-d' option) to show what's executed (notably: programs run by plugins)

Improvements

reimplement command execution tracing (debug mode)
Guard now can trace every command executed in other plugins

Development

Any module or class method can be traced

Some examples to play around with in your ~/.guard.rb file:

tracer = Guard::Internals::Tracing
ui = Guard::UI

unless $traced
  tracer.trace(Guard, :add_plugin) do |*args|
    ui.warning "* Plugin added: #{args.first.inspect}"
  end

  tracer.trace(Guard::Terminal, :clear) do |*args|
    ui.warning "* Clearing screen in 4 seconds!"
    (1..4).to_a.reverse.each { |i| ui.warning ">> #{i}..."; sleep 1 }
  end

  tracer.trace(Guard, :async_queue_add) do |*args|
    ui.warning "* Event: #{args.inspect}"
  end
  $traced = true
end

`v2.8.0`

Compare Source

Important notes

This is just a release to deprecate the extremely problematic ::Guard::Guard class, which was deprecated over a year ago (Guard 2.0).

Suggested usage in bundler:

gem 'guard', '~> 2.8'

(Since there are no plans to maintain 2.7).

Compatibility

The deprecated file will be removed in 2.8.1 (or later)!

This does not break semver, because the deprecation was introduced in 1.x:

= 1.8.1 -> deprecated for the first time
= 2.0.0 -> deprecations hidden by default (without --show-deprecations)
= 2.7.3 -> last version without deprecation
= 2.8.0 -> deprecation (this version)
>= 2.8.1 -> (upcoming) will break apps relying on deprecated classes/methods
2.9.x -> (upcoming) - will be compatible with 2.x, but will have features from 3.x
3.x -> (upcoming) - incompatible with 2.x

So, if you can't upgrade yet (even though it should be trivial), you can use:

gem 'guard', '~> 2.7.3'

Upgrade details

Upgrading to Guard 2.0

`v2.7.3`

Compare Source

Important notes

This version (v2.7.3) is the last one planned before a major deprecation in 2.8.0.

Since Guard 2.7.x will likely no longer be maintained.

So, you are encouraged to switch to 2.8 as soon as it's available:

gem 'guard', '~> 2.8'

Bugfixes

#659 regression: prevent 'guard init' from contantly adding existing entries

Development

refresh rspec config + update files to prepare for major refactoring

`v2.7.2`

Compare Source

Bugfixes

#655 actually make screen clearing useful instead of clearing the last task's output
fix the 'guard list' so it correctly shows which plugins aren't in the Guardfile
make the reevaluator plugin "permanent", even on eval errors

`v2.7.1`

Compare Source

Bugfixes:

#655 fix broken screen clearing ('-c' option)
#519 fix regression: scope handling quickfixes (needs more work)
fix regression: prevent guard list from requiring an existing Guardfile

Improvements:

silently deprecate unused accessors like lock & running
add basic acceptance tests: show and init (so bugs can be reproduced)
use Gem.win_platform? where possible

Development:

fix occasionally failing specs
enable stable installed guard gem to be used in dev (USE_INSTALLED_GUARD=1)
prevent specs from touching filesystem (by stubbing and mocking)
lots of refactoring allow for major architecture changes
less confusing var names, e.g. "guard"->"plugin", "paths"->"match_result"
remove unused fixtures
halt on failures when running rspec+cucumber+rubocop

Development (cucumber acceptance tests):

add default cucumber.yml
add Cucumber specs using in-process Aruba
add interactive Cucumber test (using @spawn) for 'start' and correctly firing plugins
add and use guard-cucumber

Development (travis/rubocop):

ignore JRuby failures on Travis (because of complex acceptance tests)
misc fixes for JRuby
and rubocop to Rake to avoid forgetting about houndci
add rubocop_todo.yml to silence irrelevant issues (e.g. in Rakefile)

`v2.7.0`

Compare Source

Important notes

(#634) the -w option now correctly allows monitoring only chosen
directories - great for large projects (previous behavior is consider a bug)
guard handles switching between tasks and interaction very differently now,
so if by any chance you experience lockups or errors, be sure to report them
Guard exposes lots of public methods and accessors for internal use and were
never meant as a public API - if you have plugins or projects relying on such
interfaces or behavior which changed (or might), feel free to create issues
and PRs
if you have major feature requests for the next major version of Guard,
please submit feature requests, since work may begin soon

Bug fixes

#614 Fix failing bug when running tasks with scope.
#598 Ensure we load Guard::Plugin as soon as possible.
#611 Configure the scope according to the CLI options on re-evaluation of Guardfile.
#617 Support Tmux 1.6 and older
#634 Fix bug where paths were relative to watchdirs instead of current working directory

New features

#603 New :first_match option to stop after the first watcher that returns a valid result.

Improvements

#595 Guard is now synchronous.
#602 Massive internal cleanup.
#612 Allow tmux notifier to receive custom types.
#613 Update .travis.yml testing against last stable Ruby version (2.1.2).
#632 remove deprecated growl_notify notifier
#609 Don't warn when using RUBYGEMS_GEMDEPS instead of Bundler
#640 guard reevaluation is handle by "internal" plugin
deprecate rubygem < 1.8.0

`v2.6.1`

Compare Source

Bug fixes

#583 Fixes tmux notifier when display_on_all_clients is true.
#536 Is greatly mitigated by avoiding Pry restarts when unwatched files change
#571 Respond to signals using thread (avoiding Lumberjack and Listen lock problems in Ruby 2.0.0)
#582 Prevent Interrupt from resulting in plugins being fired
Move rspec options to .rspec (since it's overridable with custom .rspec-local)

`v2.6.0`

Compare Source

@docwhat is in the place!

Bug fixes

#539 & #559 Fixes (or not, see #563) #turn_on and #turn_off for tmux notifier.
#568 Fix Guardfile re-evaluation.

Improvements

#560 Ignore tags file.
#561 Add docs badge to README.
#564 RSpec 3.0 syntax.
#565 Prevent user's .guard.rb from breaking tests.
#567 Delete specifying RSpec dependency twice. Also move all development dependencies to the Gemfile.

`v2.5.1`

Compare Source

Bug fix

#557 Set listen_on at false by default.

`v2.5.0`

Compare Source

New feature

#555 Add support for network events in Listen 2.5.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

If you want to rebase/retry this PR, check this box

mend-5034428 bot force-pushed the whitesource-remediate/guard-2.x branch from 9f60c5d to 96c7841 Compare October 28, 2024 21:35

mend-5034428 bot changed the title ~~Update dependency guard to '~> 2.18', '>= 2.18.1'~~ Update dependency guard to '~> 2.19' Oct 28, 2024

Update dependency guard to '~> 2.19', '>= 2.19.1'

8e0f029

mend-5034428 bot force-pushed the whitesource-remediate/guard-2.x branch from 96c7841 to 8e0f029 Compare January 3, 2025 04:12

mend-5034428 bot changed the title ~~Update dependency guard to '~> 2.19'~~ Update dependency guard to '~> 2.19', '>= 2.19.1' Jan 3, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update dependency guard to '~> 2.19', '>= 2.19.1' #3

Update dependency guard to '~> 2.19', '>= 2.19.1' #3

mend-5034428 bot commented Oct 16, 2024 •

edited

Loading

Update dependency guard to '~> 2.19', '>= 2.19.1' #3

Are you sure you want to change the base?

Update dependency guard to '~> 2.19', '>= 2.19.1' #3

Conversation

mend-5034428 bot commented Oct 16, 2024 • edited Loading

Release Notes

🏠 Housekeeping

What's Changed

✨ New Features

🐛 Bug Fixes

🐛 Bug Fixes

🏠 Housekeeping

New feature

Bugfixes

Tests & CI

Other

New feature

Bugfixes

Improvements

Tests & CI

Bugfix

Improvements

Bugfixes

Improvements

Bugfixes

Improvements

Bugfixes

Bugfixes

Bugtfixes

Improvements

Changes

Bugfixes

Improvements

Improvements

Bugfixes

Bugfixes

Bugfixes

Bugfix

Bugfixes

Improvements

Bugfixes

Bugfixes

Maintenance

Bugfixes

Improvements

Bugfixes

Bugfixes

Important changes

Bugfixes

Bugfix

Bugfixes

Improvements

Bugfixes

Bugfixes

Improvements

Known issues

Bugfixes

Bugfixes

Improvements

Development

Important notes

Compatibility

Upgrade details

Important notes

Bugfixes

Development

Bugfixes

Bugfixes:

Improvements:

Development:

Development (cucumber acceptance tests):

Development (travis/rubocop):

Important notes

Bug fixes

New features

Improvements

Bug fixes

Bug fixes

Improvements

Bug fix

mend-5034428 bot commented Oct 16, 2024 •

edited

Loading