Repository navigation
release: 0.1.1 — mint security floor >= 1.10.2 + lock bumps + version/changelog - #2
Merged
Merged
Conversation
… 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).
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.
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
mint >= 1.10.2— mint reaches every consumer transitively (req → finch → mint, all non-optional) and the published tarball ships nomix.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 viamix hex.build: the published requirements now includemint >= 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 precommitgreen — 45 passed, 0 skipped; credo strict clean (128 mods/funs);--warnings-as-errorsclean;mix hex.auditreports ONLY the accepted cowlib -43966.After merge:
git tag v0.1.1 && git push origin v0.1.1→.github/workflows/release.ymlcompiles, tests, and runsmix hex.publish --yes.Ref: ghostex-10a (investigation: ghostex-545).