Repository navigation
Update Rust crate lol_html to v3 - #53
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/lol_html-3.x
branch
from
July 21, 2026 00:06
476ad52 to
f7f42ca
Compare
renovate
Bot
force-pushed
the
renovate/lol_html-3.x
branch
from
August 1, 2026 18:51
f7f42ca to
bd5c90c
Compare
renovate
Bot
force-pushed
the
renovate/lol_html-3.x
branch
from
August 12, 2026 04:53
bd5c90c to
e772b85
Compare
renovate
Bot
force-pushed
the
renovate/lol_html-3.x
branch
from
September 3, 2026 00:57
e772b85 to
66e0610
Compare
renovate
Bot
force-pushed
the
renovate/lol_html-3.x
branch
from
October 1, 2026 00:15
66e0610 to
f4d470f
Compare
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
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.
This PR contains the following updates:
2.0.0→3.0.0Release Notes
cloudflare/lol-html (lol_html)
v3.0.1Compare Source
the preceding tag matched no selector.
[HREF]silently matchednothing and
[HREF=x]was rejected as a namespaced selector.:nth-of-type()counting custom elements spelled with different ASCII case asdistinct types.
v3.0.0Compare Source
MemorySettings::with_graceful_bail_out_on_memory_limit_exceeded(): when set, therewriter flushes every input byte it has received but not yet emitted to the sink (as-is)
before returning
MemoryLimitExceededError, so callers can continue the response bywriting subsequent bytes directly to their downstream sink instead of breaking it.
Settings::with_graceful_bail_out_on_content_handler_error(): symmetric to thememory setting above, but for
RewritingError::ContentHandlerError. When set, therewriter flushes remaining input bytes before propagating a handler error, preserving
the response. Currently exposed via the Rust API only; the C API still uses the original
behavior.
Settings::append_bail_out_handler()and the matchingbail_out!macro,BailOutrewritable unit, andBailOutHandler/BailOutHandlerSendtype aliases.Bail-out handlers fire immediately before the raw flush of remaining unparsed input on a
graceful bail-out (memory or content-handler error). Handlers receive the
RewritingErrorand aBailOutthrough which they can append final bytes to the sinkvia
BailOut::append(content, content_type). Intended for handlers that buffer stateacross the document (e.g. text-buffering handlers that defer emission) and need to
flush that state on bail-out.
RewritingError#[non_exhaustive]so future error variants can be added withouta major version bump. External callers can still
matchon it, but must include acatch-all
_ =>arm.Settings,MemorySettingsandRewriteStrSettingsto use a consuming-builderAPI. Fields are now private; construction is via
::new()plus chainedwith_*settersand
append_*methods for the content-handler vectors. This makes future field additionsnon-breaking. Migration:
integration_testto_integration_test. The leadingunderscore signals to
cargo-semver-checksand similar tools that the feature is notpart of the public API.
Comment::set_textnow also rejects--!>, a leading>, and a leading->, whichWHATWG-conformant browsers treat as comment terminators. Previously only
-->wasrejected, so a caller passing attacker-influenced data could let an attacker break out
of the comment and inject HTML (security fix).
Configuration
📅 Schedule: (UTC)
* 0-3 * * 1)🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.