-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No PR for version update of gz-physics even if the new version is correctly listed in bot-versions output and no error is listed in version error #3010
Comments
There is a similar issue for gz-sim that is at 8.3.0 and no PR is opened to update to 8.6.0 . |
Some interesting pointers: @zklaus was also really helpful on Element, thanks! : https://matrix.to/#/!SOyumkgPRWoXfQYIFH:matrix.org/$17273353865774xzwaO:matrix.org?via=matrix.org&via=gitter.im&via=ifisc.uib-csic.es |
Interestingly, the latest run of |
I have no idea what changed, but now all the version update were unblocked, see for example conda-forge/gz-physics-feedstock#41 . The only one missing is gz-sim, where the "wrong" |
At conda-forge/gz-sim-feedstock#65 we are experiencing something strange with the automatic updates that we are not sure how to further debug.
The project is https://github.com/conda-forge/gz-physics-feedstock/ . The latest version on conda-forge is 7.2.0, while there was an upstream tag for 7.3.0 (https://github.com/gazebosim/gz-physics/releases/tag/gz-physics7_7.3.0, unfortunatly the tag format
gz-physics7_7.3.0
probably plays a role here).By inspecting the
bot-versions
output, you can find the new version is correctly detected: (see https://github.com/regro/cf-scripts/actions/runs/11007210867/job/30562973811):Also by manually triggering an update with conda-forge/gz-physics-feedstock#39, the correct 7.3.0 version is updated (see conda-forge/gz-physics-feedstock#40).
Furthermore, there is no error for gz-physics in https://conda-forge.org/status/#version .
However, it seems that no automatic PR to update the repository to 7.3.0 is opened by the bot.
Does anyone have some pointer to debug this issue further? Thanks a lot in advance!
The text was updated successfully, but these errors were encountered: