* doc: add rules documentation
* version: add accessor for capa major version and git checkout command
* doc: rules: document version output
* doc: rules: show example error due to mismatched rule version
* doc: rules: update links
* ci: tag major rule version test
* ci: tag major rule version
* doc: update changelog
* ci: force to replace tag if exists
* ci: simplify tagging step
* Update doc/rules.md
* feat: disable tag, show error branch cmd
* doc: update major version rules branch
* Apply suggestions from code review
Co-authored-by: Willi Ballenthin <willi.ballenthin@gmail.com>
* Update capa/main.py
* black
Co-authored-by: Moritz Raabe <moritz.raabe@mandiant.com>
Co-authored-by: Moritz <mr-tz@users.noreply.github.com>
Use an empty item in the `New Rules` section as a marker for the GitHub
Action. If this causes problems, we could look into other solution such
as writing 2 lines before `### Bug Fixes`. But I think this is the
easiest I can come up with. So lets give it a try.
This release includes several bug fixes, such as a vivisect fix for a bug, which caused that capa didn't work on Windows with Python 3. It also adds 17 new rules and a bunch of improvements in the rules and IDA rule generator. We appreciate everyone who opened issues, provided feedback, and contributed code and rules.
This is the very last capa release that supports Python 2.
This makes it a bit easier to check if all milestoned issues/PRs are addressed, or reassign to a new milestone.
I am committing directly to master as this is a minor change which doesn't need review.
Avoid erroneous commits. The pre-commit can be skipped with the
`--no-verify` option, which is not available with the post-commit.
Note that `pre-commit` doesn't run when rebase while post-commit did.
This allows to have a single script which is run by both hooks. This
scripts can also be used independently to run the CI setup locally.
Move the cloning all submodule option to the beginning as when using
capa in development this is the most common option. Test files are
needed to run the tests locally. Simplify the rest of the submodules
documentation, as it is easier for people to look the submodule
documentation than for us to maintain a copy. The submodule init step
shouldn't be needed to clone the rules directory.
