Skip to content

release: 0.1.1 — mint security floor >= 1.10.2 + lock bumps + version/changelog - #2

Merged
jgnagy merged 2 commits into
mainfrom
fix/plug_crypto-2.2.1-ghostex-547
Oct 26, 2026
Merged

jgnagy merged 2 commits into
mainfrom
fix/plug_crypto-2.2.1-ghostex-547

Conversation

@jgnagy

@jgnagy jgnagy commented Oct 26, 2026

Copy link
Copy Markdown
Member

The 0.1.1 security release, continued from merged PR #1 (this PR adds the two commits that landed on the branch after that merge): the mint floor and the release prep.

Security

  • Runtime floor mint >= 1.10.2 — mint reaches every consumer transitively (req → finch → mint, all non-optional) and the published tarball ships no mix.lock, so the constraint must ride the package metadata. The floor clears all six open mint advisories (EEF-CVE-2026-82728/-82729 HIGH, -82672, -91043 HIGH, -92103, -94194) and keeps consumers off affected 1.9.3/1.10.0/1.10.1. Verified via mix hex.build: the published requirements now include mint >= 1.10.2 (app: mint).
  • jose → 1.11.13 (lock) — clears 8 advisories EEF-CVE-2026-65625…-65632 incl. HIGH -65629 (fix released 2026-10-26).
  • cowlib → 2.21.0 (lock) — clears -43971/-43969; the unfixable -43966 remains, documented as accepted in AGENTS.md (no patched release exists; test-stack-only, off the runtime path).

Release prep: @version → 0.1.1; CHANGELOG gains the 0.1.1 section (Keep-a-Changelog) — it also records PR #1's plug_crypto 2.2.1 bump, which this changelog entry retroactively documents; the accepted-advisory note refreshed.

Gates (verbatim): mix precommit green — 45 passed, 0 skipped; credo strict clean (128 mods/funs); --warnings-as-errors clean; mix hex.audit reports ONLY the accepted cowlib -43966.

After merge: git tag v0.1.1 && git push origin v0.1.1 → .github/workflows/release.yml compiles, tests, and runs mix hex.publish --yes.

Ref: ghostex-10a (investigation: ghostex-545).

… entries (ghostex-10a)

mint is a runtime transitive dependency of the published package
(req -> finch -> mint) and the hex tarball ships no mix.lock, so a
consumer can still resolve the vulnerable 1.9.3. Constrain mint to
>= 1.10.2 as a runtime dep so the package requirement forces consumers
off 1.9.3/1.10.0/1.10.1; that floor clears all six mint advisories
(EEF-CVE-2026-82729, -82672, -91043 (HIGH), -92103, -94194 and -82728
(HIGH)).

Lock bumps: mint 1.9.3 -> 1.11.0, hpax 1.0.4 -> 1.1.0, cowlib
2.19.0 -> 2.21.0 (clears EEF-CVE-2026-43971 and -43969), jose
1.11.12 -> 1.11.13 (clears the eight jose advisories EEF-CVE-2026-65625
through -65632, including the HIGH -65629).
Bump the version to 0.1.1, add the Keep a Changelog 0.1.1 section
(Security / Changed / Documentation) and refresh the stale
accepted-advisory note in AGENTS.md: cowlib 2.21.0 is now locked and
clears EEF-CVE-2026-43971 and EEF-CVE-2026-43969, so only
EEF-CVE-2026-43966 remains accepted (no patched cowlib release yet).
@jgnagy
jgnagy merged commit 2b451fd into main Oct 26, 2026
1 check passed
@jgnagy
jgnagy deleted the fix/plug_crypto-2.2.1-ghostex-547 branch October 26, 2026 23:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant