Problem
Individual fixes are insufficient: the running audit image already includes earlier local upstream fixes. v3.0.0 must load from documented dependencies and reproduce the supported tool behavior without ad hoc patches.
Found during the 2026-09-20 FAMIXNGSQL/Moose 13 compatibility audit.
Implementation scope
Integrate reviewed fork commits with immutable dependency pins, add compatibility smoke tests to CI, document breaking naming/API changes and supported versions, and repeat the full live-model acceptance audit. Include existing generation issue #8. Do not publish the release until every milestone issue is resolved.
Implementation PR target: deem0n/FAMIXNGSQL, in the deem0n fork first. Keep this issue separate from the other v3.0.0 fixes. The PR must explain the previous failure, resulting behavior, compatibility implications, and actual validation.
Acceptance criteria and tests
Clean Pharo 13 and Moose 13 CI with PostgreSQL 15; full package tests; metamodel regeneration produces no unexpected changes; MSE round trips; installed-tool matrix; complete mi model identities/relations; no database artifacts in GitHub; all prerequisite PRs merged and CI green.
Release
Part of the v3.0.0 milestone. An open PR is not a completed fix; release qualification is tracked separately.
Implementation
#32
Combined qualification: #32. The implementation is available for review; this issue remains open until its integrated release acceptance is verified.
Verified candidate CI
SQL qualification head a2da310 passes 244 Moose 13 tests and 85 Pharo 13 tests against PostgreSQL 15: https://github.com/deem0n/FAMIXNGSQL/actions/runs/35537847634. Famix and MooseIDE fork matrices also passed. Prior namespace/Fame fixes are included via Famix #4/#5. The dedicated namespace workflow was removed as requested; its seven tests remain and run in the combined Moose job.
Still open: reviews/merges, final mi reimport and interactive acceptance at final pins, then release promotion. No v3 tag has been published.
Problem
Individual fixes are insufficient: the running audit image already includes earlier local upstream fixes. v3.0.0 must load from documented dependencies and reproduce the supported tool behavior without ad hoc patches.
Found during the 2026-09-20 FAMIXNGSQL/Moose 13 compatibility audit.
Implementation scope
Integrate reviewed fork commits with immutable dependency pins, add compatibility smoke tests to CI, document breaking naming/API changes and supported versions, and repeat the full live-model acceptance audit. Include existing generation issue #8. Do not publish the release until every milestone issue is resolved.
Implementation PR target: deem0n/FAMIXNGSQL, in the deem0n fork first. Keep this issue separate from the other v3.0.0 fixes. The PR must explain the previous failure, resulting behavior, compatibility implications, and actual validation.
Acceptance criteria and tests
Clean Pharo 13 and Moose 13 CI with PostgreSQL 15; full package tests; metamodel regeneration produces no unexpected changes; MSE round trips; installed-tool matrix; complete mi model identities/relations; no database artifacts in GitHub; all prerequisite PRs merged and CI green.
Release
Part of the v3.0.0 milestone. An open PR is not a completed fix; release qualification is tracked separately.
Implementation
#32
Combined qualification: #32. The implementation is available for review; this issue remains open until its integrated release acceptance is verified.
Verified candidate CI
SQL qualification head a2da310 passes 244 Moose 13 tests and 85 Pharo 13 tests against PostgreSQL 15: https://github.com/deem0n/FAMIXNGSQL/actions/runs/35537847634. Famix and MooseIDE fork matrices also passed. Prior namespace/Fame fixes are included via Famix #4/#5. The dedicated namespace workflow was removed as requested; its seven tests remain and run in the combined Moose job.
Still open: reviews/merges, final mi reimport and interactive acceptance at final pins, then release promotion. No v3 tag has been published.