Hi, and thanks for maintaining enough_mail — we rely on it for IMAP-based workflows in a production Flutter app.
The ask: would it be possible to publish the current main (2.2.3, or the 2.2.4 prepared in #279) to pub.dev?
Why it matters: the latest published version, 2.1.7, constrains xml: ">=6.0.0 <7.0.0", while main already allows xml <8.0.0 (2.2.x). Because pub resolves the whole dependency graph together, that single <7.0.0 cap in the published version currently pins xml at 6.x for every app that depends on enough_mail, which in turn blocks a surprisingly large cluster of popular packages:
pdf ≥ 3.13.0 and syncfusion_flutter_pdf ≥ 34.x require xml >=7.0.1 → held backsyncfusion_flutter_pdfviewer 33.x (the last resolvable) caps device_info_plus at ^12 → device_info_plus 13 held backdevice_info_plus 12 caps win32 at ^5 → win32 6, win32_registry 3, package_info_plus 10, share_plus 13, network_info_plus 8, flutter_secure_storage 11 all held back- transitively even patch releases like
geolocator 14.0.3 (via geolocator_linux → package_info_plus ^10)
In our app that's 34 packages stuck on older versions, all tracing back to this one published constraint. The fix already exists on main — it just needs a dart pub publish.
Happy to help with anything that would make the release easier (testing a prerelease, validation on our IMAP flows, etc.). Thanks a lot!
Hi, and thanks for maintaining enough_mail — we rely on it for IMAP-based workflows in a production Flutter app.
The ask: would it be possible to publish the current
main(2.2.3, or the 2.2.4 prepared in #279) to pub.dev?Why it matters: the latest published version, 2.1.7, constrains
xml: ">=6.0.0 <7.0.0", whilemainalready allowsxml <8.0.0(2.2.x). Because pub resolves the whole dependency graph together, that single<7.0.0cap in the published version currently pinsxmlat 6.x for every app that depends on enough_mail, which in turn blocks a surprisingly large cluster of popular packages:pdf≥ 3.13.0 andsyncfusion_flutter_pdf≥ 34.x requirexml >=7.0.1→ held backsyncfusion_flutter_pdfviewer33.x (the last resolvable) capsdevice_info_plusat ^12 →device_info_plus13 held backdevice_info_plus12 capswin32at ^5 →win326,win32_registry3,package_info_plus10,share_plus13,network_info_plus8,flutter_secure_storage11 all held backgeolocator14.0.3 (viageolocator_linux→package_info_plus^10)In our app that's 34 packages stuck on older versions, all tracing back to this one published constraint. The fix already exists on
main— it just needs adart pub publish.Happy to help with anything that would make the release easier (testing a prerelease, validation on our IMAP flows, etc.). Thanks a lot!