mirror of
https://github.com/mandiant/capa.git
synced 2025-12-30 14:40:53 -08:00
52c0cfd5d0
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.
2.4 KiB
2.4 KiB
Release checklist
- Ensure all milestoned issues/PRs are addressed, or reassign to a new milestone.
- Add the
dont mergelabel 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/ --thoroughsucceeds (onlymissing examplesoffenses are allowed in the nursery). - Review changes
- capa https://github.com/fireeye/capa/compare/<last-release>...master
- capa-rules https://github.com/fireeye/capa-rules/compare/<last-release>...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
- New Features
- New Rules
- Bug Fixes
- Changes
- Development
- Raw diffs
- Update
Raw diffslinks - Create placeholder for
master (unreleased)section## master (unreleased) ### New Features ### New Rules (0) - ### Bug Fixes ### Changes ### Development ### Raw diffs - [capa <release>...master](https://github.com/fireeye/capa/compare/<release>...master) - [capa-rules <release>...master](https://github.com/fireeye/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 and create a tag in capa rules upon completion.
- Spread the word