Repository navigation
Bump rqt_robot_monitor for Qt6 - #235
Conversation
|
Don't we need to bump the version? Currently this doesn't do anything, does it? |
|
Whups, there is no new version yet. I could pin to Is there already an ABI-checker in place? Otherwise it only works with the new mutex right? |
testpr.yaml's abi-comment job was skipped for pull requests from forks, whose runs only get a read-only token (e.g. #235). Post the comment from a separate workflow_run workflow instead, which runs from main with a write token, for all pull requests. It never checks out or runs pull-request code: the abi-check-*.md artifacts and the branch name come from the pull request's run, so they are only used as the comment text, and the pull request is looked up from the API (open, head at the built commit) rather than taken from the artifacts. A cancelled run (a newer push) posts nothing. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
ABI check (linux-64)lyrical linux-64: 1 can be bumped on their own1 packages can be bumped on their own (no libraries: 1)
Compared with the newest builds on https://repo.prefix.dev/robostack-lyrical/linux-64. About this checkEach package this pull request built, compared with its newest released build (
Exported symbols are compared (the released packages are stripped, so struct layouts aren't); unchanged installed headers rule out layout and inline changes, changed ones are listed for review. Dependents to rebuild are the released ones linking to a changed library. A changed pin is part of the comparison. |
No description provided.