Repository navigation
deps: mint 1.11.0, clearing three advisories - #111
Merged
Merged
Conversation
mix deps.audit reported three against mint 1.10.1:
EEF-CVE-2026-91043 (HIGH) HPACK-indexed cookie fields in HTTP/2 responses
bypass max_header_list_size and exhaust client memory
EEF-CVE-2026-94194 (MEDIUM) chunked framing applied when chunked is not the
final transfer coding, enabling response smuggling
through intermediaries
EEF-CVE-2026-92103 (MEDIUM) HTTP/2 frames buffered up to 16 MiB before
max_frame_size is enforced
mint is transitive, through finch, whose requirement is ~> 1.8 and already admits
1.11.0, so no requirement in mix.exs had to change and none did.
hpax 1.0.4 => 1.1.0 comes with it and is not optional: mint 1.11.0 requires
hpax ~> 1.1, where 1.10.1 required ~> 0.1.1 or ~> 0.2.0 or ~> 1.0. Those two
lines are the whole of the lock change.
THIRD_PARTY_LICENSES.md is regenerated with `mix trinity.third_party_licenses
--write`, which the gate checks against the bill of materials. It is two lines,
the same two versions, and neither licence changed: both remain Apache-2.0.
Signed-off-by: Ayla Croft <aylacroft@proton.me>
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.
mix deps.auditreported three advisories againstmint 1.10.1, published upstream since the last green run. They were red onmain, not introduced by any open branch.max_header_list_sizeand exhaust client memorymax_frame_sizeis enforcedThe change
mint 1.10.1 => 1.11.0andhpax 1.0.4 => 1.1.0. Nothing else in the lock moved.mix.exsdid not change, and did not need to.mintis transitive, throughfinch:~> 1.8already admits 1.11.0, so there was no requirement to relax and none was added. Neithermintnorhpaxis named inmix.exs.The
hpaxbump is forced, not incidental:mint 1.11.0 requires
hpax ~> 1.1and the lock held 1.0.4, so the two lines are the minimum that resolves.Proof
One extra file, and why
THIRD_PARTY_LICENSES.md, two lines, the same two versions. The gate refuses a bill of materials that does not match it:Regenerated with that command rather than edited by hand. Neither licence changed:
mintandhpaxare both still Apache-2.0. Nothing underlib/, no source change of any kind, no slice id.A pre-existing flake seen on the way, not fixed here
One
mix gaterun failed onTrinity.Skills.RegistryTest, "AC3: a SKILL.md edited on disk is in the registry within 2 s without a rescan", attest/trinity/skills/registry_test.exs:118. It is load-sensitive by construction: it polls1..100withProcess.sleep(20)and asserts the total stays within 2 s, so under full-suite parallelism the sleeps overrun. Run on its own it passed 5 times out of 5, at 316 to 317 ms each. Unrelated to this bump, and a candidate identity for the uncaptured single failure reported on #110. Left alone; say the word if you want it opened.Not merged.