Hello everybody, I've noticed that the Hive 4.2.0 image has been updated shortly after its initial release, but the release tag in GitHub doesn't point to the revision from which the image was built.
According to GitHub, the release tag <https://github.com/apache/hive/releases/tag/rel%2Frelease-4.2.0> was created on Nov 21st 2025. We've adopted that docker image on Nov 27th with the exact digest 4.2.0@sha256 :499bdb1f2d05fd8a0c39738244336514f193b833e35052a23e67927e44a7f7ad. Then, according to Docker Hub <https://hub.docker.com/layers/apache/hive/4.2.0/images/sha256-2a33b8fcd12ff408f8c451698f59c486b450303936f1e19130117bc7a8efe08d>, the image was updated on Nov 28th to a new digest: 4.2.0@sha256 :b0d2842722567a89ac35da8af9002b6bba0fc2d0eb272664954a1fa46d694472 We're now trying to update to the latest image version and noticed that it contains a change (commit <https://github.com/apache/hive/commit/c46dbf203a9b7f08b1eb448773d1ba54e045fa9b#diff-4f2c828265eda522127432251cd3e235e6dc2fe678216bd679bfcb553435bbea>) that breaks our custom image build. But that change is *not* part of the rel/release-4.2.0 tag in GitHub. Please don't worry about that breaking change, I can sort it out. I'm just wondering whether the image update was pushed accidentally or if the GitHub tag should be updated to exactly reflect what's in the 4.2.0 version. Kind Regards, Simon -- * CONFIDENTIALITY NOTICE*: The contents of this email message, and any attachments, are intended solely for the addressee(s) and may contain confidential, proprietary and/or privileged information legally protected from disclosure. If you are not the intended recipient of this communication, or if you received this communication by mistake, please notify the sender immediately and delete this message and any attachments. If you are not the intended recipient, you are hereby notified that any use, retransmission, dissemination, copying or storage of this message or its attachments is strictly prohibited.
