The PVP does at the moment not give any advice about SafeHaskell. E.g. it does not say that if you make a previously Safe module unsafe, then you need a major version bump.
Why major bump? Because then import safe statements suddenly error out, and downstream packages become unbuildable.
In directory-1.3.8.0, the module System.Directory is no longer Safe, as it used to be in 1.3.7.*. Thus the new release should rather have been directory-1.4.0.0. Being released as 1.3.8.0, packages using directory < 1.4 and import safe System.Directory are now broken and need a revision.
The PVP does at the moment not give any advice about SafeHaskell. E.g. it does not say that if you make a previously
Safe
module unsafe, then you need a major version bump.Why major bump? Because then
import safe
statements suddenly error out, and downstream packages become unbuildable.In the wild:
In
directory-1.3.8.0
, the moduleSystem.Directory
is no longerSafe
, as it used to be in1.3.7.*
. Thus the new release should rather have beendirectory-1.4.0.0
. Being released as1.3.8.0
, packages usingdirectory < 1.4
andimport safe System.Directory
are now broken and need a revision.