deps-rust: bump html-to-markdown-rs from 3.2.6 to 3.6.20 in /src-tauri

[dependabot]

Bumps html-to-markdown-rs from 3.2.6 to 3.6.20.

Release notes

Sourced from html-to-markdown-rs's releases.

v3.6.20

Swift Package Manager

Add to your Package.swift:

.package(url: "https://github.com/kreuzberg-dev/html-to-markdown", from: "3.6.20")

The Swift binding is distributed as a pre-built artifact bundle. No Rust toolchain required.

Artifact: HtmlToMarkdown-rs.artifactbundle.zip Checksum: bd510aebc5cd41d3b742fb5df32d7de62e3e7a3ac67c298e9f2658e1d0ac3365

Zig

Add to your build.zig.zon:

.dependencies = .{
    .html-to-markdown-rs-zig = .{\n        .url = \"https://github.com/kreuzberg-dev/html-to-markdown/releases/download/v3.6.20/html-to-markdown-rs-zig-v3.6.20.tar.gz\",\n        .hash = \"html_to_markdown_rs-3.6.20-QtXyWxY3AQAAiIzL1plM-zpynxmxL23d_JqELIak6jIK\",\n    },\n},\n```\n
v3.6.19
Swift Package Manager
Add to your Package.swift:
.package(url: "https://github.com/kreuzberg-dev/html-to-markdown", from: "3.6.19")
</code></pre>
<p>The Swift binding is distributed as a pre-built artifact bundle. No Rust toolchain required.</p>
<p><strong>Artifact</strong>: <a href="https://github.com/kreuzberg-dev/html-to-markdown/releases/download/v3.6.19/HtmlToMarkdown-rs.artifactbundle.zip">HtmlToMarkdown-rs.artifactbundle.zip</a>
<strong>Checksum</strong>: <code>99ab6fe1c30809ef3a65768fa02a4b3442af58500a94561e848c10194f125be5</code></p>
<!-- raw HTML omitted -->
<h2>Zig</h2>
<p>Add to your <code>build.zig.zon</code>:</p>
<pre><code>.dependencies = .{
    .html-to-markdown-rs-zig = .{\n        .url = \&quot;https://github.com/kreuzberg-dev/html-to-markdown/releases/download/v3.6.19/html-to-markdown-rs-zig-v3.6.19.tar.gz\&quot;,\n        .hash = \&quot;html_to_markdown_rs-3.6.19-QtXyWxY3AQB1EZz9fEW2CPe1LBO1Zhzn9LIRKwOv_LnI\&quot;,\n    },\n},\n```\n
v3.6.18
Swift Package Manager
Add to your Package.swift:

&lt;/tr&gt;&lt;/table&gt;

</code></pre>

</blockquote>

<p>... (truncated)</p>

</details>

<details>

<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/kreuzberg-dev/html-to-markdown/blob/main/CHANGELOG.md&quot;&gt;html-to-markdown-rs's changelog</a>.</em></p>

<blockquote>

<h2>[3.6.20] - 2026-06-21</h2>

<h3>Fixed</h3>

<ul>

<li><strong>chore(precommit): scope the v2.3.0 strict doc/format/lint hooks away from the generated trees.</strong> The canonical-hookset bump (v2.3.0, commit <code>8a5203b7d</code>) enabled several strict hooks that ran against alef-generated code and failed on it. All per-language code under <code>packages/&lt;lang&gt;/</code>, <code>e2e/</code>, and <code>test_apps/</code> is generated and ships as alef emits it, so each hook now carries the same generated-tree exclusion the other formatters already use: <code>yard-coverage</code> excludes <code>packages/ruby/</code> (its <code>native.rb</code> holds undocumentable Sorbet-sig RBI defs); <code>air-check</code>/<code>air-format</code> exclude <code>packages/</code> (alef formats R with styler, not air); <code>palantir-java-format</code> excludes <code>packages/</code>, <code>e2e/</code>, <code>test_apps/</code>, and the vendored <code>.mvn/</code> wrapper. The <code>lintr</code> hook runs <code>lintr::lint_dir(&quot;.&quot;)</code> and ignores pre-commit file scoping, so its exclusion lives in a new root <code>.lintr</code> (<code>exclusions: list(&quot;e2e&quot;, &quot;packages&quot;, &quot;test_apps&quot;)</code>); <code>tsc-typecheck</code> runs <code>tsc --noEmit</code> from the repo root, so a root <code>tsconfig.json</code> scopes type-checking to <code>packages/typescript/src</code>. <code>.yardoc/</code> (yard's cache side-effect) is gitignored. (<code>.pre-commit-config.yaml</code>, <code>.lintr</code>, <code>tsconfig.json</code>, <code>.gitignore</code>)</li>

<li><strong>chore(precommit): exclude alef-canonical generated files from the formatters that diverge from alef's own output.</strong> alef 0.25.58 made <code>alef verify</code> output-sensitive and the v2.3.0 hookset added <code>alef-docs-fresh</code> (which runs <code>alef verify</code>), so any prek formatter that rewrites a generated file differently than alef emits it now breaks verify. Fourteen generated files hit this because the hooks' pinned tools differ from alef's: <code>ruff</code>/<code>ruff-format</code> (line-wrapping generated Python), <code>pyproject-fmt</code> (alef runs no pyproject-fmt pass), <code>oxfmt</code> (alef formats <code>composer.json</code> via npm oxfmt; the hook uses the oxc binary with a different style), <code>shfmt</code> (generated <code>download_ffi.sh</code>/<code>install.sh</code>/<code>gradlew</code>), <code>cargo-sort</code> (the workspace-excluded R and Elixir NIF <code>Cargo.toml</code>), and <code>end-of-file-fixer</code> (the Dart <code>frb_generated.dart</code> and <code>test_apps</code> <code>init.py</code>). Each now carries the generated-tree exclusion the other tools already use, so the files ship exactly as alef emits them and <code>alef verify</code> stays clean. (<code>.pre-commit-config.yaml</code>)</li>

</ul>

<h3>Changed</h3>

<ul>

<li><strong>chore(deps): re-pin <code>alef.toml.alef_version</code> to 0.25.58 and regenerate every binding, e2e suite, README, and API doc.</strong> Folds in the 0.25.55–0.25.58 generator fixes that apply here: the generated Go <code>cmd/download_ffi/main.go</code> tool now carries the standard <code>auto-generated by alef</code> marker so golangci-lint's <code>generated: lax</code> skips it (0.25.x had dropped its <code>//go:build ignore</code> guard, exposing inherent-to-a-downloader gosec/errcheck findings); the <code>generate</code>/<code>all</code> up-to-date skip now also compares against on-disk output (not just the side cache), so out-of-band drift (a <code>git restore</code>, a hand-edit, an interrupted write) is regenerated rather than silently retained; <strong>extract</strong> OR-merges cfg gates for same-named types with disjoint gates; <strong>R/extendr</strong> forwards cfg-gated core features into the generated crate's <code>[features]</code> table so it builds under <code>-D warnings</code>. The visible churn is the generator's <code>.d.ts</code>/TS-bridge reformatting (tabs→2-space, double→single quotes). Verified locally: <code>alef verify</code> is clean and the 3.6.20 bump is synced across all manifests. (alef 0.25.58)</li>

</ul>

<h2>[3.6.19] - 2026-06-20</h2>

<h3>Fixed</h3>

<ul>

<li><strong>test_apps(php): install the PHP extension via PIE's <code>pkg:version</code> syntax.</strong> Both generated PHP test_app installers (<code>test_apps/php/install.sh</code>, <code>test_apps/php_ext/run_tests.sh</code>) ran <code>pie install --version &quot;$VERSION&quot; &lt;pkg&gt;</code>, but PIE parses <code>--version</code>/<code>-V</code> as &quot;print PIE's own version&quot; and exits <strong>without installing</strong> — the pinned extension version was never fetched, so the registry-mode PHP smoke validated whatever stale build happened to be present (or nothing). Use <code>pie install &quot;&lt;pkg&gt;:$VERSION&quot;</code> so the targeted release is actually installed. (alef 0.25.54)</li>

<li><strong>ci(publish): unblock the npm/Node publish under pnpm 11.8.0.</strong> The <code>node-bindings</code> job runs <code>setup-node-workspace</code> (which installs with <code>--no-frozen-lockfile</code>) and then <code>build-node-napi</code>, whose own <code>pnpm install --filter</code> re-enforces CI's default frozen-lockfile. The napi platform <code>optionalDependencies</code> are pinned to the not-yet-published release version, so they cannot be in the lockfile — pnpm 11.6.0 treated the redundant install as a no-op, but the 11.8.0 bump made it fail (<code>ERR_PNPM_OUTDATED_LOCKFILE</code>), dropping every Node build and the npm publish. Pass <code>install-deps: false</code> so the already-installed workspace is reused. (<code>.github/workflows/publish.yaml</code>)</li>

<li><strong>ci(homebrew): drop the macOS-Intel CLI block from the formula template.</strong> The CLI matrix no longer builds <code>x86_64-apple-darwin</code> (Apple Silicon only), but <code>scripts/publish/html-to-markdown.rb.tmpl</code> + <code>homebrew.json</code> still referenced <code>cli-x86_64-apple-darwin.tar.gz</code>, so &quot;Update Homebrew formulas&quot; failed (<code>no assets match the file pattern</code>) and the tap stayed on the prior version. Remove the macOS <code>on_intel</code> block; macOS is now arm-only. (<code>libhtml-to-markdown</code> is unchanged — the C FFI still ships an x86_64-apple-darwin archive.)</li>

</ul>

<h3>Changed</h3>

<ul>

<li><strong>chore(deps): re-pin <code>alef.toml.alef_version</code> to 0.25.54 and regenerate every binding, e2e suite, README, and API doc.</strong> Folds in the 0.25.51–0.25.54 generator fixes: the PHP PIE <code>pkg:version</code> install fix above; <strong>Go</strong> — unit/newtype-tuple enum constants emit serde wire values, a parameter named <code>result</code> no longer collides with the codegen variable, and <code>Option&lt;&amp;[u8]&gt;</code> returns generate correctly; <strong>R/extendr</strong> — cfg-variant dedup, registration entries drop the stray <code>#[cfg(...)]</code>, and opaque-method/<code>Option</code>/<code>Vec</code>/error returns convert properly; <strong>C#</strong> — corrected host-capsule native method name; <strong>Swift</strong> — <code>Package.swift</code> dependency argument order and e2e <code>harness_extras</code> product override; <strong>test_apps runner</strong> — declared <code>[crates.e2e.env]</code> vars are exported to the run command. Verified locally: both PIE fixes are present in the regenerated test_apps and the 3.6.19 bump is synced across all manifests.</li>

<li><strong>chore(precommit): scope <code>oxfmt</code>/<code>oxlint</code> away from generated <code>e2e/</code>+<code>test_apps/</code>.</strong> alef has no e2e/test_apps JS/TS formatter (<code>alef.toml [crates.e2e.format]</code> covers go/python/rust/c only), so <code>oxfmt</code> was the lone tool reformatting generated test JS, producing churn on every regenerate. Add the <code>^(e2e/|test_apps/)</code> exclude that <code>go-fmt</code>, <code>ruff-format</code>, and <code>golangci-lint</code> already carry; generated test JS now ships as alef emits it, matching <code>e2e/ruby</code>, <code>e2e/php</code>, etc. (<code>.pre-commit-config.yaml</code>)</li>

</ul>

<h2>[3.6.18] - 2026-06-20</h2>

<h3>Fixed</h3>

<ul>

<li><strong>ci(publish): unbreak Python wheels on every platform.</strong> The shared <code>build-python-wheels</code> action source-built libheif 1.23.0 (with <code>libde265</code>/<code>x265</code> codec headers) for <em>all</em> consumers because kreuzberg links <code>libheif-sys</code>. html-to-markdown does not use libheif, but inherited the build — which fails on the <code>manylinux2014</code> (CentOS 7 EOL) base whose yum repos no longer carry <code>libde265-devel</code>/<code>x265-devel</code> (<code>Error: Not tolerating missing names on install</code>). The action now gates the libheif build behind an opt-in <code>build-libheif</code> input (default off); h2m no longer builds it, so all Python wheels build again. (<code>kreuzberg-dev/actions@v1</code>)</li>

<li><strong>ci(publish): re-exclude <code>php8.5</code> + <code>macos-arm64</code>, restoring PHP publishing.</strong> v3.6.17 tried to build the php8.5 Apple-Silicon PIE asset on the <code>macos-14</code> runner (<a href="https://redirect.github.com/kreuzberg-dev/html-to-markdown/issues/333&quot;&gt;#333&lt;/a>), but <code>shivammathur/setup-php</code> cannot provision PHP 8.5 on arm64 on <em>any</em> macOS runner (the install leaves empty paths — <code>sed: : No such file</code>, <code>/php.ini: No such file</code>). That failing cell skipped <code>upload-php-pie-release</code>, dropping <strong>every</strong> PHP PIE asset (a v3.6.15-class regression). Restoring the exclusion republishes the PHP extension for all supported targets (PHP 8.2–8.5 on linux/macos-x86_64/windows, plus arm64-darwin for 8.2–8.4). <a href="https://redirect.github.com/kreuzberg-dev/html-to-markdown/issues/333&quot;&gt;#333&lt;/a> stays open pending an upstream php@8.5 arm64 formula. (<code>.github/workflows/publish.yaml</code>)</li>

</ul>

<h3>Changed</h3>

<ul>

<li><strong>chore(deps): re-pin <code>alef.toml.alef_version</code> to 0.25.50 and regenerate every binding, e2e suite, README, and API doc.</strong> Folds in the 0.25.50 cross-language visitor-codegen fixes that turn the chronically-red e2e visitor suites green: <strong>Node</strong> — the bridge now reads the externally-tagged <code>{ Custom: ... }</code>/<code>{ Error: ... }</code> payload key (was lowercased to <code>custom</code>/<code>error</code>, yielding <code>[object Object]</code>); <strong>Ruby</strong> — visitor callbacks take named params and interpolate <code>{placeholder}</code> templates; <strong>PHP</strong> — bare-string returns map to <code>Custom</code> for multi-payload result enums; <strong>Elixir</strong> — unit-variant atoms match the snake_case wire name (<code>:skip</code> no longer leaks as literal <code>&quot;Skip&quot;</code>); <strong>Swift</strong> — <code>visitBlockquote</code>'s <code>depth</code> is <code>UInt</code>, so the override satisfies the protocol. Verified locally: every language e2e suite passes and <code>alef verify</code> is clean.</li>

</ul>

<h2>[3.6.17] - 2026-06-19</h2>

<h3>Fixed</h3>

<ul>

<li><strong>ci(publish): stage Java natives under the <code>macos-*</code> RID the loader expects, fixing Java on all macOS.</strong> The <code>java-natives</code> matrix labelled the macOS cells <code>osx-aarch64</code> / <code>osx-x86_64</code>, which became the <code>natives/&lt;rid&gt;/</code> directory baked into the jar, but the loader (<code>NativeLib.resolveNativesRid</code>, alef <code>go_java_platform</code>) expects <code>macos-arm64</code> / <code>macos-x86_64</code>. The published jar therefore failed with <code>UnsatisfiedLinkError</code> on every macOS. Align the labels with the loader. (<code>.github/workflows/publish.yaml</code>)</li>

<li><strong>ci(publish): bundle the Dart native libraries into the published package.</strong> <code>assemble-dart-package</code> shipped the pub.dev tarball with no native libraries, so the loader fell back to a relative framework path that hardened runtimes reject — the package was unusable for every consumer. Add a <code>dart-natives</code> matrix that builds the <code>html-to-markdown-rs-dart</code> cdylib per platform and stages it into <code>lib/src/native/&lt;rid&gt;/</code> where the loader (<code>_alefHostRid</code>) looks. (<code>.github/workflows/publish.yaml</code>)</li>

<li><strong>ci(publish): build the PHP 8.5 macOS-arm64 extension on the <code>macos-14</code> runner (<a href="https://redirect.github.com/kreuzberg-dev/html-to-markdown/issues/333&quot;&gt;#333&lt;/a&gt;).&lt;/strong> <code>shivammathur/setup-php</code> only provisions PHP 8.5 on Apple Silicon via the <code>macos-14</code> runner, not <code>macos-latest</code> (15/26). The <code>php-extension</code> matrix used <code>macos-latest</code> and excluded php8.5/macos-arm64, so that PIE asset was never built. Build the macos-arm64 cell on <code>macos-14</code> and drop the exclusion so the <code>php8.5-arm64-darwin</code> PIE asset ships. (<code>.github/workflows/publish.yaml</code>)</li>

<li><strong>fix(task): refresh <code>go.sum</code> in the Go smoke test.</strong> <code>test-apps:smoke:go</code> failed with &quot;missing go.sum entry&quot; after a version bump because alef edits <code>go.mod</code> only. Run the targeted <code>go mod download &lt;module&gt;</code> Go suggests — it adds the entry without rewriting <code>go.mod</code>'s block form, which <code>download_ffi.sh</code> parses for the version. (<code>Taskfile.yaml</code>)</li>

<li><strong>test(ci): run the Java e2e step on macOS to cover native RID resolution.</strong> The Java e2e ran the e2e step only on ubuntu, so macOS-specific binding/native regressions (such as the RID mismatch above) were never exercised. Run it on macOS too. (<code>.github/workflows/ci-e2e.yaml</code>)</li>

</ul>

<h3>Changed</h3>

<ul>

<li><strong>chore(deps): re-pin <code>alef.toml.alef_version</code> to 0.25.49 and regenerate every binding, e2e suite, README, and API doc.</strong> Folds in the 0.25.45–0.25.49 generator fixes (incl. kotlin-android AGP 9 toolchain, swift bridge build, content-union accessors). Verified locally: <code>alef verify</code> is clean and <code>task alef:format</code> succeeds across all languages.</li>

<li><strong>chore(precommit,alef): standardize kotlin-android formatting on ktfmt <code>--kotlinlang-style</code>.</strong> Drop the conflicting prek <code>ktlint</code> hook (its always-format mode fought <code>ktfmt</code> over blank-line-after-brace and rewrote alef's <code>///</code> doc comments to <code>// /</code>, breaking <code>alef verify</code>), switch <code>alef.toml</code> kotlin-android format/check from gradle-<code>ktlintFormat</code> to <code>ktfmt</code> so alef and prek agree, and exclude the vendored Gradle wrapper from shellcheck. detekt remains for static analysis. (<code>.pre-commit-config.yaml</code>, <code>alef.toml</code>)</li>

<li><strong>chore(alef): close formatter-coverage gaps for generated Go and Zig.</strong> Add a <code>gofmt -w</code> format hook for <code>packages/go</code>/<code>e2e/go</code> (alef's Go emitter output needs canonical re-indentation), and extend the Zig formatter/check to cover <code>build.zig</code> in addition to <code>src</code>. (<code>alef.toml</code>)</li>

</ul>

<!-- raw HTML omitted -->

</blockquote>

<p>... (truncated)</p>

</details>

<details>

<summary>Commits</summary>
<ul>

<li><a href="https://github.com/kreuzberg-dev/html-to-markdown/commit/f2798451b7a88fe13cbc75acf151f7afe74fdbc8&quot;&gt;&lt;code&gt;f279845&lt;/code&gt;&lt;/a> chore(release): substitute Swift checksum for 3.6.20</li>

<li><a href="https://github.com/kreuzberg-dev/html-to-markdown/commit/72ee0adbf6350123429fffad0181ec831b4db29b&quot;&gt;&lt;code&gt;72ee0ad&lt;/code&gt;&lt;/a> chore(release): regenerate v3.6.20 against released alef 0.25.58</li>

<li><a href="https://github.com/kreuzberg-dev/html-to-markdown/commit/1102a81aaf237a85c37f566d6367c9fcffebbc95&quot;&gt;&lt;code&gt;1102a81&lt;/code&gt;&lt;/a> chore(release): v3.6.20</li>

<li><a href="https://github.com/kreuzberg-dev/html-to-markdown/commit/3da03215392a85a2648549f13ab1c3d12cdfac85&quot;&gt;&lt;code&gt;3da0321&lt;/code&gt;&lt;/a> fix(cli-proxy): resolve ruff/mypy/oxlint debt + apply formatters</li>

<li><a href="https://github.com/kreuzberg-dev/html-to-markdown/commit/8a5203b7d67c212b2c64bbb8c0825ad33c730c41&quot;&gt;&lt;code&gt;8a5203b&lt;/code&gt;&lt;/a> chore: align pre-commit hooks to canonical polyglot set (v2.3.0)</li>

<li><a href="https://github.com/kreuzberg-dev/html-to-markdown/commit/24a7f7cb6b5d128235c66b15b0df2a7fc980f96a&quot;&gt;&lt;code&gt;24a7f7c&lt;/code&gt;&lt;/a> fix(ci): drop macOS-Intel CLI block from homebrew formula</li>

<li><a href="https://github.com/kreuzberg-dev/html-to-markdown/commit/c262827626d4bea436fda6ec36b6976ed72666ef&quot;&gt;&lt;code&gt;c262827&lt;/code&gt;&lt;/a> fix(ci): skip redundant frozen pnpm install in node publish</li>

<li><a href="https://github.com/kreuzberg-dev/html-to-markdown/commit/1a3a1384d2a98fc0c8e9299b5ffad78e06b0b128&quot;&gt;&lt;code&gt;1a3a138&lt;/code&gt;&lt;/a> chore(deps): upgrade java/python deps, sync r/ruby native lockfiles to 3.6.19</li>

<li><a href="https://github.com/kreuzberg-dev/html-to-markdown/commit/12cd03829a75037b18dac3d386d08e3bf6c8bd5b&quot;&gt;&lt;code&gt;12cd038&lt;/code&gt;&lt;/a> docs: restructure root README to lean layout, drop banner, add star CTA gif</li>

<li><a href="https://github.com/kreuzberg-dev/html-to-markdown/commit/50e52e30c5abfb82a032db3359f490dad000b709&quot;&gt;&lt;code&gt;50e52e3&lt;/code&gt;&lt;/a> chore(release): v3.6.19</li>

<li>Additional commits viewable in <a href="https://github.com/kreuzberg-dev/html-to-markdown/compare/v3.2.6...v3.6.20&quot;&gt;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 commands and options


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)

[dependabot]

Superseded by #56.