Metadata revisions for binary-tagged-0.1.4.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
-r2 (binary-tagged-0.1.4.0-r2) 2016-12-05T09:43:56Z phadej 57d5ca07145d261bf9f8785f90e626cd8ecdedcf87fc00e087b292cb52539504
  • Changed the library component's library dependency on 'generics-sop' from

    >=0.1 && <0.3
    to
    >=0.1 && <0.2.3.0

-r1 (binary-tagged-0.1.4.0-r1) 2016-08-08T08:22:30Z phadej 0448d0fe13530497a639b2bd8fc290522fa526aee5e3486bc15003797cd84bc7
  • Changed the library component's library dependency on 'aeson' from

    >=0.8 && <0.12
    to
    >=0.8 && <1.1

  • Changed the test suite 'binary-tagged-test' component's library dependency on 'aeson' from

    >=0.8 && <0.12
    to
    >=0.8 && <1.1

  • Changed the benchmark 'binary-tagged-bench' component's library dependency on 'aeson' from

    >=0.8 && <0.12
    to
    >=0.8 && <1.1

-r0 (binary-tagged-0.1.4.0-r0) 2016-04-12T07:18:37Z phadej 65ad0b97a568f35720fb0ba252701049fc8e84b9732757a8727a7cabcd9b9640