ijq: update checksum for 1.3.0 release

[stefanb]

Ref:

• go 1.27rc2, go@1.26 1.26.5 (new formula) #288803

---

• Have you followed the guidelines for contributing?
• Have you ensured that your commits follow the commit style guide?
• Have you checked that there aren't other open pull requests for the same formula update/change?
• Have you built your formula locally with HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>?
• Is your test running fine brew test <formula>?
• Does your build pass brew audit --strict <formula> (after doing HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>)? If this is a new formula, does it pass brew audit --new <formula>?

---

• AI was used to generate or assist with generating this PR. Please specify below how you used AI to help you, and what steps you have taken to manually verify the changes.

---

[daeho-ro]

Something is wrong. Current tag v1.3.0 commit hash is 38e04ac303dd316abd3f00b8feea1737cf4ad1d7 but the source tarball is redirect into wrong rev.

curl -I https://codeberg.org/gpanders/ijq/archive/v1.3.0.tar.gz
HTTP/2 200 
accept-ranges: bytes
access-control-expose-headers: Content-Disposition
cache-control: private, max-age=300
content-disposition: attachment; filename="ijq-v1.3.0.tar.gz"; filename*=UTF-8''ijq-v1.3.0.tar.gz
content-type: application/octet-stream
last-modified: Sun, 12 Jul 2026 11:56:43 GMT
link: <https://codeberg.org/api/v1/repos/gpanders/ijq/archive/430fa3c17baabb1c227106a7d893c18930ded43f.tar.gz?rev=430fa3c17baabb1c227106a7d893c18930ded43f>; rel="immutable"
no-gzip-compression: 1

Not sure how 430fa3c17baabb1c227106a7d893c18930ded43f appears here..

[daeho-ro]

• https://codeberg.org/gpanders/ijq/issues/31

[daeho-ro]

• https://codeberg.org/Codeberg/changelog/issues/2#issuecomment-19104626

[daeho-ro]

Similar things happen in smake, header rev is not matched with release tag commit hash. Checksum can be explained by the update from codeberg side, but this rev difference is really weird and waiting for the response of ijq upstream, they already asked to codeberg.

[daeho-ro]

It is just a difference between tag object and commit object for annotated tags, so this is purely caused from the codeberg update. I think it is fine to go now.

[github-actions]

🤖 An automated task has requested bottles to be published to this PR.

Caution

Please do not push to this PR branch before the bottle commits have been pushed, as this results in a state that is difficult to recover from. If you need to resolve a merge conflict, please use a merge commit. Do not force-push to this PR branch.