Bump the registry-package-updates group across 1 directory with 3 updates

[dependabot]

Bumps the registry-package-updates group with 3 updates in the /registry directory: @11ty/eleventy, swagger-ui-dist and pagefind.

Updates @11ty/eleventy from 3.1.2 to 3.1.5

Release notes

Sourced from @​11ty/eleventy's releases.

Eleventy v3.1.5: Dependable Dependencies

• No Eleventy core code changes, this release is for minor version dependency updates on 3.x only
  • Fixes npm audit report for minimatch: #4239 via @11ty/recursive-copy@4.0.4
  • Upgrade liquidjs from 10.21 to 10.25
  • Freezes moo dependency #4240
  • Removes dev dependency rimraf
• Small improvements to HTML Relative Passthrough Copy tests

Full Changelog: 11ty/eleventy@v3.1.2...v3.1.5

Eleventy v3.1.4

⚠️ This immutable release failed to publish. Please use the identical Eleventy v3.1.5 instead!

Eleventy v3.1.3

⚠️ This immutable release failed to publish. Please use the identical Eleventy v3.1.5 instead!

Commits

• c8cae12 v3.1.5
• 08f0ef0 Release script changes from main
• 52bcacb v3.1.4
• a3ea614 Fix release script
• b3a1fd2 v3.1.3 Coverage
• b811903 More test ignores for Node 24
• 9d540d8 v3.1.3
• 116f6e2 Upgrade dependencies. Fixes #4239 Fixes #4240
• 21322ea Removes rimraf dev dependency
• See full diff in compare view

Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for @​11ty/eleventy since your current version.

Updates swagger-ui-dist from 5.32.0 to 5.32.2

Release notes

Sourced from swagger-ui-dist's releases.

v5.32.2

5.32.2 (2026-04-07)

Bug Fixes

• docker: bump libpng and zlib versions to fix CVE-2026-33416, CVE-2026-33636 and CVE-2026-22184 (#10802) (c200a69)

v5.32.1

5.32.1 (2026-03-17)

Bug Fixes

• invalidate models components cache based on location (#10764) (fb78dd2)
• style: use container queries for responsive design (#10763) (e35000e)

Commits

• d02a2df chore(release): cut the 5.32.2 release
• c200a69 fix(docker): bump libpng and zlib versions to fix CVE-2026-33416, CVE-2026-33...
• eff82c1 chore(deps): bump lodash from 4.17.23 to 4.18.1 (#10801)
• 860ade2 chore(deps): bump defu from 6.1.4 to 6.1.6 (#10797)
• 749ec50 chore(deps): bump dependabot/fetch-metadata from 2.5.0 to 3.0.0 (#10777)
• b339e55 chore(deps): bump node-forge from 1.3.3 to 1.4.0 (#10781)
• 692e0ac chore(deps-dev): bump serialize-javascript from 7.0.4 to 7.0.5 (#10782)
• 14cc424 chore(deps-dev): bump brace-expansion from 1.1.12 to 1.1.13 (#10783)
• 076c188 chore(deps-dev): bump handlebars from 4.7.8 to 4.7.9 (#10778)
• f251747 chore(deps-dev): bump flatted from 3.3.3 to 3.4.2 (#10774)
• Additional commits viewable in compare view

Updates pagefind from 1.4.0 to 1.5.0

Release notes

Sourced from pagefind's releases.

v1.5.0

Hey! This is a big one. Pagefind 1.5.0 has been fermenting for a while, and addresses a lot 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 ❤️ - @​bglw

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.

Pagefind Component UI

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 <pagefind-*> elements that you can mix, match, and style with CSS variables.

The Component UI is available as vendored files in your /pagefind/ output directory, or as an npm package to install and import.

The best way to get a feel for the new components is on the 📘 Pagefind Component UI page of the docs, where interactive examples of various components are shown.

Extra goodies with the Component UI:

• Greatly improved accessibility over the Default UI
• Keyboard navigation through search results
• Configurable keyboard shortcuts (thanks @​miketheman !)
• Full custom templates for rendering results and placeholders
• Exported types for Component UI npm consumers (thanks @​vanruesc !)
• Support for multiple scoped Pagefind instances on one page
• A range of CSS variables available for light-touch customization (thanks @​miketheman for some of these!)
• Improved RTL and locale-specific rendering

Search Relevance, and Searching Metadata

Pagefind now searches metadata by default! Importantly, this means it now searches the title metadata. Matches in titles are now taken into account, and search results are very hard to shake from prime positions if all (or much) of the title matches the search query.

You can configure the weight of any metadata field. See 📘 Configuring Metadata Weights to change the title boost or apply custom weights to your own metadata fields.

Beyond metadata searching, a bunch of weird and wonderful ranking bugs were resolved:

• 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.
• 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.
• 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.
• 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.
• Fancy-pants unicode characters in words could really mess up the chunk loading, which has been fixed.

Diacritics Support

We finally properly support matching across diacritics. You can now find your cafés without remembering how to type é.

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 📘 Configuring Diacritic Similarity to adjust how this plays out on your site.

If you need strict matching, set exactDiacritics: true to disable normalization entirely — "cafe" will only match "cafe", and "café" will only match "café". 📘 Exact Diacritics

Multilingual Improvements

Thanks browsers! Pagefind now taps into Intl.Segmenter 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.

... (truncated)

Changelog

Sourced from pagefind's changelog.

v1.5.0 (April 6, 2026)

Hey! This is a big one. Pagefind 1.5.0 has been fermenting for a while, and addresses a lot 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 ❤️ - @​bglw

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.

Pagefind Component UI

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 <pagefind-*> elements that you can mix, match, and style with CSS variables.

The Component UI is available as vendored files in your /pagefind/ output directory, or as an npm package to install and import.

The best way to get a feel for the new components is on the 📘 Pagefind Component UI page of the docs, where interactive examples of various components are shown.

Extra goodies with the Component UI:

• Greatly improved accessibility over the Default UI
• Keyboard navigation through search results
• Configurable keyboard shortcuts (thanks @​miketheman !)
• Full custom templates for rendering results and placeholders
• Exported types for Component UI npm consumers (thanks @​vanruesc !)
• Support for multiple scoped Pagefind instances on one page
• A range of CSS variables available for light-touch customization (thanks @​miketheman for some of these!)
• Improved RTL and locale-specific rendering

Search Relevance, and Searching Metadata

Pagefind now searches metadata by default! Importantly, this means it now searches the title metadata. Matches in titles are now taken into account, and search results are very hard to shake from prime positions if all (or much) of the title matches the search query.

You can configure the weight of any metadata field. See 📘 Configuring Metadata Weights to change the title boost or apply custom weights to your own metadata fields.

Beyond metadata searching, a bunch of weird and wonderful ranking bugs were resolved:

• 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.
• 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.
• 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.
• 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.
• Fancy-pants unicode characters in words could really mess up the chunk loading, which has been fixed.

Diacritics Support

We finally properly support matching across diacritics. You can now find your cafés without remembering how to type é.

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 📘 Configuring Diacritic Similarity to adjust how this plays out on your site.

If you need strict matching, set exactDiacritics: true to disable normalization entirely — "cafe" will only match "cafe", and "café" will only match "café". 📘 Exact Diacritics

Multilingual Improvements

Thanks browsers! Pagefind now taps into Intl.Segmenter 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.

... (truncated)

Commits

• 0c6d2fe Release tidy-ups (#1094)
• 162d756 v1.5.0 Changelog (#1093)
• d5973c2 A collection of docs fixes (#1092)
• 84a46ef Improve flaky keyboard shortcuts test (#1091)
• 883df72 Add highlightParam and exactDiacritics attributes to <pagefind-config> (#1090)
• 259ca49 Add plain_excerpt field to search results (#1089)
• 7347d5f Fix box-sizing for pseudo-elements in component UI (#1088)
• 23d03e5 Fix relative image URLs breaking in search results (#1087)
• 3bc1bd5 Add scoped instances to initialize properly separate configurations (#1085)
• 778c873 Improve RTL layouts in the component UI (#1086)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for pagefind since your current version.