rioriost opened a new issue, #2555:
URL: https://github.com/apache/age/issues/2555

   **Describe the bug**
   
   The official Apache AGE GitHub release for PostgreSQL 17 / AGE 1.7.0 exists, 
but the corresponding official Docker Hub release image is missing.
   
   - GitHub release: https://github.com/apache/age/releases/tag/PG17/v1.7.0-rc0
   - Expected Docker Hub tag: `apache/age:release_PG17_1.7.0`
   - Docker Hub tags: https://hub.docker.com/r/apache/age/tags
   
   This appears to be a release-image publishing gap. The neighboring 
combinations are available:
   
   - `apache/age:release_PG17_1.6.0`
   - `apache/age:release_PG18_1.7.0`
   
   **How are you accessing AGE (Command line, driver, etc.)?**
   
   Docker / Docker Hub.
   
   **What data setup do we need to do?**
   
   None.
   
   **What is the necessary configuration info needed?**
   
   None.
   
   **What is the command that caused the error?**
   
   ```console
   docker pull apache/age:release_PG17_1.7.0
   ```
   
   The Docker Hub API currently returns HTTP 404 with:
   
   ```text
   httperror 404: tag 'release_PG17_1.7.0' not found
   ```
   
   **Expected behavior**
   
   The official multi-architecture release image 
`apache/age:release_PG17_1.7.0` should be published, consistently with the 
existing release-image naming convention. It would also be helpful to check the 
release automation so future GitHub releases and Docker Hub images do not get 
out of sync.
   
   **Environment (please complete the following information):**
   
   - PostgreSQL version: 17
   - Apache AGE version: 1.7.0
   - Docker Hub status checked: 2026-08-28
   - GitHub release published: 2026-02-11
   
   **Additional context**
   
   A search of open and closed issues, as well as recent discussions, found no 
existing report for this missing tag.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to