runtimeverification / runtimeverification/evm-semantics
Discrepancy in `deps/k_release` and `deps/pyk_release` format
Open
Nobody has claimed this yet.
- Dominant language
- KCL
- Stars
- 591
- Forks
- 156
- Avg merge
- 2h 19m
- Merged PRs (30d)
- 1
Description
Example:
deps/k_release--5.6.114deps/pyk_release--v0.1.311
This might be an issue in runtimeverification/devops.
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 inspecting deps/k_release and deps/pyk_release, then check the referenced runtimeverification/devops repository for how these values are produced and consumed. Clarify the intended version format, align the two release values or their generation, and verify that the release tooling accepts the resulting format.
Written by the indexing model from the issue text.
Assessment
- Domain
- devops, release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100