Metadata revisions for expiring-cache-map-0.0.5.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 (expiring-cache-map-0.0.5.0-r2) 2022-07-04T08:50:00Z elblake e297a632a70e2ec89d9374396ede689c1ab60630f1b233711f3a8ff5075750f6
  • 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.0-r1) 2014-12-01T12:49:14Z elblake 2ea22d4d0feca220e3b1a86755789de843452585be3d3c795988db34d89e3204
  • 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.0-r0) 2014-11-24T19:50:12Z elblake baed867b34a686ae1f8860daa82ed86a6cea017519626f5156815d21f8a131a4