v0.3.13.0b missing from Hackage

[colindean]

trafficstars

v0.3.13.0a and v0.3.13.0b are missing from https://hackage.haskell.org/package/pandoc-crossref, which is where Homebrew gets the package it uses to build the app. I'd like to bump the Homebrew formula (in Homebrew/homebrew-core#109242) to this new version in order to get pandoc 2.19 support and silence some warnings.

Even a v0.3.13.1 would suffice for my need.

[lierdakil]

Releases with a letter suffix are just to have a place to attach binaries, there are no source code differences (aside from maybe relaxed version constraints) between v0.3.13.0, v0.3.13.0a and v0.3.13.0b (in fact v0.3.13.0b only exists because I forgot to update GHC version on CI for the Linux build)

AFAIU (bear in mind I don't own a mac, so I have a very fuzzy idea of how that all works with homebrew), you don't need to bump the formula, you just need to somehow rebuild it against the new pandoc. I've relaxed version constraints on Hackage at the same time I published the new builds, so that should work fine.

[colindean]

OK, thanks for the clarification. The exercise then may be to somehow retrieve the metadata updates dynamically and authentically since Homebrew downloads the source file from Hackage and compiles from it. Since the source tarball isn't updated when a maintainer changes Hackage metadata, we need to somehow capture that metadata or we have to wait for a new source drop.

I'll discuss with the Homebrew maintainers and see what the best course of action is.

[ickc]

AFAIU (bear in mind I don't own a mac, so I have a very fuzzy idea of how that all works with homebrew), you don't need to bump the formula, you just need to somehow rebuild it against the new pandoc. I've relaxed version constraints on Hackage at the same time I published the new builds, so that should work fine.

Homebrew packages can be pre-built or build from source. A typical user with a default, recommended homebrew setup would have a pre-built binary, which is why it will complain.

One way to do it is to just make a formal release like v0.3.13.0b despite no difference in source code, and propagate that version change to all downstream package manager including homebrew to enforce a rebuilding of pre-built binaries, which would uses the latest pandoc at the time.

[lierdakil]

make a formal release

Not how we're supposed to do releases on Hackage. Now, I do "formal releases" on this here repo. Can Homebrew track those instead?

[ickc]

In principle yes, convincing them to do it is another matter.