Repository navigation
Conversation
…is built CI - IDA integration runs the live headless and GUI suite on Linux for every minor version from 9.0 to 9.5 instead of 9.3 alone. The dispatch-only matrix keeps the offline IDALib check on Windows and macOS, now on 9.5. install_idalib_runtime.py installs the bundled bindings whether IDA ships them as a wheel or, as 9.0 and 9.1 do, as a source package. - The matrix jobs no longer repeat the metadata, settings, ruff and plugin lint checks that the Validate and IDA package workflows run, and install their Python packages with uv. - A Binary Ninja integration workflow runs the same suite through Binary Ninja headless and in the GUI. It needs the BN_LICENSE_B64 and BN_DOWNLOAD_URL_LINUX_X64_STABLE secrets and is skipped without them. - Ghidra integration verifies the SHA-256 of the Ghidra download, cancels superseded runs and uploads its logs next to the screenshots. - Validate runs actionlint. Workflows that run on push ignore tag pushes, so pushing a release tag starts no second CI run. Jobs have timeouts. - Integration artifacts no longer include the IDA user directories, which hold the licence registry. Releases - The IDA and Binary Ninja release workflows build the offline dependency bundles before anything is published, attach them and the plugin archive to a draft release, and then publish it. A failed bundle build used to leave a published release without its bundles, and assets cannot be added to an immutable release after publication. - verify_release_ci.py replaces the inline check of the pytest workflow. It reads the newest push or dispatch run on the release commit, so an older green run cannot hide a newer failure, and for IDA requires all six integration jobs to have succeeded rather than been skipped. Binary Ninja releases are gated on pytest and Validate only until its CI secrets exist. - The release jobs run the unit tests on the verified commit and refuse to publish if the tag moved after verification.
idapro from IDA 9.0 and 9.1 failed to load libidalib.so when the run used an isolated IDAUSR, so the headless integration never started on those versions.
… point On IDA 9.0 the bundled PyQt5 is importable under IDALib, and ida-settings imports QtCore from it when it is loaded. The check is about what the plugin's entry point imports, so load ida-settings before taking the baseline.
ida_undo.create_undo_point takes an action name and a label from IDA 9.1 on. IDA 9.0 exposes only the form that takes a packed record, so the call raised TypeError and importing labels, like every other mutation, stopped there. The change now goes ahead on 9.0 without an undo point.
Skipping the undo point let the change through but left an import of labels as separate undo steps. IDA 9.0 accepts the record the SDK's two-string helper packs: both strings, each zero-terminated.
Whether a second release can be created for a tag that only has a draft is not something the release notes should assert; the advice to delete the failed draft first holds either way. The pytest workflow can also be dispatched by hand.
This was referenced Nov 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The IDA integration job only ran on 9.3. It now runs on every version we say we support, 9.0 to 9.5, and it got faster on the way:
hcli ida installdoes the download, licence and EULA in one go, so a job takes about a minute and a half instead of three.Running 9.0 turned up a real bug:
ida_undo.create_undo_point(name, label)only exists from 9.1, so on 9.0 importing labels (and anything else that changes the database) died with aTypeError. Fixed inIdaBackend, with a changelog entry.The rest:
binja-tests.ymlfor the licensed Binary Ninja run. It skips itself untilBN_LICENSE_B64andBN_DOWNLOAD_URL_LINUX_X64_STABLEare set, so it is not part of the release gate yet.All six IDA versions and Ghidra pass on my fork, and so do the Windows and macOS jobs (IDA 9.5, headless only), which now run on pushes to
mainand manual runs instead of behind a tick box. The release workflows themselves have not run yet, a release is the only thing that triggers those.Note
This touches
ghidra-tests.yml,RELEASING.mdanddocs/development.md, same as #61. Happy to rebase onto whichever goes in first.