New version: OCCT_jll v7.7.2+0 #113891
New version: OCCT_jll v7.7.2+0 #113891
Conversation
UUID: baad4e97-8daa-5946-aac2-2edac59d34e1 Repo: https://github.com/JuliaBinaryWrappers/OCCT_jll.jl.git Tree: bef34b68c20cc34475c5cb464ab48555e74f4c61 Registrator tree SHA: 191228b6dd8b9d0e2965ae3e705fe54c51dcfee8
|
Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of AutoMerge guidelines. If all these guidelines are met, this pull request will be merged automatically, completing your registration. It is strongly recommended to follow the guidelines, since otherwise the pull request needs to be manually reviewed and merged by a human. 1. AutoMerge Guidelines are all met! ✅Your new version registration met all of the guidelines for auto-merging and is scheduled to be merged in the next round. 2. To pause or stop registrationIf you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text Tip: You can edit blocking comments to add |
|
Stop, this breaks the ABI: JuliaBinaryWrappers/OCCT_jll.jl@919b378. @jaakkor2 can you please retroactively fix compat bounds of gmsh_jll here and in Yggdrasil (first here, then in Yggdrasil)? |
gmsh_jll 4.10.2, 4.11.1, 4.12.2, 14.13.0 depend on OCCT_jll 7.6.2 #113891
|
The retroactive compat bounds were added in #113905. Can this PR now be "resumed"? Or does it need to be recreated or something? |
|
[noblock] gentle ping @giordano |
giordano
deleted the
registrator-occt_jll-baad4e97-v7.7.2+0-335348113d
branch
Autogenerated JLL package registration