dependabot[bot] opened a new pull request, #76055: URL: https://github.com/apache/airflow/pull/76055
Bumps the uv-dependency-updates group with 3 updates in the /dev/breeze directory: [filelock](https://github.com/tox-dev/py-filelock), [prek](https://github.com/j178/prek) and [boto3](https://github.com/boto/boto3). Updates `filelock` from 4.2.0 to 4.2.4 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/tox-dev/py-filelock/releases";>filelock's releases</a>.</em></p> <blockquote> <h2>4.2.4</h2> <p><a href="https://pypi.org/project/filelock/4.2.4/";>🐍 PyPI release</a></p> <p><a href="https://github.com/tox-dev/filelock/compare/4.2.3...4.2.4";>📜 Full Changelog</a></p> <h2>4.2.3</h2> <p><!-- raw HTML omitted --><!-- raw HTML omitted --></p> <h3>Bug fixes</h3> <ul> <li>Creating a lock on a Python 3.15 interpreter without <code>types.LazyImportType</code> no longer triggers <code>AttributeError</code> at exit. <a href="https://redirect.github.com/tox-dev/filelock/pull/861";>#861</a> by <a href="https://github.com/gaborbernat";><code>@gaborbernat</code></a>.</li> <li>Handle <code>EFTYPE</code> when a no-follow open refuses a symlink in a soft reader/writer lock's protocol tree, so heartbeat reports lost ownership rather than a transient refresh error. <a href="https://redirect.github.com/tox-dev/filelock/pull/859";>#859</a> by <a href="https://github.com/edsonsims";><code>@edsonsims</code></a>.</li> </ul> <h3>New Contributors</h3> <ul> <li><a href="https://github.com/edsonsims";><code>@edsonsims</code></a> made their first contribution in <a href="https://redirect.github.com/tox-dev/filelock/pull/859";>#859</a></li> </ul> <p><a href="https://pypi.org/project/filelock/4.2.3/";>🐍 PyPI release</a></p> <p><a href="https://github.com/tox-dev/filelock/compare/4.2.2...4.2.3";>📜 Full Changelog</a></p> <h2>4.2.2</h2> <p><!-- raw HTML omitted --><!-- raw HTML omitted --></p> <h3>Bug fixes</h3> <ul> <li>Fix a lock on a relative path that stayed held after a later <code>with lock:</code> ended, when an earlier <code>acquire()</code> had failed because the working directory no longer exists. That call still raises <code>FileNotFoundError</code>, and it now leaves the lock's hold count unchanged. <a href="https://redirect.github.com/tox-dev/filelock/pull/856";>#856</a> by <a href="https://github.com/spicysharkco";><code>@spicysharkco</code></a>.</li> </ul> <h3>New Contributors</h3> <ul> <li><a href="https://github.com/spicysharkco";><code>@spicysharkco</code></a> made their first contribution in <a href="https://redirect.github.com/tox-dev/filelock/pull/856";>#856</a></li> </ul> <p><a href="https://pypi.org/project/filelock/4.2.2/";>🐍 PyPI release</a></p> <p><a href="https://github.com/tox-dev/filelock/compare/4.2.1...4.2.2";>📜 Full Changelog</a></p> <h2>4.2.1</h2> <p><!-- raw HTML omitted --><!-- raw HTML omitted --></p> <h3>Bug fixes</h3> <ul> <li>On a singleton wrapper, <code>AsyncReadWriteLock.close()</code> and <code>AsyncSoftReadWriteLock.close()</code> end only the holds that tasks acquired through that wrapper. A reader that arrives during <code>close()</code> gets the closed error instead of joining the ending hold. After synchronous code closes or force-releases the shared lock, the wrappers refuse to admit readers into the ended hold, and <code>close()</code> on such a wrapper returns. Closing one wrapper no longer ends a task's nested hold taken through another wrapper on the same path. <a href="https://redirect.github.com/tox-dev/filelock/pull/832";>#832</a> by <a href="https://github.com/gaborbernat";><code>@gaborbernat</code></a>.</li> <li><code>ReadWriteLock</code> locks again after a <code>release()</code> that an exception from a signal handler interrupted. The async read-write wrappers stop admitting readers into such a level. The async read-write locks forget a hold whose backend release failed after the backend let go, and they free the memory of each acquire that times out or is canceled. <code>AsyncFileLock</code> returns from <code>release()</code> after a few hundred acquires gave up behind a waiting one. An exception from a signal handler delivered while an <code>AsyncFileLock</code> call joins its queue no longer blocks every later call on that lock. <a href="https://redirect.github.com/tox-dev/filelock/pull/833";>#833</a> by <a href="https://github.com/gaborbernat";><code>@gaborbernat</code></a>.</li> <li>Fix <code>ReadWriteLock</code> acting on <code>-journal</code>, <code>-wal</code> or <code>-shm</code> files another process puts beside its database: a write could land in another file, a reader could get in beside a writer, and an acquire could fail. SQLite now opens the database by name only in a directory no other account can write, and through a private hard link elsewhere. On Windows the directory's access control list decides. Where hard links are unavailable, keep the database in a directory other accounts cannot write, such as one under <code>%LOCALAPPDATA%</code>. The lock removes link directories through a checked descriptor rather than by name, reads a link directory's name only when the locking account owns it, and leaves alone a directory with other content renamed onto a link directory's name. A database whose schema takes more than a few kilobytes to load raises <code>ValueError</code> instead of running past the acquire timeout. <a href="https://redirect.githu b.com/tox-dev/filelock/pull/834">#834</a> by <a href="https://github.com/gaborbernat";><code>@gaborbernat</code></a>.</li> <li>Fix five bugs in opening the lock file. <code>UnixFileLock</code> no longer truncates a file it did not create, such as one renamed to the lock path, and no longer applies <code>mode</code> to it. An <code>on_acquired</code> hook that writes holder metadata now truncates the file itself. A lease (Linux) or an oplock (Windows) on the lock file or a soft lock's marker no longer holds <code>acquire()</code> past its <code>timeout</code> or <code>blocking=False</code>, and an oplock no longer holds <code>release()</code>; <code>ReadWriteLock</code> on Windows waits for its <code>timeout</code> and raises <code>Timeout</code>. On Windows, a <code>mode</code> without group and other bits, such as <code>0o600</code>, now creates the lock file with an owner-only permission list; the <code>ReadWriteLock</code> database gets the same. The soft locks' writability check no longer follows a symlink swapped in at the lock path. On a filesystem without <code>flock</code>, a contender from an other account now waits on a marker it cannot write instead of raising <code>PermissionError</code>. <a href="https://redirect.github.com/tox-dev/filelock/pull/835";>#835</a> by <a href="https://github.com/gaborbernat";><code>@gaborbernat</code></a>.</li> <li>Fix <code>SoftFileLock</code>, <code>MarkerSoftFileLock</code> and <code>SoftFileLease</code> removing a live holder's marker in three cases: the holder and the contender run in Linux time namespaces with different boottime offsets; only one of them can read the boot id; a process other than the owner rewrote the marker. Soft markers no longer carry group or other write bits. A process name containing a carriage return or another line separator no longer makes the stale check raise <code>ValueError</code>. When <code>/proc/self/ns/time</code> exists but cannot be read, the stale check no longer compares start times and keeps the marker. <a href="https://redirect.github.com/tox-dev/filelock/pull/836";>#836</a> by <a href="https://github.com/gaborbernat";><code>@gaborbernat</code></a>.</li> <li>The async read-write locks record their hold under a task owner, so synchronous code on the executor thread that took the hold can no longer re-enter or release it. <code>AsyncSoftReadWriteLock</code> gives back one level on release, so synchronous readers of a shared singleton keep theirs. <code>SoftReadWriteLock</code> tracks read levels per thread: <code>release()</code> from a thread that holds none raises <code>RuntimeError</code>. After its heartbeat recorded a lost hold, it refuses new acquires until that hold is released. <a href="https://redirect.github.com/tox-dev/filelock/pull/838";>#838</a> by <a href="https://github.com/gaborbernat";><code>@gaborbernat</code></a>.</li> <li><code>StrictSoftFileLock</code> creates <code><path>.filelock</code> and its <code>claims</code> directory with the lock's <code>mode</code> and sets the sticky bit (a directory flag that lets only a file's owner remove it) on both. On the next acquisition it narrows a directory it owns that an earlier release created wider; it leaves a directory of another account as it is, so remove such leftovers by hand. It reaches <code>claims</code> through a descriptor opened without following symlinks; on Windows it holds both directories open and refuses a junction (a directory that points at another directory). Under a sticky parent such as <code>/tmp</code> it refuses a coordination directory of another account, as <code>SoftReadWriteLock</code> does for <code><path>.rw</code>. One read grace now covers a whole claim scan, a failed claim cleanup no longer leaves the sentinel descriptor open, and a non-regular node at a sentinel private-record name raises <code>SoftFileLo ckProtocolError</code>. On Windows, contenders read claims without blocking their owner's unlink. <a href="https://redirect.github.com/tox-dev/filelock/pull/839";>#839</a> by <a href="https://github.com/gaborbernat";><code>@gaborbernat</code></a>.</li> <li>Fix a lock reporting a hold the OS had dropped after a signal handler raised during <code>acquire</code> or <code>release</code>. A release that a signal handler cuts short after it has started now completes before the error propagates. A handler that acquires the lock its own thread is releasing now gets <code>RuntimeError</code> instead of a hold that stays held. The singleton cache no longer hands out an <code>is_singleton=True</code> lock or a <code>ReadWriteLock</code> whose finalizer is running, which released the new holder's lock. A signal during <code>os.fork()</code> no longer leaves the other threads blocked in their next lock call, and a fork from another thread no longer waits for a <code>ReadWriteLock</code> acquire on a busy database. <a href="https://redirect.github.com/tox-dev/filelock/pull/840";>#840</a> by <a href="https://github.com/gaborbernat";><code>@gaborbernat</code></a>.</li> <li>Fix a lock on a relative path locking a file in the directory the process changed to while the lock waited, and leaving its marker behind on release after such a change. The path resolved when an acquisition starts stays in use until the hold ends. An <code>is_singleton=True</code> lookup no longer returns a cached lock whose relative path now resolves to another file; a held lock still matches the file it holds. A rename of the lock's directory during a hold no longer leaves the marker behind or reports a false lease compromise, and a waiter no longer creates a second lock file in a directory that was renamed away. <a href="https://redirect.github.com/tox-dev/filelock/pull/841";>#841</a> by <a href="https://github.com/gaborbernat";><code>@gaborbernat</code></a>.</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/tox-dev/filelock/blob/main/docs/changelog.rst";>filelock's changelog</a>.</em></p> <blockquote> <p>########### Changelog ###########</p> <p>.. towncrier-draft-entries:: Unreleased</p> <p>.. towncrier release notes start</p> <p>.. _release-4-2-4:</p> <hr /> <p>4.2.4 (2026-10-19)</p> <hr /> <p>.. _release-4-2-3:</p> <hr /> <p>4.2.3 (2026-10-19)</p> <hr /> <p>.. _release-4-2-3-fixed:</p> <h1>Fixed</h1> <ul> <li>Creating a lock on a Python 3.15 interpreter without <code>types.LazyImportType</code> no longer triggers <code>AttributeError</code> at exit. :pr:<code>861</code> - by :user:<code>gaborbernat</code>.</li> <li>Handle <code>EFTYPE</code> when a no-follow open refuses a symlink in a soft reader/writer lock's protocol tree, so heartbeat reports lost ownership rather than a transient refresh error. :pr:<code>859</code> - by :user:<code>edsonsims</code>.</li> </ul> <p>.. _release-4-2-2:</p> <hr /> <p>4.2.2 (2026-10-18)</p> <hr /> <p>.. _release-4-2-2-fixed:</p> <h1>Fixed</h1> <ul> <li>Fix a lock on a relative path that stayed held after a later <code>with lock:</code> ended, when an earlier <code>acquire()</code> had failed because the working directory no longer exists. That call still raises :class:<code>FileNotFoundError</code>, and it now leaves the lock's hold count unchanged. :pr:<code>856</code> - by :user:<code>spicysharkco</code>.</li> </ul> <p>.. _release-4-2-1:</p> <hr /> <p>4.2.1 (2026-10-17)</p> <hr /> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/tox-dev/filelock/commit/22f0776dd499690d71d2e6d2f95e1662a76db75d";><code>22f0776</code></a> Release 4.2.4</li> <li><a href="https://github.com/tox-dev/filelock/commit/9d278ed268586d561f903aebc693908b99329a98";><code>9d278ed</code></a> Document GitHub Release note cleanup (<a href="https://redirect.github.com/tox-dev/py-filelock/issues/863";>#863</a>)</li> <li><a href="https://github.com/tox-dev/filelock/commit/3c337980bffcb15a4a3aa4c5f61a652b31181822";><code>3c33798</code></a> 🐛 fix(release): trim GitHub release notes (<a href="https://redirect.github.com/tox-dev/py-filelock/issues/862";>#862</a>)</li> <li><a href="https://github.com/tox-dev/filelock/commit/e7379240003b1c5a990b012624a5cb5e55f72b9d";><code>e737924</code></a> Release 4.2.3</li> <li><a href="https://github.com/tox-dev/filelock/commit/84dc80cf65493c8232033ecff41d1edac38c6808";><code>84dc80c</code></a> 👷 ci: collect required checks (<a href="https://redirect.github.com/tox-dev/py-filelock/issues/857";>#857</a>)</li> <li><a href="https://github.com/tox-dev/filelock/commit/cb8b57e471bcd505848991951541fdb5bff3ef02";><code>cb8b57e</code></a> fix(api): guard lazy import exit hook (<a href="https://redirect.github.com/tox-dev/py-filelock/issues/861";>#861</a>)</li> <li><a href="https://github.com/tox-dev/filelock/commit/dd341acfb4efbe3b0c9a686e7815e18e11582c4b";><code>dd341ac</code></a> Handle NetBSD EFTYPE for replaced soft-RW protocol directories (<a href="https://redirect.github.com/tox-dev/py-filelock/issues/859";>#859</a>)</li> <li><a href="https://github.com/tox-dev/filelock/commit/db47f34032dd72e865e296a8a13fbce539ba2c8a";><code>db47f34</code></a> Release 4.2.2</li> <li><a href="https://github.com/tox-dev/filelock/commit/caaff8ad35b9140f4f1ec43cb2aba452af7d67b5";><code>caaff8a</code></a> fix(api): keep the hold count when the lock path cannot be resolved (<a href="https://redirect.github.com/tox-dev/py-filelock/issues/856";>#856</a>)</li> <li><a href="https://github.com/tox-dev/filelock/commit/60331bb89f325020b48bc51bde904c6446384e4a";><code>60331bb</code></a> Release 4.2.1</li> <li>Additional commits viewable in <a href="https://github.com/tox-dev/py-filelock/compare/4.2.0...4.2.4";>compare view</a></li> </ul> </details> <br /> Updates `prek` from 0.5.5 to 0.5.7 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/j178/prek/releases";>prek's releases</a>.</em></p> <blockquote> <h2>0.5.7</h2> <h2>Release Notes</h2> <p>Released on 2026-10-21.</p> <h3>Enhancements</h3> <ul> <li>Support system Rust toolchains without rustup (<a href="https://redirect.github.com/j178/prek/pull/2887";>#2887</a>)</li> </ul> <h3>Performance</h3> <ul> <li>Use blocking file checks for CPU-heavy builtin hooks (<a href="https://redirect.github.com/j178/prek/pull/2910";>#2910</a>)</li> </ul> <h3>Other changes</h3> <ul> <li>Update CA root crates and uv for the eMudhra intermediate CA compromise (<a href="https://redirect.github.com/j178/prek/pull/2919";>#2919</a>)</li> </ul> <h3>Contributors</h3> <ul> <li><a href="https://github.com/shaanmajid";><code>@shaanmajid</code></a></li> <li><a href="https://github.com/j178";><code>@j178</code></a></li> </ul> <h2>Install prek 0.5.7</h2> <h3>Install prebuilt binaries via shell script</h3> <pre lang="sh"><code>curl --proto '=https' --tlsv1.2 -LsSf https://github.com/j178/prek/releases/download/v0.5.7/prek-installer.sh | sh </code></pre> <h3>Install prebuilt binaries via powershell script</h3> <pre lang="sh"><code>powershell -ExecutionPolicy Bypass -c "irm https://github.com/j178/prek/releases/download/v0.5.7/prek-installer.ps1 | iex" </code></pre> <h3>Install prebuilt binaries via Homebrew</h3> <pre lang="sh"><code>brew install prek </code></pre> <h2>Download prek 0.5.7</h2> <table> <thead> <tr> <th>File</th> <th>Platform</th> <th>Checksum</th> </tr> </thead> <tbody> <tr> <td><a href="https://github.com/j178/prek/releases/download/v0.5.7/prek-aarch64-apple-darwin.tar.gz";>prek-aarch64-apple-darwin.tar.gz</a></td> <td>Apple Silicon macOS</td> <td><a href="https://github.com/j178/prek/releases/download/v0.5.7/prek-aarch64-apple-darwin.tar.gz.sha256";>checksum</a></td> </tr> <tr> <td><a href="https://github.com/j178/prek/releases/download/v0.5.7/prek-x86_64-apple-darwin.tar.gz";>prek-x86_64-apple-darwin.tar.gz</a></td> <td>Intel macOS</td> <td><a href="https://github.com/j178/prek/releases/download/v0.5.7/prek-x86_64-apple-darwin.tar.gz.sha256";>checksum</a></td> </tr> <tr> <td><a href="https://github.com/j178/prek/releases/download/v0.5.7/prek-aarch64-pc-windows-msvc.zip";>prek-aarch64-pc-windows-msvc.zip</a></td> <td>ARM64 Windows</td> <td><a href="https://github.com/j178/prek/releases/download/v0.5.7/prek-aarch64-pc-windows-msvc.zip.sha256";>checksum</a></td> </tr> <tr> <td><a href="https://github.com/j178/prek/releases/download/v0.5.7/prek-x86_64-pc-windows-msvc.zip";>prek-x86_64-pc-windows-msvc.zip</a></td> <td>x64 Windows</td> <td><a href="https://github.com/j178/prek/releases/download/v0.5.7/prek-x86_64-pc-windows-msvc.zip.sha256";>checksum</a></td> </tr> </tbody> </table> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/j178/prek/blob/main/CHANGELOG.md";>prek's changelog</a>.</em></p> <blockquote> <h2>0.5.7</h2> <p>Released on 2026-10-21.</p> <h3>Enhancements</h3> <ul> <li>Support system Rust toolchains without rustup (<a href="https://redirect.github.com/j178/prek/pull/2887";>#2887</a>)</li> </ul> <h3>Performance</h3> <ul> <li>Use blocking file checks for CPU-heavy builtin hooks (<a href="https://redirect.github.com/j178/prek/pull/2910";>#2910</a>)</li> </ul> <h3>Other changes</h3> <ul> <li>Update CA root crates and uv for the eMudhra intermediate CA compromise (<a href="https://redirect.github.com/j178/prek/pull/2919";>#2919</a>)</li> </ul> <h3>Contributors</h3> <ul> <li><a href="https://github.com/shaanmajid";><code>@shaanmajid</code></a></li> <li><a href="https://github.com/j178";><code>@j178</code></a></li> </ul> <h2>0.5.6</h2> <p>Released on 2026-10-19.</p> <h3>Enhancements</h3> <ul> <li>Add builtin hook <code>check-commit-trailers</code> (<a href="https://redirect.github.com/j178/prek/pull/2885";>#2885</a>)</li> <li>Add builtin hook <code>check-signed-commit</code> (<a href="https://redirect.github.com/j178/prek/pull/2725";>#2725</a>)</li> </ul> <h3>Performance</h3> <ul> <li>Enable PGO for native release builds (<a href="https://redirect.github.com/j178/prek/pull/2890";>#2890</a>)</li> <li>Reduce hook process launches with balanced batches (<a href="https://redirect.github.com/j178/prek/pull/2907";>#2907</a>)</li> <li>Resolve hook commands before batching (<a href="https://redirect.github.com/j178/prek/pull/2840";>#2840</a>)</li> </ul> <h3>Bug fixes</h3> <ul> <li>Accept UTF-8 BOM in <code>check-json</code> (<a href="https://redirect.github.com/j178/prek/pull/2879";>#2879</a>)</li> <li>Preserve unquoted dotted revisions in <code>prek update</code> (<a href="https://redirect.github.com/j178/prek/pull/2853";>#2853</a>)</li> </ul> <h3>Documentation</h3> <ul> <li>Document standalone installer options (<a href="https://redirect.github.com/j178/prek/pull/2859";>#2859</a>)</li> <li>Update benchmarks for prek 0.5.5 (<a href="https://redirect.github.com/j178/prek/pull/2786";>#2786</a>)</li> </ul> <h3>Other changes</h3> <ul> <li>Enable ICF for release builds (<a href="https://redirect.github.com/j178/prek/pull/2891";>#2891</a>)</li> <li>Update uv to 0.13.0 (<a href="https://redirect.github.com/j178/prek/pull/2856";>#2856</a>)</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/j178/prek/commit/8569a4ac59a79212fe152f3c815505775301ec1d";><code>8569a4a</code></a> Bump version to 0.5.7 (<a href="https://redirect.github.com/j178/prek/issues/2920";>#2920</a>)</li> <li><a href="https://github.com/j178/prek/commit/c290bac7b2bc85e5d113bd3f20585b48f07c4cbe";><code>c290bac</code></a> Bump certifi from 2026.7.22 to 2026.10.19 (<a href="https://redirect.github.com/j178/prek/issues/2921";>#2921</a>)</li> <li><a href="https://github.com/j178/prek/commit/40287b8205068b2a0c01448e59b9ac7116763c6d";><code>40287b8</code></a> Temporarily skip Aliyun uv download in CI (<a href="https://redirect.github.com/j178/prek/issues/2922";>#2922</a>)</li> <li><a href="https://github.com/j178/prek/commit/062c8a0bd20cd04ea815fd1820671c42e748a39d";><code>062c8a0</code></a> Update CA root crates and uv for the eMudhra intermediate CA compromise (<a href="https://redirect.github.com/j178/prek/issues/2919";>#2919</a>)</li> <li><a href="https://github.com/j178/prek/commit/5b66378566f209aaaf71656540f2dac852ffb125";><code>5b66378</code></a> Log download and archive extraction stages (<a href="https://redirect.github.com/j178/prek/issues/2917";>#2917</a>)</li> <li><a href="https://github.com/j178/prek/commit/c3693539c41d72323190d93ccab5cd312d8fcd2d";><code>c369353</code></a> Share tar extraction across compression formats (<a href="https://redirect.github.com/j178/prek/issues/2916";>#2916</a>)</li> <li><a href="https://github.com/j178/prek/commit/1c82a0d0f01ecf06df2745bde2a997c742be3c90";><code>1c82a0d</code></a> Move managed Rust toolchain discovery into the installer (<a href="https://redirect.github.com/j178/prek/issues/2914";>#2914</a>)</li> <li><a href="https://github.com/j178/prek/commit/2bf1958a626bd61f35c62f185aa4cf3681bf9dd2";><code>2bf1958</code></a> Support system Rust toolchains without rustup (<a href="https://redirect.github.com/j178/prek/issues/2887";>#2887</a>)</li> <li><a href="https://github.com/j178/prek/commit/812e80f6d52d39db3627e0d666842919ed3ce864";><code>812e80f</code></a> Move shared hook helpers and rename run to concurrency (<a href="https://redirect.github.com/j178/prek/issues/2911";>#2911</a>)</li> <li><a href="https://github.com/j178/prek/commit/615a0016fbad79be1cfb63b15cc7288ea9c6046b";><code>615a001</code></a> Use blocking file checks for CPU-heavy builtin hooks (<a href="https://redirect.github.com/j178/prek/issues/2910";>#2910</a>)</li> <li>Additional commits viewable in <a href="https://github.com/j178/prek/compare/v0.5.5...v0.5.7";>compare view</a></li> </ul> </details> <br /> Updates `boto3` from 1.43.114 to 1.43.118 <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/boto/boto3/commit/185b1bd1bb677650bd986d581d19c0ed3596e583";><code>185b1bd</code></a> Merge branch 'release-1.43.118'</li> <li><a href="https://github.com/boto/boto3/commit/732c473d141c94365d0ba679f1b376b17ca7f429";><code>732c473</code></a> Bumping version to 1.43.118</li> <li><a href="https://github.com/boto/boto3/commit/b087cd3965d0c876c498ebd755d7663562dc39c8";><code>b087cd3</code></a> Add changelog entries from botocore</li> <li><a href="https://github.com/boto/boto3/commit/69e35c33ecdb461f226c479190ee8909b10a279c";><code>69e35c3</code></a> Backfill 1.43.117 changelog entry for CA bundle fix (<a href="https://redirect.github.com/boto/boto3/issues/4861";>#4861</a>)</li> <li><a href="https://github.com/boto/boto3/commit/36676797cc898470e079f032e7b43085135792e0";><code>3667679</code></a> Merge branch 'release-1.43.117'</li> <li><a href="https://github.com/boto/boto3/commit/ea1363487385e9c0788b08208a33f0c3e0c25951";><code>ea13634</code></a> Merge branch 'release-1.43.117' into develop</li> <li><a href="https://github.com/boto/boto3/commit/94f6b3ecda6e8ac834415299db7c3547442667d7";><code>94f6b3e</code></a> Bumping version to 1.43.117</li> <li><a href="https://github.com/boto/boto3/commit/1eba892af3005e14aebca3c8974a7aec69b00a5d";><code>1eba892</code></a> Add changelog entries from botocore</li> <li><a href="https://github.com/boto/boto3/commit/cfa48089b7c2d51815e49c7aeac1398ce955d83f";><code>cfa4808</code></a> Bump <a href="https://github.com/astral-sh/ruff-pre-commit";>https://github.com/astral-sh/ruff-pre-commit</a> (<a href="https://redirect.github.com/boto/boto3/issues/4860";>#4860</a>)</li> <li><a href="https://github.com/boto/boto3/commit/dbaa95d6cec6e692615db69ddcebccf814a70e8c";><code>dbaa95d</code></a> Merge branch 'release-1.43.116'</li> <li>Additional commits viewable in <a href="https://github.com/boto/boto3/compare/1.43.114...1.43.118";>compare view</a></li> </ul> </details> <br /> 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 <dependency name> major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore <dependency name> minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore <dependency name>` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore <dependency name>` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore <dependency name> <ignore condition>` will remove the ignore condition of the specified dependency and ignore conditions </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]
