release v8.0.0

[mr-tz]

Release checklist

• Ensure all milestoned issues/PRs are addressed, or reassign to a new milestone.
• Add the don't merge label to all PRs that are close to be ready to merge (or merge them if they are ready) in capa and capa-rules.
• Ensure the CI workflow succeeds in master.
• Ensure that python scripts/lint.py rules/ --thorough succeeds (only missing examples offenses are allowed in the nursery). You can manually trigger a thorough lint in CI via the "Run workflow" option.
• Review changes
  • capa https://github.com/mandiant/capa/compare/\<last-release>...master
  • capa-rules https://github.com/mandiant/capa-rules/compare/\...master
• Update CHANGELOG.md
  • Do not forget to add a nice introduction thanking contributors
  • Remember that we need a major release if we introduce breaking changes
  • Sections: see template below
  • Update Raw diffs links
  • Create placeholder for master (unreleased) section

    ## master (unreleased)
    
    ### New Features
    
    ### Breaking Changes
    
    ### New Rules (0)
    
    -
    
    ### Bug Fixes
    
    ### capa Explorer Web
    
    ### capa Explorer IDA Pro plugin
    
    ### Development
    
    ### Raw diffs
    - [capa <release>...master](https://github.com/mandiant/capa/compare/<release>...master)
    - [capa-rules <release>...master](https://github.com/mandiant/capa-rules/compare/<release>...master)
    

• Update capa/version.py
• Create a PR with the updated CHANGELOG.md and capa/version.py. Copy this checklist in the PR description.
• After PR review, merge the PR and create the release in GH using text from the CHANGELOG.md.
• Verify GH actions
  • upload artifacts
  • publish to PyPI
  • create tag in capa rules
  • create release in capa rules
• Update homepage
• Spread the word
• Update internal service

closes #2498

[Ana06]

🎉

[mike-hunhoff]

🚀

[williballenthin]

can we hold off until mandiant/capa-rules#953 and mandiant/capa-rules#954 are merged?

if we tackle the prevalence database soon, it would be nice to include those rules in the dataset, rather than waiting for the next release.

[williballenthin]

recommend updating website "what's new" section too, or i can do this in a separate PR.

[mr-tz]

For waiting, it depends on when @Ana06 needs the release ready and how long the rules PR would take.

Good idea to change the website as part of the release PR.

[williballenthin]

lgtm