Metadata revisions for purescript-0.6.1

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 (purescript-0.6.1-r2) 2015-06-14T12:33:01Z AdamBergmark f9feac6fca6d1c9e2b68b83d9829a5f3474862761722e2bb00d5b5d9d40fd1e2
  • Changed the library component's library dependency on 'base' from

    >=4 && <5
    to
    >=4.7 && <5

-r1 (purescript-0.6.1-r1) 2015-06-04T09:24:10Z AdamBergmark 22b0dda6f2537649ca7eb524e4986be514f4a4e42711204dcba132a990122105
  • Changed the library component's library dependency on 'utf8-string' from

    >=0
    to
    <1

  • Changed the executable 'psc' component's library dependency on 'utf8-string' from

    >=0
    to
    <1

  • Changed the executable 'psc-make' component's library dependency on 'utf8-string' from

    >=0
    to
    <1

  • Changed the executable 'psci' component's library dependency on 'utf8-string' from

    >=0
    to
    <1

  • Changed the executable 'psc-docs' component's library dependency on 'utf8-string' from

    >=0
    to
    <1

  • Changed the executable 'hierarchy' component's library dependency on 'utf8-string' from

    >=0
    to
    <1

  • Changed the test suite 'tests' component's library dependency on 'utf8-string' from

    >=0
    to
    <1

-r0 (purescript-0.6.1-r0) 2014-11-18T00:47:23Z PhilFreeman 56b58f6961b3af00be584b9ed7daf4eaa8cb4164ab820d2decb913128bc6063c