kayx23 opened a new pull request, #632:
URL: https://github.com/apache/apisix-docker/pull/632

   **Why submit this pull request?**
   
   - [x] Bugfix
   
   **What changes will this PR take into?**
   
   Same class of breakage as #630. 
[apache/apisix-docker#631](https://github.com/apache/apisix-docker/pull/631) 
merged and its PR CI passed, but Hub never got `apache/apisix:3.18.0-*`.
   
   Publishing is `Docker image` on `push` to `release/apisix-**`. The 
`release/apisix-3.18.0` run ended in `startup_failure` before any job started:
   
   https://github.com/apache/apisix-docker/actions/runs/32466017063
   
   The annotation is:
   
   > The actions 
`docker/setup-qemu-action@ce360397dd3f832beb865e1373c09c0e9f86d70a` and 
`docker/setup-buildx-action@4d04d5d9486b7bd6fa91e7baf45bbb4f8b9deedd` are not 
allowed in apache/apisix-docker ...
   
   
[`approved_patterns.yml`](https://github.com/apache/infrastructure-actions/blob/master/approved_patterns.yml)
 currently lists:
   
   - `docker/setup-qemu-action@96fe6ef7f33517b61c61be40b68a1882f3264fb8`
   - `docker/setup-buildx-action@bb05f3f5519dd87d3ba754cc423b652a5edd6d2c`
   
   `docker/login-action@dbcb8138` from #630 is still allowlisted and is 
unchanged.
   
   After this merges, cherry-pick onto `release/apisix-3.18.0` and push that 
branch so Hub publish actually runs. Pushing to `master` alone does not push 
images.
   
   **Checklist:**
   
   - [x] Did you explain what problem does this PR solve?
   - [ ] Have you added corresponding test cases?
   - [ ] Have you modified the corresponding document?
   - [x] Is this PR backward compatible?


-- 
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