dependabot[bot] opened a new pull request, #65066: URL: https://github.com/apache/airflow/pull/65066
Bumps the registry-package-updates group with 3 updates in the /registry directory: [@11ty/eleventy](https://github.com/11ty/eleventy), [swagger-ui-dist](https://github.com/swagger-api/swagger-ui) and [pagefind](https://github.com/Pagefind/pagefind). Updates `@11ty/eleventy` from 3.1.2 to 3.1.5 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/11ty/eleventy/releases";><code>@11ty/eleventy</code>'s releases</a>.</em></p> <blockquote> <h2>Eleventy v3.1.5: Dependable Dependencies</h2> <ul> <li>No Eleventy core code changes, this release is for minor version dependency updates on 3.x only <ul> <li>Fixes <code>npm audit</code> report for <code>minimatch</code>: <a href="https://redirect.github.com/11ty/eleventy/issues/4239";>#4239</a> via <a href="https://github.com/11ty/recursive-copy/releases/tag/v4.0.4";><code>@11ty/[email protected]</code></a></li> <li>Upgrade <a href="https://github.com/harttle/liquidjs/releases";><code>liquidjs</code> from 10.21 to 10.25</a></li> <li>Freezes <code>moo</code> dependency <a href="https://redirect.github.com/11ty/eleventy/issues/4240";>#4240</a></li> <li>Removes dev dependency <code>rimraf</code></li> </ul> </li> <li>Small improvements to HTML Relative Passthrough Copy tests</li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/11ty/eleventy/compare/v3.1.2...v3.1.5";>https://github.com/11ty/eleventy/compare/v3.1.2...v3.1.5</a></p> <h2>Eleventy v3.1.4</h2> <p>⚠️ This immutable release failed to publish. Please use the identical <a href="https://github.com/11ty/eleventy/releases/tag/v3.1.5";>Eleventy v3.1.5</a> instead!</p> <h2>Eleventy v3.1.3</h2> <p>⚠️ This immutable release failed to publish. Please use the identical <a href="https://github.com/11ty/eleventy/releases/tag/v3.1.5";>Eleventy v3.1.5</a> instead!</p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/11ty/eleventy/commit/c8cae123fe61ea17aac6ce850393c157d0e30780";><code>c8cae12</code></a> v3.1.5</li> <li><a href="https://github.com/11ty/eleventy/commit/08f0ef095a885d4177884c93f6faf7cdd90e77de";><code>08f0ef0</code></a> Release script changes from <code>main</code></li> <li><a href="https://github.com/11ty/eleventy/commit/52bcacbf94e33d19e81199d2e115b5c5ce275da5";><code>52bcacb</code></a> v3.1.4</li> <li><a href="https://github.com/11ty/eleventy/commit/a3ea614d64d5e80d6f2e6708a4d7f79b82b1720e";><code>a3ea614</code></a> Fix release script</li> <li><a href="https://github.com/11ty/eleventy/commit/b3a1fd2af518ee14f31437e20faf18fbb103e7fe";><code>b3a1fd2</code></a> v3.1.3 Coverage</li> <li><a href="https://github.com/11ty/eleventy/commit/b8119031b71f098e46b3fde91a88e0bf14861655";><code>b811903</code></a> More test ignores for Node 24</li> <li><a href="https://github.com/11ty/eleventy/commit/9d540d86c1cfee308ebe129512b47610ee898fb3";><code>9d540d8</code></a> v3.1.3</li> <li><a href="https://github.com/11ty/eleventy/commit/116f6e210e229bc8ed362d2a48aa842660be4604";><code>116f6e2</code></a> Upgrade dependencies. Fixes <a href="https://redirect.github.com/11ty/eleventy/issues/4239";>#4239</a> Fixes <a href="https://redirect.github.com/11ty/eleventy/issues/4240";>#4240</a></li> <li><a href="https://github.com/11ty/eleventy/commit/21322ea5ed8427c9c8b1ee12ea5303fe3b090b74";><code>21322ea</code></a> Removes <code>rimraf</code> dev dependency</li> <li>See full diff in <a href="https://github.com/11ty/eleventy/compare/v3.1.2...v3.1.5";>compare view</a></li> </ul> </details> <details> <summary>Maintainer changes</summary> <p>This version was pushed to npm by [GitHub Actions](<a href="https://www.npmjs.com/~GitHub";>https://www.npmjs.com/~GitHub</a> Actions), a new releaser for <code>@11ty/eleventy</code> since your current version.</p> </details> <br /> Updates `swagger-ui-dist` from 5.32.0 to 5.32.2 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/swagger-api/swagger-ui/releases";>swagger-ui-dist's releases</a>.</em></p> <blockquote> <h2>v5.32.2</h2> <h2><a href="https://github.com/swagger-api/swagger-ui/compare/v5.32.1...v5.32.2";>5.32.2</a> (2026-04-07)</h2> <h3>Bug Fixes</h3> <ul> <li><strong>docker:</strong> bump libpng and zlib versions to fix CVE-2026-33416, CVE-2026-33636 and CVE-2026-22184 (<a href="https://redirect.github.com/swagger-api/swagger-ui/issues/10802";>#10802</a>) (<a href="https://github.com/swagger-api/swagger-ui/commit/c200a69b634343b663f4cb8908678cd332aa8e64";>c200a69</a>)</li> </ul> <h2>v5.32.1</h2> <h2><a href="https://github.com/swagger-api/swagger-ui/compare/v5.32.0...v5.32.1";>5.32.1</a> (2026-03-17)</h2> <h3>Bug Fixes</h3> <ul> <li>invalidate models components cache based on location (<a href="https://redirect.github.com/swagger-api/swagger-ui/issues/10764";>#10764</a>) (<a href="https://github.com/swagger-api/swagger-ui/commit/fb78dd2a497307529fff3d368936519d050b5946";>fb78dd2</a>)</li> <li><strong>style:</strong> use container queries for responsive design (<a href="https://redirect.github.com/swagger-api/swagger-ui/issues/10763";>#10763</a>) (<a href="https://github.com/swagger-api/swagger-ui/commit/e35000e0b353d5bd756d142fbbc2337adab7fb31";>e35000e</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/swagger-api/swagger-ui/commit/d02a2df106961d8cb6bceb6b4b3aa8d9f6faaf4a";><code>d02a2df</code></a> chore(release): cut the 5.32.2 release</li> <li><a href="https://github.com/swagger-api/swagger-ui/commit/c200a69b634343b663f4cb8908678cd332aa8e64";><code>c200a69</code></a> fix(docker): bump libpng and zlib versions to fix CVE-2026-33416, CVE-2026-33...</li> <li><a href="https://github.com/swagger-api/swagger-ui/commit/eff82c1fd004ba1d061f9c41f5a980339fb889bf";><code>eff82c1</code></a> chore(deps): bump lodash from 4.17.23 to 4.18.1 (<a href="https://redirect.github.com/swagger-api/swagger-ui/issues/10801";>#10801</a>)</li> <li><a href="https://github.com/swagger-api/swagger-ui/commit/860ade2c7f8e50a838228bece0e18d93d23198b0";><code>860ade2</code></a> chore(deps): bump defu from 6.1.4 to 6.1.6 (<a href="https://redirect.github.com/swagger-api/swagger-ui/issues/10797";>#10797</a>)</li> <li><a href="https://github.com/swagger-api/swagger-ui/commit/749ec5097273aeced4e71078867d5338b63ee65c";><code>749ec50</code></a> chore(deps): bump dependabot/fetch-metadata from 2.5.0 to 3.0.0 (<a href="https://redirect.github.com/swagger-api/swagger-ui/issues/10777";>#10777</a>)</li> <li><a href="https://github.com/swagger-api/swagger-ui/commit/b339e559ac986506d41728054ec8d07cf8c1046f";><code>b339e55</code></a> chore(deps): bump node-forge from 1.3.3 to 1.4.0 (<a href="https://redirect.github.com/swagger-api/swagger-ui/issues/10781";>#10781</a>)</li> <li><a href="https://github.com/swagger-api/swagger-ui/commit/692e0ace72378d1e62b041b613fcc967251ddbb2";><code>692e0ac</code></a> chore(deps-dev): bump serialize-javascript from 7.0.4 to 7.0.5 (<a href="https://redirect.github.com/swagger-api/swagger-ui/issues/10782";>#10782</a>)</li> <li><a href="https://github.com/swagger-api/swagger-ui/commit/14cc424da6c4eb716a832462b172e67af4df69c4";><code>14cc424</code></a> chore(deps-dev): bump brace-expansion from 1.1.12 to 1.1.13 (<a href="https://redirect.github.com/swagger-api/swagger-ui/issues/10783";>#10783</a>)</li> <li><a href="https://github.com/swagger-api/swagger-ui/commit/076c188477fb20e46da7bd2e43c13bb59f71e2ea";><code>076c188</code></a> chore(deps-dev): bump handlebars from 4.7.8 to 4.7.9 (<a href="https://redirect.github.com/swagger-api/swagger-ui/issues/10778";>#10778</a>)</li> <li><a href="https://github.com/swagger-api/swagger-ui/commit/f251747350848eae8da0b39bb84ec41b41bb368a";><code>f251747</code></a> chore(deps-dev): bump flatted from 3.3.3 to 3.4.2 (<a href="https://redirect.github.com/swagger-api/swagger-ui/issues/10774";>#10774</a>)</li> <li>Additional commits viewable in <a href="https://github.com/swagger-api/swagger-ui/compare/v5.32.0...v5.32.2";>compare view</a></li> </ul> </details> <br /> Updates `pagefind` from 1.4.0 to 1.5.0 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/Pagefind/pagefind/releases";>pagefind's releases</a>.</em></p> <blockquote> <h2>v1.5.0</h2> <p>Hey! This is a big one. Pagefind 1.5.0 has been fermenting for a while, and addresses a <em>lot</em> of long-standing issues and feature requests. This release brings an entirely new search UI built on web components, major improvements to search relevance and ranking, diacritics support, automatic CJK segmentation, Web Worker search, notably smaller indexes, and a much faster indexing binary. Enormous thanks to everyone who contributed features and fixes, as well as to everyone who tested the beta releases and provided feedback ❤️ - <a href="https://github.com/bglw";><code>@bglw</code></a></p> <p>If you only read this far, I should mention up front: The existing Default UI and Modular UI remain available and supported for now, so you can upgrade your sites to Pagefind v1.5.0 without migrating to the Component UI.</p> <h3>Pagefind Component UI</h3> <p>Pagefind ships a brand new UI system built entirely on web components. The Component UI gives you searchboxes, modals, result lists, and filter controls as composable <code><pagefind-*></code> elements that you can mix, match, and style with CSS variables.</p> <p>The Component UI is available as vendored files in your <code>/pagefind/</code> output directory, or as <a href="https://www.npmjs.com/package/@pagefind/component-ui";>an npm package</a> to install and import.</p> <p>The best way to get a feel for the new components is on the <a href="https://pagefind.app/docs/search-ui/#modal-search";>📘 Pagefind Component UI</a> page of the docs, where interactive examples of various components are shown.</p> <p>Extra goodies with the Component UI:</p> <ul> <li>Greatly improved accessibility over the Default UI</li> <li>Keyboard navigation through search results</li> <li>Configurable keyboard shortcuts (thanks <a href="https://github.com/miketheman";><code>@miketheman</code></a> !)</li> <li>Full custom templates for rendering results and placeholders</li> <li>Exported types for Component UI npm consumers (thanks <a href="https://github.com/vanruesc";><code>@vanruesc</code></a> !)</li> <li>Support for multiple scoped Pagefind instances on one page</li> <li>A range of CSS variables available for light-touch customization (thanks <a href="https://github.com/miketheman";><code>@miketheman</code></a> for some of these!)</li> <li>Improved RTL and locale-specific rendering</li> </ul> <h3>Search Relevance, and Searching Metadata</h3> <p>Pagefind now searches metadata by default! Importantly, this means it now searches the <em>title</em> metadata. Matches in titles are now taken into account, and search results are <em>very</em> hard to shake from prime positions if all (or much) of the title matches the search query.</p> <p>You can configure the weight of any metadata field. See <a href="https://pagefind.app/docs/ranking/#configuring-metadata-weights";>📘 Configuring Metadata Weights</a> to change the title boost or apply custom weights to your own metadata fields.</p> <p>Beyond metadata searching, a <em>bunch</em> of weird and wonderful ranking bugs were resolved:</p> <ul> <li>Metadata-only matches now return results. Previously, if a page matched the search query only in its metadata (e.g. the title) but not in the body content, it would be missed. These pages now correctly appear in results.</li> <li>Word splitting and indexing was revisited to properly handle diacritics, stemming, and compound words together. This fixes a broad set of edge cases where compound word parts weren't indexed correctly.</li> <li>Loading index chunks now correctly uses stemmed terms. This was a discrepancy in how chunks were identified, and could cause some hard to pin down issues where the wrong chunk would be loaded for a search term, leaving you with no (or fewer) results.</li> <li>A couple of pathways left you with only the first matching chunk loaded, which would also give you fewer results. Words that straddle multiple chunks now behave better.</li> <li>Fancy-pants unicode characters in words could <em>really</em> mess up the chunk loading, which has been fixed.</li> </ul> <h3>Diacritics Support</h3> <p>We finally properly support matching across diacritics. You can now find your cafés without remembering how to type é.</p> <p>By default, exact diacritic matches are preferred. So if you're searching "cafe", pages with "cafe" will rank higher than pages with "café". Getting this relevance right by default was the final piece of the puzzle for shipping this, which is why it took a while to land. See <a href="https://pagefind.app/docs/ranking/#configuring-diacritic-similarity";>📘 Configuring Diacritic Similarity</a> to adjust how this plays out on your site.</p> <p>If you need strict matching, set <code>exactDiacritics: true</code> to disable normalization entirely — "cafe" will only match "cafe", and "café" will only match "café". <a href="https://pagefind.app/docs/search-config/#exact-diacritics";>📘 Exact Diacritics</a></p> <h3>Multilingual Improvements</h3> <p>Thanks browsers! Pagefind now taps into <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/Segmenter";>Intl.Segmenter</a> to chop search queries in CJK (Chinese, Japanese, Korean) non-whitespace-delimited languages. This was already done during indexing by Pagefind, but users searching still had to delimit their queries. Now searching "这是一段简单的测试文本" searches for the words "这", "是", "一段", "简单", "的", "测试", and "文本", which is also how that sentence was indexed.</p> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/Pagefind/pagefind/blob/main/CHANGELOG.md";>pagefind's changelog</a>.</em></p> <blockquote> <h2>v1.5.0 (April 6, 2026)</h2> <p>Hey! This is a big one. Pagefind 1.5.0 has been fermenting for a while, and addresses a <em>lot</em> of long-standing issues and feature requests. This release brings an entirely new search UI built on web components, major improvements to search relevance and ranking, diacritics support, automatic CJK segmentation, Web Worker search, notably smaller indexes, and a much faster indexing binary. Enormous thanks to everyone who contributed features and fixes, as well as to everyone who tested the beta releases and provided feedback ❤️ - <a href="https://github.com/bglw";><code>@bglw</code></a></p> <p>If you only read this far, I should mention up front: The existing Default UI and Modular UI remain available and supported for now, so you can upgrade your sites to Pagefind v1.5.0 without migrating to the Component UI.</p> <h3>Pagefind Component UI</h3> <p>Pagefind ships a brand new UI system built entirely on web components. The Component UI gives you searchboxes, modals, result lists, and filter controls as composable <code><pagefind-*></code> elements that you can mix, match, and style with CSS variables.</p> <p>The Component UI is available as vendored files in your <code>/pagefind/</code> output directory, or as <a href="https://www.npmjs.com/package/@pagefind/component-ui";>an npm package</a> to install and import.</p> <p>The best way to get a feel for the new components is on the <a href="https://pagefind.app/docs/search-ui/#modal-search";>📘 Pagefind Component UI</a> page of the docs, where interactive examples of various components are shown.</p> <p>Extra goodies with the Component UI:</p> <ul> <li>Greatly improved accessibility over the Default UI</li> <li>Keyboard navigation through search results</li> <li>Configurable keyboard shortcuts (thanks <a href="https://github.com/miketheman";><code>@miketheman</code></a> !)</li> <li>Full custom templates for rendering results and placeholders</li> <li>Exported types for Component UI npm consumers (thanks <a href="https://github.com/vanruesc";><code>@vanruesc</code></a> !)</li> <li>Support for multiple scoped Pagefind instances on one page</li> <li>A range of CSS variables available for light-touch customization (thanks <a href="https://github.com/miketheman";><code>@miketheman</code></a> for some of these!)</li> <li>Improved RTL and locale-specific rendering</li> </ul> <h3>Search Relevance, and Searching Metadata</h3> <p>Pagefind now searches metadata by default! Importantly, this means it now searches the <em>title</em> metadata. Matches in titles are now taken into account, and search results are <em>very</em> hard to shake from prime positions if all (or much) of the title matches the search query.</p> <p>You can configure the weight of any metadata field. See <a href="https://pagefind.app/docs/ranking/#configuring-metadata-weights";>📘 Configuring Metadata Weights</a> to change the title boost or apply custom weights to your own metadata fields.</p> <p>Beyond metadata searching, a <em>bunch</em> of weird and wonderful ranking bugs were resolved:</p> <ul> <li>Metadata-only matches now return results. Previously, if a page matched the search query only in its metadata (e.g. the title) but not in the body content, it would be missed. These pages now correctly appear in results.</li> <li>Word splitting and indexing was revisited to properly handle diacritics, stemming, and compound words together. This fixes a broad set of edge cases where compound word parts weren't indexed correctly.</li> <li>Loading index chunks now correctly uses stemmed terms. This was a discrepancy in how chunks were identified, and could cause some hard to pin down issues where the wrong chunk would be loaded for a search term, leaving you with no (or fewer) results.</li> <li>A couple of pathways left you with only the first matching chunk loaded, which would also give you fewer results. Words that straddle multiple chunks now behave better.</li> <li>Fancy-pants unicode characters in words could <em>really</em> mess up the chunk loading, which has been fixed.</li> </ul> <h3>Diacritics Support</h3> <p>We finally properly support matching across diacritics. You can now find your cafés without remembering how to type é.</p> <p>By default, exact diacritic matches are preferred. So if you're searching "cafe", pages with "cafe" will rank higher than pages with "café". Getting this relevance right by default was the final piece of the puzzle for shipping this, which is why it took a while to land. See <a href="https://pagefind.app/docs/ranking/#configuring-diacritic-similarity";>📘 Configuring Diacritic Similarity</a> to adjust how this plays out on your site.</p> <p>If you need strict matching, set <code>exactDiacritics: true</code> to disable normalization entirely — "cafe" will only match "cafe", and "café" will only match "café". <a href="https://pagefind.app/docs/search-config/#exact-diacritics";>📘 Exact Diacritics</a></p> <h3>Multilingual Improvements</h3> <p>Thanks browsers! Pagefind now taps into <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/Segmenter";>Intl.Segmenter</a> to chop search queries in CJK (Chinese, Japanese, Korean) non-whitespace-delimited languages. This was already done during indexing by Pagefind, but users searching still had to delimit their queries. Now searching "这是一段简单的测试文本" searches for the words "这", "是", "一段", "简单", "的", "测试", and "文本", which is also how that sentence was indexed.</p> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/Pagefind/pagefind/commit/0c6d2feafddfb16ad6cdc67b2b28f3fecac9b25b";><code>0c6d2fe</code></a> Release tidy-ups (<a href="https://redirect.github.com/Pagefind/pagefind/issues/1094";>#1094</a>)</li> <li><a href="https://github.com/Pagefind/pagefind/commit/162d7567ee5a7148e59b26c45ff3c524f2f16753";><code>162d756</code></a> v1.5.0 Changelog (<a href="https://redirect.github.com/Pagefind/pagefind/issues/1093";>#1093</a>)</li> <li><a href="https://github.com/Pagefind/pagefind/commit/d5973c2e6d8660a030b90b9cec86f46f698c2f4f";><code>d5973c2</code></a> A collection of docs fixes (<a href="https://redirect.github.com/Pagefind/pagefind/issues/1092";>#1092</a>)</li> <li><a href="https://github.com/Pagefind/pagefind/commit/84a46efb03c673861c872992419cda8453fedcfc";><code>84a46ef</code></a> Improve flaky keyboard shortcuts test (<a href="https://redirect.github.com/Pagefind/pagefind/issues/1091";>#1091</a>)</li> <li><a href="https://github.com/Pagefind/pagefind/commit/883df72195519f4426b8972e61d0986c71dd84be";><code>883df72</code></a> Add highlightParam and exactDiacritics attributes to <pagefind-config> (<a href="https://redirect.github.com/Pagefind/pagefind/issues/1090";>#1090</a>)</li> <li><a href="https://github.com/Pagefind/pagefind/commit/259ca4928a59a209fa41a2dd210a880605200933";><code>259ca49</code></a> Add plain_excerpt field to search results (<a href="https://redirect.github.com/Pagefind/pagefind/issues/1089";>#1089</a>)</li> <li><a href="https://github.com/Pagefind/pagefind/commit/7347d5f0cb659410b72da4f09b896b3ead318d58";><code>7347d5f</code></a> Fix box-sizing for pseudo-elements in component UI (<a href="https://redirect.github.com/Pagefind/pagefind/issues/1088";>#1088</a>)</li> <li><a href="https://github.com/Pagefind/pagefind/commit/23d03e5eb84e07f759291a1fdb3ce63ba737db3b";><code>23d03e5</code></a> Fix relative image URLs breaking in search results (<a href="https://redirect.github.com/Pagefind/pagefind/issues/1087";>#1087</a>)</li> <li><a href="https://github.com/Pagefind/pagefind/commit/3bc1bd5f9d311cde3711862f5e6f5210930b7eb9";><code>3bc1bd5</code></a> Add scoped instances to initialize properly separate configurations (<a href="https://redirect.github.com/Pagefind/pagefind/issues/1085";>#1085</a>)</li> <li><a href="https://github.com/Pagefind/pagefind/commit/778c8732a4a58227232afb4dac280e084248d7a7";><code>778c873</code></a> Improve RTL layouts in the component UI (<a href="https://redirect.github.com/Pagefind/pagefind/issues/1086";>#1086</a>)</li> <li>Additional commits viewable in <a href="https://github.com/Pagefind/pagefind/compare/v1.4.0...v1.5.0";>compare view</a></li> </ul> </details> <details> <summary>Maintainer changes</summary> <p>This version was pushed to npm by [GitHub Actions](<a href="https://www.npmjs.com/~GitHub";>https://www.npmjs.com/~GitHub</a> Actions), a new releaser for pagefind since your current version.</p> </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]
