dependabot[bot] opened a new pull request, #14056:
URL: https://github.com/apache/maven/pull/14056

   Bumps [ch.qos.logback:logback-classic](https://github.com/qos-ch/logback) 
from 1.6.6 to 1.6.7.
   <details>
   <summary>Release notes</summary>
   <p><em>Sourced from <a 
href="https://github.com/qos-ch/logback/releases";>ch.qos.logback:logback-classic's
 releases</a>.</em></p>
   <blockquote>
   <h2>Logback 1.6.7</h2>
   <h3>2026-11-14 Release of logback version 1.6.7</h3>
   <p>• The <code>scan</code> attribute of the 
<code>&lt;propertiesConfigurator&gt;</code> element, when
   set, now takes precedence over the <code>scan</code> attribute of the 
top-level
   <code>&lt;configuration&gt;</code> element, in both directions. With 
<code>scan=&quot;true&quot;</code>
   and scanning disabled or unset at the top level, the properties file
   is now actually monitored for changes. Previously, the file was
   added to the watch list but no task ever polled it. The scan period
   is taken from the <code>scanPeriod</code> attribute of the top-level
   <code>&lt;configuration&gt;</code> element. Conversely, with 
<code>scan=&quot;false&quot;</code> and
   <code>scan=&quot;true&quot;</code> at the top level, the properties file is 
no longer
   monitored. Moreover, when several <code>&lt;propertiesConfigurator 
scan=&quot;true&quot;&gt;</code>
   elements are present without top-level scanning, all
   the referenced files are now monitored. Previously, only the last
   one was.</p>
   <p>• Two new modules, <em>logback-core-kryo</em> and 
<em>logback-classic-kryo</em>,
   encode and decode logging events with the <a 
href="https://github.com/EsotericSoftware/kryo";>Kryo 5</a> serialization
   library. <a 
href="https://logback.qos.ch/manual/encoders.html#KryoEncoder";><code>KryoEncoder</code></a>
  writes <code>ILoggingEvent</code> instances into a
   <strong>compact binary stream</strong> and <code>KryoDecoder</code> reads 
them back.  The
   stream is framed so that the decoder can recover from torn or truncated
   writes, for example after a crash of the application. Both modules require
   Java 11 and ship with JPMS module descriptors, namely 
<code>ch.qos.logback.core.kryo</code>
   and <code>ch.qos.logback.classic.kryo</code>. See also the relevant 
documentation
   at  <a 
href="https://logback.qos.ch/manual/encoders.html#KryoEncoder";>KryoEncoder</a>.</p>
   <p>• Added the <code>toBooleanObject(String, Boolean)</code> and
   <code>toLopsidedBooleanObject</code> methods in 
<code>OptionHelper</code>.</p>
   </blockquote>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li><a 
href="https://github.com/qos-ch/logback/commit/8b97c2fe6dd0cfa298ed3c3dd4f500b942edc63a";><code>8b97c2f</code></a>
 prepare release 1.6.7</li>
   <li><a 
href="https://github.com/qos-ch/logback/commit/764b5c4613edb5c0920edfe7ff2404e778a0f0f1";><code>764b5c4</code></a>
 kryo: use stream version 0 when KryoEncoder is set to Vanilla</li>
   <li><a 
href="https://github.com/qos-ch/logback/commit/b29f465c3a3556a5432f768d37f0b3e127ebc076";><code>b29f465</code></a>
 kryo: remove V3 and V4 stream encodings, keep Vanilla and V5</li>
   <li><a 
href="https://github.com/qos-ch/logback/commit/d42c0129146630e7d769e9e8c2261bb68a3c04e5";><code>d42c012</code></a>
 add logback-core-kryo and logback-classic-kryo modules</li>
   <li><a 
href="https://github.com/qos-ch/logback/commit/069d51abcd1549d67f872fc4a315d585150f8087";><code>069d51a</code></a>
 remove dead code</li>
   <li><a 
href="https://github.com/qos-ch/logback/commit/271d89c82cad3b7071478610e2eea2013210bb6f";><code>271d89c</code></a>
 honor scan attribute of &lt;propertiesConfigurator&gt; in both directions</li>
   <li><a 
href="https://github.com/qos-ch/logback/commit/b01611fddfddd58ff03be4c7cbb37b6a4e7161ca";><code>b01611f</code></a>
 added a OptionHelper#toLopsidedBooleanObject</li>
   <li><a 
href="https://github.com/qos-ch/logback/commit/b1267ca05580340c42aca3985394de6e9093e501";><code>b1267ca</code></a>
 start work on 1.6.7-SNAPSHOT</li>
   <li>See full diff in <a 
href="https://github.com/qos-ch/logback/compare/v_1.6.6...v_1.6.7";>compare 
view</a></li>
   </ul>
   </details>
   <br />
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=ch.qos.logback:logback-classic&package-manager=maven&previous-version=1.6.6&new-version=1.6.7)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
   
   Dependabot will resolve any conflicts with this PR as long as you don't 
alter it yourself. You can also trigger a rebase manually by commenting 
`@dependabot rebase`.
   
   [//]: # (dependabot-automerge-start)
   [//]: # (dependabot-automerge-end)
   
   ---
   
   <details>
   <summary>Dependabot commands and options</summary>
   <br />
   
   You can trigger Dependabot actions by commenting on this PR:
   - `@dependabot rebase` will rebase this PR
   - `@dependabot recreate` will recreate this PR, overwriting any edits that 
have been made to it
   - `@dependabot show <dependency name> ignore conditions` will show all of 
the ignore conditions of the specified dependency
   - `@dependabot ignore this major version` will close this PR and stop 
Dependabot creating any more for this major version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this minor version` will close this PR and stop 
Dependabot creating any more for this minor version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this dependency` will close this PR and stop 
Dependabot creating any more for this dependency (unless you reopen the PR or 
upgrade to it yourself)
   
   
   </details>


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to