runtimeverification / runtimeverification/mir-semantics
Inconsistent KMIR versions across project
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 52
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
It appears our scripts that bump versions are not doing so consistently over the project and there are descrepancies:
and at the time of writing, dockerhub has our latest release at 0.4.213
I believe the tag from docker is the correct version, and the others have just not updated correctly. There also may be more than I found with this quick search
Contributor guide
No contributing guide indexed for this repository
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 comparing the version in kmir/pyproject.toml with package/version and the 0.4.213 Docker Hub release referenced in the issue. Trace the project’s version-bumping scripts to find all version sources and determine which value is authoritative. Done means the relevant files and release metadata are updated consistently and the discrepancy is covered by the existing versioning workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- build-system, release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100