Repository navigation
Release the IDA plugin as 2.1.0 - #51
Merged
Merged
Conversation
Nothing in the versioning scope changes since 2.0.0: the settings keys, the minimum IDA version, the Python dependencies and the install method are identical. The release adds features and fixes without anything a user has to change, so it is a minor release: Binary Ninja match tinting in its own views, IDA's MCRIT requests and most of the export off the main thread, table models for the match tables, and the job selection and client fixes. The Binary Ninja plugin keeps its own version line and is released separately, as 1.0.1. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…ja versions An old bare 1.4.5 tag blocks that version too. The release action also refuses the version already in plugin.json, which a dry run of 1.0.0 showed, so the first Binary Ninja release is 1.0.1. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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.
Cuts the IDA plugin release 2.1.0, following RELEASING.md.
Release commit
mcrit_plugin/ida/ida-plugin.jsonandmcrit_plugin/ida/config.pyare set to 2.1.0.CHANGELOG.md,## [Unreleased]becomes## [2.1.0] - 2026-10-15, with a fresh empty[Unreleased]above it and the compare links at the foot updated. Added, Changed and Fixed all have entries, so no subsection is dropped.Why minor: since 2.0.0 nothing in the versioning scope changed. The settings, the minimum IDA version (
>=9.0), the Python dependencies and the install method are all identical. The release adds features and fixes:The date is today's. If the tag lands on a later day, adjust the heading before merging.
Docs commit
RELEASING.mdnow names the old bare1.4.5tag among the versions the Binary Ninja release cannot use. It also says the action only releases a version greater than the one inplugin.json: a dry run with 1.0.0 was refused with "not greater than the current version", so the first Binary Ninja release will be 1.0.1.Rehearsal
Run locally on this branch:
verify_metadata_sync.py --expected-version 2.1.0(IDA) and the Binary Ninja metadata checkverify_settings_sync.pyandrun_quality_checks.pypython -m pytest tests(334 tests)package_plugin.py, which buildsmcrit-ida-2.1.0.zipwith 74 files, version 2.1.0 and nobinjafileshcli plugin linton that ZIP: no recommendationsAfter merging
ida-v2.1.0there and push the tag.binja-release.yml, with release notes written from this changelog.🤖 Generated with Claude Code