Metadata revisions for safe-exceptions-checked-0.1.0

Package maintainers and Hackage trustees are allowed to edit certain bits of package metadata after a release, without uploading a new tarball. Note that the tarball itself is never changed, just the metadata that is stored separately. For more information about metadata revisions, please refer to the Hackage Metadata Revisions FAQ.

No. Time User SHA256
-r3 (safe-exceptions-checked-0.1.0-r3) 2018-01-25T20:21:59Z mitchellwrosen ae142f284c6b102f0e7606a69a5719f4f72771d9cc353af72fa4484326689100
  • Changed the library component's library dependency on 'safe-exceptions' from

    >=0.1.1 && <0.1.7
    to
    >=0.1.1 && <0.1.8

-r2 (safe-exceptions-checked-0.1.0-r2) 2017-07-05T18:35:40Z mitchellwrosen 7f473c090b7adf74d2c0afa23ab6ef37d929130954af5d82f0a47e947d99dca1
  • Changed the library component's library dependency on 'safe-exceptions' from

    >=0.1.1 && <0.1.6
    to
    >=0.1.1 && <0.1.7

-r1 (safe-exceptions-checked-0.1.0-r1) 2017-03-07T19:26:05Z mitchellwrosen eb73db3a495242ccc5bea2cc4aef48e91693dcd43301ea9e531f1c0aaea4d6da
  • Changed the library component's library dependency on 'safe-exceptions' from

    >=0.1.1 && <0.1.5
    to
    >=0.1.1 && <0.1.6

-r0 (safe-exceptions-checked-0.1.0-r0) 2017-01-28T19:42:52Z mitchellwrosen aac51e0b98755ae46cddd0bb64206f62eca92e3b921b9e3805bd5a34f37a0524