You don't need to rebuild the man page for stable releases. No point in bumping the revision.
As for head, `jq.1.prebuilt` is a slightly outdated option.
Possibility of cutting a release for downstream packagers?
==========================================================
The latest release, 3.0.0, is from 2009, and this is the release packaged by packagers (Debian, Homebrew and MacPorts on macOS, etc). 175 commits have been added to master since then, with 19 new languages added:
```
augeas
bfpp
brainfuck
chaiscript
coffeescript
coq
forth
golang
jam
logtalk
modula2
modula3
nsis
oberon
prolog
puppet
rebol
rust
tex_dtx
```
In particular, CoffeeScript, Go and Rust are very widely used these days, but the packaged version is useless for all these languages.
Therefore, could you please consider cutting a release so that downstream packagers could pick up the (not-so-)recent improvements? Thanks.
Previous discussion starting here: https://github.com/jarun/googler/issues/83#issuecomment-219848271. The concluding remark there was
> I didn't think from this perspective earlier, but you can always use the o key at the omniprompt to open the search in the browser. One additional step in the workflow but what is the percentage of pages you do not trust? I'ld say it's a rare case and we already have a way.
and I agree with that.
Since @jarun and I are no longer interested in implementing complex features (this one will be rather involved), new features won't materialize without PRs (and even then they may be rejected).