yuchanns opened a new issue, #4994: URL: https://github.com/apache/opendal/issues/4994
### Describe the bug https://github.com/apache/opendal-go-services/actions/runs/10322022975/job/28576406436 Yesterday, v0.49.0-rc.1 of the opendal-core and v0.1.0-rc.1 of openda-go were released. Then the cronjob of opendal-go-services built new artifacts and pushed them to the main branch. The commit should be `ce0b4d343ae758fd63f8c340f4c99de4309f9f96`. Later we got a set of tags for the opendal-go-services: v0.1.0-rc.1, s3/v0.1.0-rc.1, etc. I found that v0.1.0-rc.1 is tagged with the correct commit, while the rest of them are tagged with `f2e8851055abbd2b7c45d0f496152cb56dc6f4ae`, the previous commit. That indicates all of the services/tag use old artifacts. ### Steps to Reproduce Release opendal-core and opendal-go version. ### Expected Behavior All tags should be the correct commit. ### Additional Context _No response_ ### Are you willing to submit a PR to fix this bug? - [ ] Yes, I would like to submit a PR. -- 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]
