Metadata revisions for constrained-category-0.1.0.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 (constrained-category-0.1.0.0-r2) 2020-04-10T04:54:37Z MatthewFarkasDyck 8c7850faf42ecbefc611a7d6e0e08e519285f3d1bdc25b491c391d82ff2d4bfe
  • Removed source-repository

    source-repository head
        type:     git
        location: https://github.com/strake/constrained-category.hs
    

-r1 (constrained-category-0.1.0.0-r1) 2020-02-11T07:23:53Z MatthewFarkasDyck 43b7789b2e0ad2d1e6a15ece9dd4ee1aa9ee31a999b651f2846dc9b6ffcff3cd
  • Changed source-repository from

    source-repository head
        type:     git
        location: https://github.com/githubuser/constrained-category.hs
    
    to
    source-repository head
        type:     git
        location: https://github.com/strake/constrained-category.hs
    

-r0 (constrained-category-0.1.0.0-r0) 2018-12-30T18:56:31Z MatthewFarkasDyck c76bdc82639d80d7dde78dabb2ea967d65c22b3f9eb007ec6a51adab8e8f814b