Updating to announce a whole bunch of new features in the latest redeploy, with a few yet to come. This release includes a bunch of work from GSoC students, as well as a few other big-ticket items, and some various small fixes.
The biggest highlight is reverse-dependencies, which are finally here after years of attempts. Janus Troelsen re-thought the problem space to make an order-of-magnitude improvement in memory footprint, which means that we can finally provide this much requested feature.
A fun and noticeable change is that hackage now has a ânight modeâ color scheme enabled when your browser is set to request it. Thanks to Peter Becich for that!
Also included is a ton of GSoC work from Alias Qli and OndĆej KubĂĄnek (though the latterâs work on a âhackage-rankâ feature has not yet been merged). Notably, hackage now has an improved user account management page (reach it from User accounts | Hackage). You can now self-update your name and email address, and even more excitingly, opt into notification emails. You can now request notification when a maintainer is added to a package you maintain, a metadata revision is performed, a tag is proposed to be added, or when a docbuilder run finishes. For now, youâll need to opt-in explicitly, since its not clear if existing hackage users will want to start getting a bunch of new emails all of a sudden.
Along with smaller bugfixes, and the usual dependency bumps and CI fixes (thanks Andreas Abel and Peter for all your help on that!) here are some other changes of note:
improvements to the sitemap to help guide google search (and searchbox metadata)
improvements to rendering of markdown
allows syntax from cabal 3.8
maintainers can disable tests being run by the docbuilder
display logs for docbuilder-run tests
Updates to accepted licenses (allowed both from osi and fsf lists)
better warnings on deprecated versions
maintainers listed on package pages
captcha for user registration (should reduce spam registrations we get hammered with)
remove filtering 00-index for cabal version < 2.0 hack (not a big deal, but makes some weird corner cases less weird)
Add lastVersion in browse listings
quickjump now works on candidate pages
paging enabled for recent uploads and revision pages
As a final note, I just realized while updating the docbuilder that while it is still somewhat janky, and the UI is lacking, I believe that it now builds documentation for candidates!
Is there any way to opt out of Hackageâs dark mode? I like dark modes, all my desktop applications implement a dark mode, as are most of the websites I visit, but Hackageâs dark mode is incomplete and hinders readability in some places.
Good catches! Peter jumped in and patched up the issues you found. The fixes are now live, assuming you force a reload of the css. We still will need to polish the dark mode a bit going forward, but the most problematic stuff is at least all solved.
Edit: deleting this post because I just realized it was a response to a comment from over a year ago and not worth reopening.
Discourse confuses me by highlighting new-to-me discussions as ârecentâ just because somebody posts a new comment on it. (Maybe we shouldnât resurrect old threads very often)
Yep, you got it. I just sort of decided that thereâs no need to support cabal < 2 â even older ghcs are still supported by newer cabal versions, and the last ltses which shipped with it seem about to EOL (cabal 2.0 was released in 2017). And meanwhile the occasional confusion about the 00-index not containing all packages seems to come up far more often, especially as newer versions of cabal files become more frequent on hackage.
Bumping this thread to announce a new hackage redeploy. Some more notable changes:
Email notifications for revision upgrades â opt in to that and other useful notifications from your account management page linked from User accounts | Hackage
Bugfix for nonupdating âlatest versionâ in package browse.
JSON endpoint for top downloaded packages
improved check for changelogs and readme files
uses cabal 3.10 â this should mean support for uploading multilibs is enabled!
Please enable the new email notification (for dependencies going out of bounds) and let me know if there are any problems with it!
When the notification is enabled, the setting can be configured to not keep sending emails if the second highest version number also doesnât accept the new dependency (see below). This should keep traffic to a minimum.
The email notifications for out of bounds packages is so nice. I used to rely on Stackage reports on GitHub but then I created an issue for a number of packages including one I maintained so I did not see that it went out of bounds.
Do you know of any good user-facing resources that describe multilibs? I think these have a lot of really good potential, but I think that we need to explain them well in order to get the most value.
(Maybe we shouldnât resurrect old threads very often)
