Metadata revisions for expiring-cache-map-0.0.5.3

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 (expiring-cache-map-0.0.5.3-r2) 2022-07-04T08:49:21Z elblake f4f23b6a2a9af9294493176736ee4a310aab93f8c3eec62eb6dea8d39a482ff2
  • Changed homepage from

    https://github.com/elblake/expiring-cache-map
    to
    https://codeberg.org/elblake/expiring-cache-map

  • Changed bug-reports from

    https://github.com/elblake/expiring-cache-map/issues
    to
    https://codeberg.org/elblake/expiring-cache-map/issues

-r1 (expiring-cache-map-0.0.5.3-r1) 2014-12-01T12:48:37Z elblake e3990400b7a0fc202dd68fb9d4fea926af9fdaeb34d2e9cf7e04eb3c2a03da4c
  • Changed the library component's library dependency on 'hashable' from

    >=1.0.1.1 && <1.2
    to
    >=1.0.1.1

  • Changed the test suite 'test-threads' component's library dependency on 'hashable' from

    >=1.0.1.1 && <1.2
    to
    >=1.0.1.1

  • Changed the test suite 'test-sequence' component's library dependency on 'hashable' from

    >=1.0.1.1 && <1.2
    to
    >=1.0.1.1

-r0 (expiring-cache-map-0.0.5.3-r0) 2014-11-30T07:53:29Z elblake 023afc12d324512f2853cf8901fb2cc50614dbe9c1cdaa1ace5aa816a0dfba7b