Skip to content

Update changelog for Hoogle 5.0.19 - #467

Merged
Bodigrim merged 1 commit into
ndmitchell:masterfrom
Bodigrim:changelog
Jan 19, 2026
Merged

Bodigrim merged 1 commit into
ndmitchell:masterfrom
Bodigrim:changelog

Conversation

@Bodigrim

@Bodigrim Bodigrim commented Jan 2, 2026

Copy link
Copy Markdown
Collaborator

@ndmitchell how do you feel about making a release soon? I think we are in a good position for it.

@Bodigrim

Copy link
Copy Markdown
Collaborator Author

@ndmitchell just a gentle reminder. (I don't have Hackage rights to roll out the release myself)

@ndmitchell

Copy link
Copy Markdown
Owner

I've now given you permissions on Hackage. Make a release as you feel is appropriate. Generally, we shouldn't be waiting on me for anything, as I'm just not responsive enough right now, alas.

The larger issue is that the hoogle.haskell.org website is something I no longer have permissions. We will need to follow up with the haskell.org maintainers, as I think my account got locked at some point.

@Bodigrim

Copy link
Copy Markdown
Collaborator Author

Thanks, I'll make a release soon.

@jmct could you help us with hoogle.haskell.org permissions?

@jmct

jmct commented Jan 19, 2026

Copy link
Copy Markdown

Yep, I'm on it.

@Bodigrim
Bodigrim merged commit e11273e into ndmitchell:master Jan 19, 2026
5 checks passed
@Bodigrim
Bodigrim deleted the changelog branch January 19, 2026 20:37
@Bodigrim

Copy link
Copy Markdown
Collaborator Author

@jmct @MangoIV any updates?

@jmct

jmct commented Jan 25, 2026

Copy link
Copy Markdown

Yes, apologies.

@MangoIV said the following:

it looks like hoogle is deployed from this branch: https://github.com/bgamari/hoogle/tree/h-o-deployment

So it shouldn't require direct access to the infrastructure.

If that doesn't work or if you want access anyway, we can get that sorted.

@jmct

jmct commented Jan 25, 2026

Copy link
Copy Markdown

Ideally we'd make it deploy from a branch on this repo, IMO. There's an infrastructure sync meeting tomorrow and it's on the agenda.

@MangoIV

MangoIV commented Jan 26, 2026

Copy link
Copy Markdown

We can talk about this tonight, but here's what I would propose

  • we merge ben's changes into upstream hoogle (here)
  • I pull the updated hoogle from here and deploy on the machine.

That would mean you would have to ask me (or someone else with access to the machine) to update hoogle.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants