Skip to content

New projects depend on mob ~> 0.9.25 and mob_dev ~> 0.7.30 (MOB-493) - #112

Merged
GenericJam merged 3 commits into
masterfrom
mob-493-floors
Oct 23, 2026
Merged

GenericJam merged 3 commits into
masterfrom
mob-493-floors

Conversation

@GenericJam

Copy link
Copy Markdown
Owner

Blocking finding from the 0.6.16 release-gate review (Codex): the generated floors (mob ~> 0.9.18, mob_dev ~> 0.7.12) would let a new project resolve mob_dev 0.7.29, whose runtime is OTP 29.0 (critical TLS CVE-2026-89422 and CVE-2026-55953) and which pushes the host's ssl over the runtime's, even though the generated .tool-versions pins erlang 29.1.2. mob_dev 0.7.30 ships the otp-d199a49a runtime (erts-17.1.1), which needs mob 0.9.25.

The generator comment, the test, AGENTS.md and the CHANGELOG are updated. Tests: 532/532 (the two --local tests need MOB_DEV_DIR in a worktree). Merge after mob_dev 0.7.30 is on Hex.

@GenericJam

Copy link
Copy Markdown
Owner Author

Review: reviewer subagent (Codex usage-limited until 4:04 AM): SHIP. Its should-fix (an Upgrading note for existing apps) and nitpick (name the platforms) are applied. Release rungs 5 and 6 pass from this head's packed Hex package: the installed archive generated an app that resolves mob 0.9.25 / mob_dev 0.7.30; mix mob.release --android built the AAB; bundletool installed it on a physical Moto G power 2021; logcat shows ERTS dir erts-17.1.1 and the home screen rendered, with no crashes.

@GenericJam
GenericJam merged commit 274a366 into master Oct 23, 2026
3 checks passed
@GenericJam
GenericJam deleted the mob-493-floors branch October 23, 2026 06:21
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