Log message:
devel/bacon: update to 3.6.0

 - support for cpp (gcc & clang) with analyzer = "cpp" - Thanks \ 
@bryceberger
 - removal of the --path argument, replaced with --project and --watch \ 
(overrides the list of watched files).
   The path to the project can also be given as trailing argument as today. - \ 
Fix #274
 - the cargo_json analyzer can now be leveraged to export data from the cargo \ 
metadata Diagnostic and DiagnosticSpan structs - Fix #249

Log message:
devel/bacon: update to 3.5.0

    support for biome with analyzer = "biome"
    support for ruff with analyzer = "python_ruff"
    read bacon.toml in workspace/.config and package/.config - Fix #268
    read workspace.metadata.bacon and package.metadata.bacon config elements in \ 
Cargo.toml files - Fix #241
    fix locations export when launching bacon inside a rust workspace but with a \ 
non cargo tool

Log message:
devel/bacon: update to 3.4.0

 - new analyzer framework, make it possible for bacon to call more tools
 - Python Pytest analyzer
 - Analyzer for cargo check --message-format json-diagnostic-rendered-ansi - see #269
 - allow specifying scroll-pages action with a floating point number - Fix #264

Log message:
devel/bacon: update to 3.3.0

    bacon can now be launched without Cargo.toml file
    eslint analyzer (set analyzer = "eslint" in your job definition)
    Python Unittest analyzer (set analyzer = "python_unittest" in your \ 
job definition)
    fix Miri output seen as wrong when there's only warnings
    allow defining environment vars for all jobs - Thanks @joshka
    set env.CARGO_TERM_COLOR = "always" in default conf, thus making \ 
"--color", "always" useless in all cargo based job \ 
definitions - Thanks @joshka
    new ignore job parameter, accepts a list of glob patterns
    more lenient detection of warnings and errors due to 'miri run' not \ 
supporting --color - Fix #251

Log message:
devel/bacon: update to 3.2.0

v3.2.0 - 2024/11/04

 - allow defining default_watch and watch at global level, so that they apply to \ 
all jobs unless overridden.

v3.1.2 - 2024/10/29

 - "config loaded" message always automatically disappears after a few \ 
seconds

Log message:
devel/bacon: update to 3.1.1

Major feature: hot reload of config files

When a configuration file is modified, bacon automatically reloads its config. \ 
So you don't need to quit/relaunch when you add a new job, add a key-binding, \ 
change the allowed lints of clippy, etc. - Fix #29

Log message:
devel/bacon: update to 3.0.0

v3.0.0 - 2024/10/09
Major feature: nextest support

Hit n to launch the nextest job.

It's a default job, but you may define your own one by specifying analyzer = \ 
"nextest" in the job entry.

Internally, this is supported by a new analyzer framework which will allow \ 
easier analysis updates or addition of analysis for other tools (or languages).

Fix #196
Major feature: scope test job to failure

If you're running a test or nextest job and you want only the failing test to be \ 
retried, hit f.

If you want all tests to be executed again, hit esc.

Fix #214
Other features:
- grace period (by default 5ms) after a file event before the real launch of the \ 
command and during which other file events may be disregarded. Helps when saving \ 
a file changes several ones (eg backup then rename).
- new exports structure in configuration. New analysis export bound by default \ 
to ctrl-e. The old syntax defining locations export is still supported but won't \ 
appear in documentations anymore.
- recognize panic location in test - Fix #208
- lines to ignore can be specified as a set of regular expressions in a \ 
ignored_lines field either in the job or at the top of the prefs or bacon.toml - \ 
Fix #223
- toggle-backtrace accepts an optional level: toggle-backtrace(1) or \ 
toggle-backtrace(full) - Experimental - Fix #210
- configuration paths can be passed in BACON_PREFS and BACON_CONFIG env vars - \ 
Fix #76

Fixes:
    fix changing wrapping mode not always working in raw output mode - Fix #234

Log message:
devel/bacon: update to 2.21.0

v2.21.0 - 2024/09/14
With show_changes_count=true, you can see the number of file changes that \ 
occurred since last job start.

Major change: the on_change_strategy setting and a new default strategy

 - With on_change_strategy = "kill_then_restart", the current job is \ 
immediately killed and a new job restarted.
   This is the behavior that bacon had before this PR. It has the downside of \ 
never allowing any job to complete
   if you're always changing files and the job is just a little too long to \ 
finish between changes.
 - With on_change_strategy = "wait_then_restart" (which is the new \ 
default, so you can omit it), bacon waits
   for the job to finish before restarting it. This is probably much better when \ 
the jobs aren't instant and you
   want to continue changing files while it's computing.

The on_change_strategy can be defined in the global prefs, in the project \ 
settings, and even for a specific job.