[SBIN] Create a GitHub Release job that regenerates the ABI database
Nobody has claimed this yet.
- Dominant language
- Cuda
- Stars
- 854
- Forks
- 236
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 62
Description
We need a script / job that can be executed each time we do a release. This job's function is to regenerate and update the reference ABI database, ensuring the database reflects the current, official release ABI. This could just be a secondary mode of ABI check CI job where it pushes the state back to a central location.
Since we need to support patch releases, the upload of the ABI database can’t overwrite the existing one. Instead we need to store N numbers of databases.
For example when we are on 26.08 we still need the 26.06 database if we need to do a patch release for some reason
copied from https://docs.google.com/document/d/13fxnoZQIvJPKDwz-21fXMrux6HtJG7KW5cHafrmJtAo/edit?usp=sharing
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.
Research direction
Start by locating the existing ABI check CI job and the repository's GitHub release workflow; the issue does not name specific files or tests. Trace how the ABI database is generated and stored, then define a release path that preserves databases for multiple release versions, including patch releases. Done means a release can regenerate and upload the correct version without overwriting earlier databases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- build-system, ci-cd, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100