mitre-attack / mitre-attack/attack-workbench-frontend
[REQUEST] Release Tracks
@avwchapman is already working on this.
Since Aug 14, 2026.
- Dominant language
- TypeScript
- Stars
- 438
- Forks
- 79
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 3
Description
Update the current “Collections” system into a new Release Tracks system that makes it easier to plan, review, and publish content releases. The aim is to have one clear way to manage what belongs in a release, keep a history of changes over time, and “stamp” official releases with a version number. It will also connect to a new review workflow, so we can separate items that are still being worked on from items that are ready to ship, letting teams keep working on future updates without blocking an upcoming release. Separate child issues will cover additional implementation details.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.