Add tools to ensure we didn't break API compatibility
Open
@HaroldCindy is already working on this.
Since Nov 11, 2025.
enhancement
- Dominant language
- C++
- Stars
- 17
- Forks
- 10
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 4
Description
Now that we're better about making sure everything has a unique reference in Ares, we need to be sure that we don't accidentally remove anything from the API surface, and adding anything should increment the API version. We need some tooling to ensure that we do so. Might also be nice to be able to swap out function implementations depending on API version if necessary to help us avoid the ll.*Base64.*Correct() problem.
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.