Repository navigation
chore(release): prepare v0.6.0 - #186
Merged
Merged
Conversation
chaliy
marked this pull request as ready for review
October 23, 2026 21:48
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Prepare Fetchkit 0.6.0 with published Markkit >=0.1.1, Tokio >=1.54.1, the patched PDF/TLS graph, and locked Cargo publishing. Release tags target the exact triggering commit. Preserve and document the document conversion, HTML processing, and agent discovery changes accumulated on main since 0.5.0.
Why
A root-only Markkit git patch does not protect packaged downstream consumers. The release also removes the Tokio AsyncFd unsoundness reported in RUSTSEC-2026-0386. Public API changes already on main require a minor release rather than 0.5.1.
Before / After
84d943a6deeb8cc6c6f632531aaf4f1c62275239: zero vulnerability/unsound findings; existing unmaintained notices remain for dlopen_derive and ttf-parser. No direct AsyncFd call was found in Fetchkit; exploit reachability was not established.Risk
Medium: the release includes previously merged public API changes. Exhaustive FetchOptions literals need new fields or Default; construct DefaultFetcher with new()/default(); enable docs-office explicitly for PPTX/XLSB. See CHANGELOG.md and docs/security.md. Existing downstream locks still require updates for transitive TLS dependencies. The default HTTP client uses platform trust; OS CA package maintenance remains an operator responsibility. No Python/npm release is configured or added.
Validation
cargo fmt --all -- --check; workspace/all-target Clippy with warnings denied.docs-all,docs-office,bot-auth,render-rakers): tests and Clippy passed. The externallive-testssuite is not enabled by that deterministic matrix..cratebuilt and exercised by an independent consumer: HTML, registry Markkit DOCX, and deeply nested PDF. Package and fresh-consumer audits: zero vulnerabilities.Checklist