Metadata revisions for armor-0.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
-r4 2019-09-22T20:01:35Z DougBeardsley 89620b14aeb1ae058e88525f892e1deb901680ee53bcaceec924737543c2d2ee
  • Changed the library component's library dependency on 'lens' from

    >=4.16 && <4.17
    to
    >=4.16 && <4.19

  • Changed the test suite 'testsuite' component's library dependency on 'hspec' from

    >=2.4 && <2.7
    to
    >=2.4 && <2.8

-r3 2019-01-20T11:21:49Z DougBeardsley a74a6de67ce7a2e0ca36209543d1dfb7c1a63ab0e497d4ba947d3358b4c97aaa
  • Changed category from

    Data
    to
    Data,Testing

-r2 2019-01-20T11:18:40Z DougBeardsley 6f95bd6588e7264126fd9a7fa482fc463f6d1c6c014d36fd29748d32c97e0905
  • Changed synopsis from

    Armor data structures against serialization backwards compatibility problems
    to
    Prevent serialization backwards compatibility problems using golden tests

-r1 2018-12-21T21:12:00Z DougBeardsley 53135a95d3744c35939c7c7534eaed751d9db2e693d93c1d71f52b00d9ecb61c
  • Changed the test suite 'testsuite' component's library dependency on 'hspec' from

    >=2.4 && <2.5
    to
    >=2.4 && <2.7

-r0 2018-03-14T22:46:00Z DougBeardsley 7c97ba433c856f2d2441def69dd7090764616f58f0e76f63cdb6c2b2eb2be6bf