Triggering a documentation update for a Hackage package

Question

I have two releases which were accidentally uploaded before some of their dependencies:

Since then their dependencies have long been satisfied, however the documentation for them has not been generated to this day.

How can I trigger a reevaluation of those releases by Hackage? Is uploading a new release the only solution to such a silly problem?

I could find nothing related in the "Maintainer's corner".

You could try uploading it with the same version again. Not sure if it works, just a guess. — Tobias Brandt, Apr 01 '14 at 18:15
@TobiasBrandt Nope. That won't work due to [this problem](http://stackoverflow.com/q/21724729/485115). — Nikita Volkov, Apr 01 '14 at 18:22

score 2 · Answer 1 · answered Apr 09 '14 at 01:05

From New features in Hackage 2.

Documentation can be uploaded by any suitably-authorised user, not just a single dedicated documentation build bot. In particular maintainers can upload documentation bundles if the doc build bots fail to do so.

There's a Github Issue complaining that the documentation for this is incomplete, and linked from this thread is a shell script that automatically builds, bundles, and uploads documentation for you. Give it a try, and post results.

Triggering a documentation update for a Hackage package

1 Answers1